UB bug still present in v16, [split by Baronius] Options

[Baronius]

The bug was known for v15 already. Wouldn't it be easier to fix it in UB itself?

[This topic was split from this]

[Baronius]

Okay, so I'm kind of unclear about the rules here (and I accept they might vary from person to person; there doesn't need to be an Official BWL Line any more than an Official Any Other Site Line).

Are people interested in a serious intellectual discussion of the topic, or is it just a point-scoring exercise? I'm not terribly interested in the latter (though I don't mind having a conversation with people who are and blanking people who aren't.)

DavidW, I'm sure Sikret has even less hope than myself that those certain G3 Fixpack developers will ever consider that their viewpoint isn't superior to others'. Sikret knows it very well what it means when your thorough work is broken due to the mistake and pride of others, and instead of correcting their mistakes, those others deny their mistakes and start to attack & ridicule your work.

@plainab:

Thank you for your post, and for the clarification. You seem to be completely different from those (= certain G3 FP developers) who I tried to cooperate with in the past. They ignored my advice and keep ignoring my arguments, because they're convinced about the superiority of their methods. So I do have a reason when I'm being harsh in my statements regarding their attitude.

Maybe if we work together on these little issues and get some consensus for the future, we will find the bigger problems become more manageable until they are all gone....

To tell the truth, I've lost all my hope in any cooperation with them.

Fine, a bigger problem, let's get it resolved. Get everyone together whose had a public mod release, and make these decisions. Get the results posted at every forum so we can all follow them. Until such consensus takes place, the community will remain fractured over this, you will continue to share with everyone why we are fractured, and some of us who try to help will become discouraged by it all.

If the G3 FP developers don't intend to split, revise and test their mod and will keep manipulating the players and dictating mod developers by abusing the popularity of BG2 Fixpack (which popularity was gained through powerful marketing and advertisements, and not exclusively with the quality of the work), then I will keep encouraging mod developers to boycott the use of G3 Fixpack.

They are the only one who can help on this situation, because they are responsible for the problems, not the authors of publicly released mods (and future mods). Are you wondering why they have never addressed any of my technical arguments? Because they have no valid counter-arguments, and pretend as if my arguments didn't exist, or simply spread the usual lie that "Baronius doesn't like the G3 Fixpack".

The reason they don't want to revise/split the mod is that it might decrease the popularity of the G3 Fixpack, because it wouldn't be possible to advertise it with the current populist slogans ("Baldurdash plus a few hundred fixes more"). If G3 Fixpack actually contained a few hundred real fixes, the original game would have probably been unplayable and would have been a huge and spectacular failure for Bioware.

The reason they didn't/don't want to devote more effort for its quality assurance (including proper testing) is that it would have made (it would make) the integration of new "fixes" slower, which again would decrease the popularity of G3 Fixpack.

I'm sorry if all this negative tone is discouraging for you plainab, but I've always been in favour of crying out the truth instead of staying silent. It would be hypocricy for myself, and I never do that. I am in favour of diplomacy, but it requires a minimal intention from the other side as well, and they don't have this intention.

So again, if you feel all this as negative and fruitless, then please just ignore it, and do what you enjoy doing -- modding. That is what we all do, because we like it. And good luck for BG1 Fixpack! I'm sure you won't make the same mistakes as the G3 BG2 Fixpack developers did and do. Test your work thoroughly, and don't advertise it with populist slogans -- tell no more and no less about it than what it actually is. Make detailed documentation of your fixes, and don't let yourself influenced by others. Consider suggestions and criticism, but don't let yourself to be influenced when you feel you're right. Always know what your goals are.