BG2 Fixpack Testers Needed

[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.

edit: And thanks for pinning this. [img]smile.gif[/img]

[ 04-06-2005, 06:51 AM: Message edited by: CamDawg ]

[CamDawg]

We've completed our latest build and are still soliciting testers. I wanted to clarify some points based on feedback from the previous announcement.

Q. So is this supposed to replace Baldurdash, or will I have to install Baldurdash as well? What about Baldurdash's Game Text Update?
A. 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. The game text update will be available as a separate component, since it remains English-only.

Q. Why should I install this instead of Baldurdash?
A. 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.

Q. What is G3, and where can I find a link to it?
A. G3 is short for The Gibberlings Three, an active modding community that can be found at www.gibberlings3.net. While G3 may be hosting, it's important to note that this a collaborative effort of modders from a broad slice of communities. We hope to make the project public very soon.

Q. Can I just reply in this thread if I am interested?
A. Yes. You can also email CamDawg at webmaster@gibberlings3.net.

Q. 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. A mod's compatibility is a function of the modmaker, not the platform he builds on. We do add a separate component designed to assist modders by cleaning up some of the BG leftover code, expanded IDS files, and other goodies such as assigning area scripts to areas without them, and so on. All of these changes are checked to make sure they do not affect game play or the bug fixes at all.

Q. How do you identify and check bugs?
A. The greatest advantage to a team approach is that we have very open-ended discussions not only about whether something is a bug, but what's the best method to fix it. Every proposed fix is scrutinized, and fixes that are not absolutely certain are deferred to another optional component to ensure the 'purity' of the core fixes.