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]

[plainab]

Nice solution, plainab. thumb.gif It's "intelligent" code, because it detects the script's name.

He likes the code and that makes me happy. I'm not being sarcastic here.

As to the rest of the post, I take it you have a problem with G3's BG2 Fixpack? (Now I might be a bit sarcastic)

I can understand the concern about changes that make changes to other things. I and a group of others are working on what will become the G3 BG1 Fixpack. There are already things that I plan to offer as a "fix" because they make sense, but they may affect other things within the game. True if an existing mod expects it to be a certain way and I "fixed" it to be different then we have something that's incompatible or workable but not ideal. Was this not true back in the old days, when baldurdash and dudleyville came out with their respective fixpacks?

At that time, if something conflicted, a list of files would have to be made to show what could or couldn't be installed to have limited compatibility with each other. Until one or the other relented and changed their files to play nice with the other. The third party mod usually lost out and had to update their files to go with one or the other of the available fixpacks. Now that something new has come along that attempts to do what both the previous fixpacks tried, we are in the same position. We must learn to accept the G3 BG2 Fixpack for what it is, an attempt to fix bugs (granted some perceived bugs) within the game. Sure this would be easier if every file adjusted or every type of fix had its own component to be decided upon at install time. They have chosen to install the majority in a single component for the convenience of the installer. That leaves it to the rest of us to accept and work with or to deny and use

CODE

FORBID_COMPONENT ~setup-bg2fixpack.tp2~ ~0~ ~G3 BG2 Fixpack is installed. The fixpack and this mod are not compatible. Skipping installation.~ //repeat for any other component numbers as necessary.

in our mods.

If you want to have a proactive solution, to a reactive problem that is fine with me. Tell me what problems I will face when making the BG1 fixpack and I'll do my best to fix them before they get there. Sorry. That's not possible. I wouldn't fix a thing and there is no way to know what the problems will be until they arise. If we don't try we'd be left with a smattering of mods that try to do this and that here and there with no consistency rhyme or reason when taken as a whole. Be glad some people have stepped up to the plate to bring these fixes together in one install for each of the respected games. Yes, some things will break that is a given even in the most proactive situation. Yet, they could have said, "Here are the fixes! We're done. You're screwed. Change your mods to fit ours." They didn't and we won't. Some issues have been resolved by adjusting the fixpack others by updating some older code in the third party mods. It's a two way street to solve issues when proactive becomes reactive.

Now I don't normally like to post this long (unless it's code or something that I'm posting for review) so I'm going to wrap it up and say that you are entitled to your opinion. You're entitled to share that opinion as well. What I don't think you should do is drudge up past issues regarding something that is making widespread acceptance within the community for its efforts to squash the many bugs left behind by BioWare. I've already known that you've had issues with G3 BG2 Fixpack and don't need to hear it again (link to one of the other times you've had something to say along these lines would have been sufficient).

What I find appalling is that a simple posted solution to an issue between ToD, UB, SCSII, my NPC mod, and maybe others none of which was the G3 BG2 Fixpack brought on an entire bash (I use the word loosely) of the BG2 Fixpack. It's one thing to mention them as an example, once or twice. But to mention only them for all the issues you have, you seriously need to get some new material.

I guess, I was wrong. I am posting a bit longer....

You (or someone on your behalf) said that as a new modder someone might have looked at the area script reference and said, "Odd naming convention, but what the hey, I'll use it." First off, if someone is able to look at the file and see what the area script is, they've probably looked at several other areas and saw that the file names matched. But since WeiDu might not have been up to the task yet, they didn't want to overwrite an area file that just needed a script block, the existing one was used. WeiDu comes along and we update. It's the nature of the programming industry of any industry really. You work with what you can and make it work. Then as things get better, you incorporate it into your existing processes until the older methods can be completely phased out. This I fear is one of those times, we all need to get on board and work with these new processes to bring older things up to date and new things in line.

I came onto the IE modding scene in 2006, you've had this chip on your shoulder about the G3 BG2 Fixpack ever since then. It's not helping the community, when relatively new modders/players come along with questions and suggestions, to rehash an old issue that will probably always be ongoing rather than to simply answer the question.

I'll boil your post down for myself.
"The code is good. It solves the problem, but it doesn't solve the problem before it starts. Because the problem didn't know it was a problem until the problem become a problem. But my problem is G3 BG2 Fixpack." And that has nothing to do with this problem.

Let me ask you this, would it have been a problem if Bioware had created another expansion with additional quests and included an area file called AR0004.are that had a script reference of AR0004.bcs but no actual script? According to you no, because someone would have made a mod for the game without the expansion and had no clue of the problem in the first place. So the solution then for everyone else is the use AR0021.bcs for the AR0004.are file. No that's stupid, you ask the mod(s) made for the non-expansion to adjust theirs accordingly. They would because it makes sense. Your files are no more important than anyone else's. They are important to you, but not to everyone else. We just want a good game that we can play. If you choose not to be compatible with something, that is your choice. Players will just have to decide which route they want to take. We know you don't like the fixpack and certain components of several mods, just put it in your readmes that it's not compatible, forbid the components in your tp2 and go on. Quit bringing it up. It only brings others down.

Once again, thank you for the compliment on the code. It didn't take that long to come up with. But nobody could have foreseen the problem until it came up (except for maybe the first modder to use the ar0004.bcs instead of changing it to ar0021.bcs).