The Gibberlings Three Debugging Suite for Baldur's Gate II

A Gibberlings Three Mod
Author: CamDawg, aka 'Cam' Camagna
n the web: Home page and discussion forum

Version 3 - Check for the most recent version
Languages: English
Platforms: Windows and Mac OS X


In the course of BG2 Fixpack development, several errors kept cropping up repeatedly--so much so that it became time-efficient to write some automated checking tools. With some polish, these tools are now ready to be released independently so that modders can use them to diagnose issues in their own mods.


The Debugging Suite is designed to work with Baldur's Gate II with or without the Throne of Bhaal expansion pack. Note that the suite doesn't actually alter any game files and leaves no entry in the WeiDU log, so that it can be used at any point in the install order, as many times as needed. If there is interest for the Suite on other platforms (BG, IWD, etc.) it can be developed. For the most part, the file formats are the same so certain components may work on non-BG2 variants of the Infinity Engine, though I may not be able to actively support them.


The G3 Debugging Suite is packaged and installed with WeiDU and is distributed as a self-extracting archive. To install, simply double-click the archive and follow the instructions on screen.

Alternatively the files can be extracted from the archive using WinRAR. If properly extracted, you should have a G3_Debugging_Suite folder and Setup-G3_Debugging_Suite.exe in your BG2 folder. To install, simply double-click Setup-bg2fixpack.exe and follow the instructions on screen.

Please run Setup-G3_Debugging_Suite.exe in your BG2 folder to run and re-run the suite as needed.

Mac OS X
If the mod was previously installed, uninstall it before extracting the new version. The G3 Debugging Suite is packaged and installed with WeiDU. To install, simply extract the contents of the mod into your BG2 folder. If properly extracted, you should have a G3_Debugging_Suite folder, Setup-G3_Debugging_Suite, and Setup-G3_Debugging_Suite.command in your BG2 folder. To run or re-run, simply double-click Setup-G3_Debugging_Suite.command and follow the instructions on screen.


Each different component leaves no log record in weidu.log and does not modify any files--it generates a purely informational report. Any error messages are also echoed to the install screen. An explanation of what is checked and the possible error messages for each component is listed under each component's description.Two very important points need to be made:

  1. This is the equivalent of running a fine-toothed comb over your files. The Suite can (and will) generate false positives so it's important that you verify warnings as legitimate issues that need to be fixed.
  2. Many of the error messages generated will likely have little to no effect on your game. That being said, the tool can still be incredibly useful in tracking down file anomalies.

The Suite also has a built-in tool to limit the files checked. At the top of the t2 is a block in which you can set your modding prefix:

  OUTER_SPRINT "prefix" ""

To have it only scan files that start with CD, for example, use this:

  OUTER_SPRINT "prefix" "CD"

All file checks will be restricted by the prefix set by this line. To scan all files, leave the value empty, as it is in the first example (this is also the default value of the Suite when it's downloaded).

Area Checker
Output of this check can be found in G3_Debugging_Suite/debugger_area_checker.log. This component scans all area files present for common errors, such as bad indices, references to non-existent files, trap errors, etc. The following checks are performed, and listed along with their generated error message:

Creature Checker
Output of this check can be found in G3_Debugging_Suite/debugger_creature_checker.log. This component will check several potential issues in creature files. The inventory is only given minimal treatement; please use the Creature Invenory Checker component for in-depth inventory checks.

Creature Inventory Checker
Output of this check can be found in G3_Debugging_Suite/debugger_creature_inventory_checker.log. Originally available separately, this has been rolled into the Suite.

Item Checker
Output of this check can be found in G3_Debugging_Suite/debugger_item_checker.log. This component performs basic checks against item files.

Spell Checker
Output of this check can be found in G3_Debugging_Suite/debugger_spell_checker.log. This component performs basic checks against spell files.

Contact Information

CamDawg created this tool. You can find out more about the G3 Debugging Suite by visiting the Debugging Suite forum or the project page. Visit the Gibberlings Three Forums for information on this and any other Gibberlings Three mods on which we may be working.

Thanks and Acknowledgements

First, something like this would not be possible without the incredible research and development that has resulted in resources like the IESDP and tools like DLTCEP, Near Infinity, and WeiDU. This suite certainly duplicates some of the error checking from other tools, but I believe it's still beneficial as a standalone suite.

Second, a big thanks to the wonderful community at The Gibberlings Three. The atmosphere continues to be wonderful and drives me to keep modding and producing.

Tools Used in Creation
WeiDU by Wes Weimer and the bigg
Near Infinity by Jon Olav Hauglid
IESDP maintained by igi

Credits and Copyright Information

This suite may not be sold, published, compiled or redistributed in any form without the consent of its authors. The G3 Debugging Suite is ©2006.

Version History

Version 3 - March 1, 2010

Version 2 - February 19, 2007

Version 1 - October 3, 2006