25 replies to this topic

[CamDawg]

With the disappearance of Kevin Dorner and the cessation of activity of the Baldurdash fixpack for BG2, several modders and myself began working on a new WeiDU fixpack to address the numerous bugs that have been identified since Baldurdash. This collaborative effort, including the work of modders from several different modding communities, has resulted in a fixpack that currently includes all of the fixes addressed by Baldurdash (including the Game Text Update) and several hundred new bugfixes. The project is ongoing, and we're working through a substantial list of bugs culled from various sites and the old Baldurdash forums. The project has matured enough for us to begin soliciting testers and recruit additional modding talent to continue the bugfixing efforts.

For testers, we're seeking players familiar with the intricacies of the game and engine, and an eye for detail is a requirement. Testing will commence with our next development release, slated for late April. The tester's role will be threefold--to report any issues with existing fixes, help us confirm and replicate existing bugs on our buglist, and to identify new bugs to be fixed.

For modders, we're looking for folks that can confirm, replicate, and fix bugs. One of the goals of the fixpack is to address bugs without overwriting files, so familiarity with file patching via WeiDU is very much desired. Failing that, being able to confirm and identify the source of bugs would still be a great help.

If you're interested in helping, either as a tester or fixer, please contact me via PM. The forum is currently private and hosted at G3.

[Caedwyr]

So is this supposed to replace Baldurdash, or will I have to install Baldurdash as well?

Why should I install this instead of Baldurdash?

What is G3, and where can I find a link to it?

Can I just reply in this thread if I am interested?

Edited by Caedwyr, 08 April 2005 - 10:47 AM.

[CamDawg]

So is this supposed to replace Baldurdash, or will I have to install Baldurdash as well? 

This fixpack will replace Baldurdash in its entirety. The current build already fixes all of the bugs addressed by Baldurdash and several hundred additional ones.

Why should I install this instead of Baldurdash?

The Fixpack is WeiDU-based, meaning it can be updated easily when new bugs and fixes are added. We've already identified and fixed several hundred bugs not addressed by Baldurdash, and have a long list of other bugs on which we're working. We consolidate bugfixes from several existing mods. The fixpack is actively supported by a team, which means we can respond faster to bug reports and also that the project will continue even if one member disappears or loses interest.

What is G3, and where can I find a link to it?

G3 is short for The Gibberlings Three. While G3 may be hosting, it's important to note that this a collaborative effort of modders from a broad slice of communities including Forgotten Wars. We hope to make the project public very soon.

Can I just reply in this thread if I am interested?

Yes.

Edited by CamDawg, 08 April 2005 - 11:10 AM.

[Caedwyr]

A couple more questions that may be asked.


Are there any advantages for a modder to use this fixpack over Baldurdash, and if I do use it, will the mod that I make be compatible with people using Baldurdash?

[SimDing0]

Are there any advantages for a modder to use this fixpack over Baldurdash, and if I do use it, will the mod that I make be compatible with people using Baldurdash?

A mod's compatibility is a function of the modmaker, not the platform he builds on.

I suggest that for all purposes, the fixpack should be treated in the same regard as the official patch.

[Sir BillyBob]

I suggest that for all purposes, the fixpack should be treated in the same regard as the official patch.

Agreed, as long as this stays a fixpack and doesn't become a "tweak" pack or other "enhancement" to the game.

[CamDawg]

We're imposing strict fix/non-fix rules with a peer review process.

[CamDawg]

Many of the fixes are to files stored in the save game (areas, global creatures, etc.). If you have mods that won't install (anything non-WeiDU) you would need to reinstall the game, otherwise you could just uninstall the mods, apply the fixpack, then reinstall the mods.

Edited by CamDawg, 09 April 2005 - 05:08 AM.

[SimDing0]

That means starting a new game to get the maximum benefit. It doesn't require a complete reinstall, and you'll still see some of the fixes if you install it mid-game.

[King Diamond]

Guys! You're talking too much. Just give ppl a shortcut to download.... :w00t:

Edited by King Diamond, 09 April 2005 - 05:16 AM.

[SimDing0]

We don't release half-working products. While we're fairly sure it's not going to be full of bugs, it's also important to have it thoroughly tested before public release to ensure proper functionality.

[SConrad]

We don't release half-working products. While we're fairly sure it's not going to be full of bugs, it's also important to have it thoroughly tested before public release to ensure proper functionality.

...and, besides this, we're going to include even more fixes on our immensely long to-do list before releasing the first real version.

[King Diamond]

What bugs are you talking about? I could think only about tp2 script bugs....but they could be checked very easy - right after the installation.
Because the patching is so obvious. If something need to be changed and it changed after the installation what are you going to check more? If wrong script name has changed to a proper one what "bug" could appear there?
That is a meaning of a real bug-fixing patch - to fix obvious things.

[SimDing0]

What bugs are you talking about? I could think only about tp2 script bugs....but they could be checked very easy - right after the installation.

If the fixpack breaks something. I don't believe it will, but I don't find it acceptable to release until we're absolutely sure.

[Caedwyr]

A wonderful side effect of coding, is that fixing one bug can often create entirely new bugs that you didn't expect. Just ask Microsoft. There are lots of jokes around about how certain bigfix patches just fix a few bugs and introduce a whole lot more.

[Yacomo]

A wonderful side effect of coding, is that fixing one bug can often create entirely new bugs that you didn't expect.  Just ask Microsoft.  There are lots of jokes around about how certain bigfix patches just fix a few bugs and introduce a whole lot more.

There is a running gag around programmers, I hope I translate it correctly:

Every program has at least one line of code too much and every program contains at least one bug. From this you can follow using mathematical induction that you can reduce every program to one line of code that is buggy

Which essentially means, no matter how hard you try, there will always be that one last nasty bug

But trying hard is a virtue, so please do not feel discouraged!

[CamDawg]

We've now completed our latest build and testing is commencing. The more playtesters, the better, so if anyone else is interested let us know.

[Cantrip]

Question: Are you aware of this - http://dracolisk.net...ewforum.php?f=2 ?
If so, why not recruit the guy?

Sorry if I'm bothering you...

Edited by Cantrip, 07 May 2005 - 08:31 AM.

[drake127]

Question: Are you aware of this - http://dracolisk.net...ewforum.php?f=2  ?
If so, why not recruit the guy?

Sorry if I'm bothering you... 

I would not aware of me. I am only one and small. And at present I have no time  - that question will be actual after 16th of May (my leaving exams).

I have only several suggestions for G3: make your fixes clear and short, without file's dependencies and check these fixes immediately when you create them.

Edited by drake127, 07 May 2005 - 08:40 AM.