Frequently Asked Questions
General
Installation
Playing the Modification
Uninstallation
Compatibility and Other Modifications
Miscellaneous
How does Baldur’s Gate Trilogy fit in with other modifications for Baldur’s Gate II out there?
Bardez’s Baldur’s Gate Trilogy, BGT_MK3_112, became incorporated with the mega-modification known as The Big Picture, which combines a number of large modifications for Baldur’s Gate II (The Darkest Day, Shadows over Soubar, and Tortured Souls) together in order to allow the gamer to play through all the major modifications at the same time. Subsequently, the conversion of the TeamBG mod Dark Side of the Sword Coast for use with this platform as well as the creation of modifications made specifically for Baldur’s Gate Trilogy, such as Northern Tales of the Sword Coast and Secret of Bonehill, made the so-called BP-BGT a humungus conglomeration of modifications that richly expanded the Baldur’s Gate universe.
Today, BP-BGT is an obsolete term, and the mega-modification refers to a installation of modifications containing at least two of Baldur's Gate Trilogy-WeiDU (BGT-WeiDU), The Darkest Day (TDD), Shadows Over Soubar (SoS), Tortured Souls (TS - BP version), Check the Bodies (CtB), Region of Terror (RoT), Never Ending Journey (NeJ), and The Big Picture (BP).
If Bardez made Baldur’s Gate Trilogy, why should there be Baldur’s Gate Trilogy-WeiDU (BGT-WeiDU)?
Stitching together a large number of modifications that affect all aspects of Baldur’s Gate II and are made by different authors generates many compatibility problems between modifications. This arises because often the same files are patched and overwritten, meaning that one change replaces another and the original change disappears forever. Also, large modifications usually come with a load of bugs that can be difficult to locate file-wise and fix.
You might also expect that large modifications, especially one such as Baldur’s Gate Trilogy, which adds most of the material from Baldur’s Gate and Tales of the Sword Coast to Baldur’s Gate II, require large installation packages, and therefore downloading large files could be tedious and slow for some gamers with aging internet connections. BGT-WeiDU aims to address these problems by converting the installation process into the Weimer Dialogue Utilities (WeiDU) platform, a powerful tool that can solve compatibility issues and allow bugs to be fixed quickly and efficiently. BGT-WeiDU also draws most resources from the original installation of Baldur’s Gate and Tales of the Sword Coast to greatly reduce the size of the download.
You said BGT-WeiDU is mostly faithful to the original. What are the major differences between this modification and the original Baldur’s Gate and Tales of the Sword Coast?
There are a number of new features introduced by BGT-WeiDU, many of them utilise the advantages of the Baldur’s Gate II engine and the compatibility features of WeiDU. New features are described in the Introduction section.
Additionally, many bugs inherent in Baldur’s Gate and Tales of the Sword Coast were fixed. A list of fixes currently incorporated into BGT-WeiDU can be found here.
How does BGT-WeiDU incorporate Baldur’s Gate and Tales of the Sword Coast into my Baldur’s Gate II game?
BGT-WeiDU converts Baldur’s Gate and Tales of the Sword Coast resources and installs them to your Baldur’s Gate II directory. Holistically, the conversion is mostly faithful to the original. Technically, the installation imports by duplication most of the core resources of the modification directly from your existing Baldur’s Gate and Tales of the Sword Coast. Therefore, your original Baldur’s Gate and Tales of the Sword Coast is unaffected. You may choose to uninstall Baldur’s Gate and Tales of the Sword Coast after installation of BGT-WeiDU to free up some disk space.
I want to install BGT-WeiDU. Should I have clean copies of Baldur’s Gate, Tales of the Sword Coast, Shadows of Amn, and Throne of Bhaal installed?
It is critical that you have a clean copy of Baldur’s Gate and Tales of the Sword Coast installed that contains no modifications whatsoever (including Baldurdash fixes). Failure to do this will generate numerous unpredictable problems in your BGT-WeiDU installation.
For Shadows of Amn and Throne of Bhaal, you may have modifications pre-installed. See below for more details on using other modifications with BGT-WeiDU.
How long does the installation process for BGT-WeiDU take?
Installation time will depend on the abilities of your system, but as a rough estimate installation may take anywhere from 20 minutes to 1 hour. You will receive prompts informing you of what is occurring during installation. You will also be prompted at the end of the installation process.
I have BGT-WeiDU installed now. How do I start Baldur’s Gate from Candlekeep?
When you start Baldur’s Gate II, you will arrive at the main menu where you would normally choose to play Shadows of Amn or Throne of Bhaal. Notice that the Shadows of Amn button has been replaced by a Baldur’s Gate button. Click on this button, and then click Single Player, then New Game. This will take you to the character generation screen, where you will create a level 1 character or import an existing character. Your character will then start in Candlekeep.
Can I still play Shadows of Amn and/or Throne of Bhaal with BGT-WeiDU installed?
Certainly.
For Shadows of Amn, click on the Baldur’s Gate button in the main menu, and then Single Player. You will notice that the Tutorial button has been replaced by a button labelled ‘New BG2 Game’. Click on this button, and click on the New BG2 Game button on the dialog box to go to the character generation screen, where you will create a character that will have the appropriate amount of experience for Baldur's Gate II, or import an existing character. When finished, you will start in Irenicus’ Dungeon.
The method to start a Throne of Bhaal game has not changed.
How does continuity in BGT-WeiDU work?
If you start a game in Candlekeep, you play through the original Baldur’s Gate until you defeat Sarevok. The Tales of the Sword Coast areas are accessible whenever you like by travelling north of Wyrm’s Crossing, when that area becomes available. Defeating Sarevok will not end the game, but will allow you to play on. Talk to Belt at the Duchal Palace, and he will give you a new assignment. This will start a cutscene where you are ambushed by the Shadow Thieves and are taken to Irenicus’ Dungeon.
Additionally, joinable non-player characters that appear in both Baldur's Gate and Shadows of Amn conditionally keep their attributes upon transition to Shadows of Amn depending on the fate that you left them in Baldur's Gate. Edwin, Imoen, Jaheira, Minsc, and Viconia will keep their attributes and appearance from Baldur's Gate if they are alive and are in your party when you talk to Belt after the defeat of Sarevok. Otherwise, they will present themselves in Shadows of Amn as if BGT-WeiDU was not installed.
Baldur’s Gate and Tales of the Sword Coast had its fair share of bugs. In this conversion, do these bugs still exist?
BGT-WeiDU attempts to address the most significant bugs that existed in the final versions of Baldur’s Gate and Tales of the Sword Coast. A list of fixes currently incorporated into BGT-WeiDU can be found here.
Do I have to restore dialog.tlk after I uninstall BGT-WeiDU?
No, you do not have to. However, if you do not, it could be problematic if you start installing other modifications and using saved games in different combinations. The safest way to uninstall BGT-WeiDU to avoid such problems is to restore dialog.tlk.
Why should I manually restore dialog.tlk after I uninstall BGT-WeiDU?
BGT-WeiDU alters a large number of references inside your Baldur’s Gate II dialog.tlk file, the file that contains almost all the text in the game. A limitation of WeiDU and the way that the BGT-WeiDU installation is designed is that it generates the modified dialog.tlk file when the installation/uninstallation process finishes. This does not allow the running of a batch file that will automatically restore your dialog.tlk. Therefore, the only way that it can be restored is by copying that backup to its original location manually.
Can I play BGT-WeiDU with other modifications?
Yes. BGT-WeiDU does not just retain, but improves compatibility with the mega-modification. For other modifications, no one can guarantee that every modification is compatible with another. BGT-WeiDU compatibility is no exception. However, possible compatibility issues between BGT-WeiDU and other modifications are actively analysed. A BGT-WeiDU compatibility list is available here. The most up-to-date compatibility list can be found online.
How do I install the mega-modification with BGT-WeiDU?
Mega-modification installation order is in a state of flux. Therefore, this readme will not tell you in what order to install such modifications. However, there is a forum dedicated to mega-modification installations, which you can access here.
How do I install other modifications with BGT-WeiDU?
As a general rule, install Baldur's Gate 2 Fixpack first, if you plan to use it, then install the mega-modification, BGT-WeiDU, and then all other modifications on top. Specifics in installation order are in a state of flux, so more detailed advice cannot be given.
If you want to play BGT-WeiDU without the mega-modification but with other modifications, install Baldur's Gate 2 Fixpack first, followed by BGT-WeiDU, and then all other modifications on top.
Be mindful of compatibility issues. Current compatibility between BGT-WeiDU and other modifications are listed here. Possible compatibility between sets of other modifications should be queried to their respective authors.
I would like to translate this modification. How do I do it?
To translate BGT-WeiDU into a different language, follow the steps listed below:
- Go to your BGT-WeiDU installation directory, and switch to the bgt\language directory
- Create a copy of the English directory and rename it to the language you wish to translate to
- In your renamed directory, translate all files present as follows:
- Switch to the bgt\help directory
- Make a copy of [english]bgtreadme.htm and [english]postinstall.htm and rename the portion that refers to the language
[english]bgtreadme.html -> [castilian]bgtreadme.html
[english]postinstall.html -> [castilian]postinstall.html
- Translate sections 1, 2, 3, 4, 5, and 9 of bgtreadme.htm only, and all of postinstall.htm
- Switch to the bgt\worldmap\english directory, make a copy of worldmap.tra and translate as above for .tra files.
Treat ### as a space, but make sure you leave ### present. If you need to include spaces, replace them with ###.
@1001 = ~English###English~ -> @1001 = ~Castiliano###Castiliano~
@-1001 = "English###English" -> @-1001 = "Castiliano###Castiliano"
- Package your renamed directory, readme file, postinstall.htm and worldmap.tra
- Either post the file on the mod forum, or send a private message (PM) to Ascension64 at the Spellhold Studios forums, who will give you an e-mail address to send the package to
- Expect the language to be included for the next release
I have other questions.
Come to the Spellhold Studios forums, register for free as a member, and post your questions online.
•BACK TO TOP
Troubleshooting
Fatal Installation Errors
I have a custom install of Baldur's Gate and Tales of the Sword Coast patched to version 5512, or Baldur's Gate: The Original Saga, but the installation does not accept the directory that I type in.
The most likely scenario is that your installation discs for Baldur's Gate and Tales of the Sword Coast or Baldur's Gate: The Original Saga are scratched, and the installation did not copy over all the files.
- Check that all of these files are present in the \data directory of your Baldur's Gate I installation directory. If any are missing, try and manually copy the file into the correct directory from the original disc.
- AREA000A.bif
- AREA000B.bif
- AREA000C.bif
- AREA000D.bif
- AREA000E.bif
- AREA000F.bif
- AREA000G.bif
- AREA000H.bif
- AREA010A.bif
- AREA010B.bif
- AREA020A.bif
- AREA020B.bif
- AREA030A.bif
- AREA030B.bif
- AREA040X.bif
- AREA050D.bif
- AREA060A.bif
- AREA070A.bif
- AREA080A.bif
- AREA080B.bif
- AREA090X.bif
- AREA0100.bif
- AREA110A.bif
- AREA110B.bif
- AREA110C.bif
- AREA120A.bif
- AREA120B.bif
- AREA130A.bif
- AREA140A.bif
- AREA140B.bif
- AREA160X.bif
- AREA180A.bif
- AREA180B.bif
- AREA180C.bif
- AREA180D.bif
- AREA180E.bif
- AREA190X.bif
- AREA0200.bif
- AREA210X.bif
- AREA220X.bif
- AREA230A.bif
- AREA230B.bif
- AREA260A.bif
- AREA260B.bif
- AREA260C.bif
- AREA0300.bif
- AREA320X.bif
- AREA330A.bif
- AREA330B.bif
- AREA330C.bif
- AREA330D.bif
- AREA340X.bif
- AREA360X.bif
- AREA380X.bif
- AREA390X.bif
- AREA0400.bif
- AREA400X.bif
- AREA410X.bif
- AREA420X.bif
- AREA440X.bif
- AREA450X.bif
- AREA470X.bif
- AREA480X.bif
- AREA490X.bif
- AREA500X.bif
- AREA510X.bif
- AREA520X.bif
- AREA540A.bif
- AREA540B.bif
- AREA540C.bif
- AREA540D.bif
- AREA550X.bif
- AREA0600.bif
- AREA0700.bif
- AREA0800.bif
- AREA0900.bif
- AREA1100.bif
- AREA1200.bif
- AREA1300.bif
- AREA1400.bif
- AREA1600.bif
- AREA1700.bif
- AREA1800.bif
- AREA1900.bif
- AREA2100.bif
- AREA2200.bif
- AREA2300.bif
- AREA2400.bif
- AREA2600.bif
- AREA2700.bif
- AREA2800.bif
- AREA2900.bif
- AREA3000.bif
- AREA3100.bif
- AREA3200.bif
- AREA3300.bif
- AREA3400.bif
- AREA3500.bif
- AREA3600.bif
- AREA3700.bif
- AREA3800.bif
- AREA3900.bif
- AREA4000.bif
- AREA4100.bif
- AREA4200.bif
- AREA4300.bif
- AREA4400.bif
- AREA4500.bif
- AREA4600.bif
- AREA4700.bif
- AREA4800.bif
- AREA4900.bif
- AREA5000.bif
- AREA5100.bif
- AREA5200.bif
- AREA5300.bif
- AREA5400.bif
- AREA5500.bif
- Areas.bif
- ARMisc.bif
- CHAAnim.bif
- CHASound.bif
- CREAnim.bif
- Creature.bif
- CRESound.bif
- Default.bif
- Dialog.bif
- Effects.bif
- Gui.bif
- Items.bif
- MPCREANM.bif
- MPGUI.bif
- MPSounds.bif
- NPCSound.bif
- OBJAnim.bif
- RndEncnt.bif
- scripts.bif
- SFXSound.bif
- Spells.bif
- AREA050A.bif
- AREA050B.bif
- AREA050C.bif
- AREA100A.bif
- AREA150A.bif
- AREA200A.bif
- AREA200B.bif
- AREA0500.bif
- AREA1000.bif
- AREA1500.bif
- AREA2000.bif
- ExArMaps.bif
- ExPAreas.bif
WeiDU tried to delete files that did not exist and asked me whether to install the modification again.
You may not have a clean installation of Baldur’s Gate and Tales of the Sword Coast and/or Baldur’s Gate: Throne of Bhaal.
- When the installation prompts for install again, quit the installation
- Restore dialog.tlk as described in the Installation and Uninstallation section of this file
- You have just reverted the installation process. Do not try to install again immediately.
- Try reinstalling Baldur’s Gate and Tales of the Sword Coast and/or Baldur’s Gate: Throne of Bhaal without any modifications and re-install BGT-WeiDU.
- If you have other modifications installed, try uninstalling those and re-install BGT-WeiDU.
- If you still experience problems, post the files SETUP-BGT.DEBUG and SETUP-BGTDOS.DEBUG (if it exists), located in your Baldur’s Gate II installation directory, in the mod forum
Windows gave me an exception error detailing _WeiDU.exe or tis2bg2.exe
The DOS prompt returned the error "WeiDU: ZLIB: Warning! Problem decompressing block." in some cases.
These are known issues that occur if you did not follow Step 2 of the Installation section.
- Allow the installation finish. This is critical. Uninstall BGT-WeiDU as described in the Uninstallation and Re-installation section.
- Restore dialog.tlk.
- Follow the installation procedures correctly.
Minor Installation Errors
During the installation, I constantly get errors saying ‘There is no disk in your drive’.
This occurs if you did not follow Step 2 of the installation procedures.
- If you have not installed yet, or as you read this the installation is halted directly after you were asked to enter your Baldur's Gate and Tales of the Sword Coast directory with the disk check, abort the installation immediately.
- As you read this, if the installation is halted any time after you were asked to enter your Baldur's Gate and Tales of the Sword Coast directory, press 'Cancel' to every single prompt that occurs, and allow the installation to finish. When the installation is finished, uninstall BGT-WeiDU and restore dialog.tlk.
- Follow the installation procedures correctly without omitting Step 2.
•BACK TO TOP
Credits
Core
Ascension64 (project leader): bug-testing, coding, distribution
King Diamond: bug-testing, coding
Waywocket: menu screens
Yacomo: menu screens
Translations
Castilian/Spanish (http://www.clandlan.net): Ghildrean, Immortality, Lisandro, Memnoch, Saemon
Czech: Lyrick, PostTrauma
French: Anomaly
German: OldVeteran, RubberDuck, weigo
Italian: al17, Gemini82, melkor_morgoth75, Salk
Korean: Inesius, web2air, Shi woo, Whiteraven
Polish: dragonian, Joneleth, Promilus, Valfar (aka Evendur), yarpen
Russian: Badgert, iopden, King Diamond, Kulyok, Vlad
Simplified/Traditional Chinese (http://trow.cn/forum/): Delmarey, fc666, good0593, Kinkairy, moon_cloud, 猫猫伸懒腰
Kudos
- Many thanks to Bioware and Black Isle Studios for creating such a great RPG
- Many thanks to Andyr and the Tutu team for providing a template for the sorting of journal entries
- Many thanks to Bardez who created the original Baldur's Gate Trilogy and for permission to convert this mod to WeiDU
- Many thanks to CamDawg and the TuTu Tweak Pack team for providing a template for the revised map notes
- Many thanks to Corvias for the creativity in making the Baldur’s Gate Trilogy icon
- Many thanks to Douglas Boling for the STRINGS command file
- Many thanks to Elve for work on the full Baldur's Gate/Shadows of Amn/Throne of Bhaal music
- Many thanks to Horred the Plague, hlidskialf, Seanas, Sir BillyBob, and all the testers who have worked to make the game as smooth as possible
- Many thanks to Riklaunim of the Polish BG community for allowing the inclusion of his Polish BG1 font utility
- Many thanks to Taimon for his songlist hack and finding a solution to duplicate characters in GAM files
- Many thanks to Turambar for his work in overhauling the installation to compatible with Linux systems
- Many thanks to weimer for creating the WeiDU utility for excellent modification installation
- Many thanks to Yacomo for the MOSUnpack utility and the World Map modification
- Many thanks to you and all the other players that who have contributed to the completeness and the enjoyment in developing this modification
•BACK TO TOP
Legalese
BALDUR’S GATE, BALDUR'S GATE: TALES OF THE SWORD COAST: © 1999 BioWare Corp. All Rights Reserved. Baldur's Gate and Baldur's Gate Tales of the Sword Coast are trademarks of TSR, Inc., a subsidiary of Wizards of the Coast, Inc., and are used by Interplay under license. The BioWare Infinity Engine is a trademark of BioWare Corp.
BALDUR'S GATE II: SHADOWS OF AMN, BALDUR’S GATE II: THRONE OF BHAAL: © 2000, 2001 BioWare Corp. All Rights Reserved. Baldur's Gate, Throne of Bhaal, and Shadows of Amn are trademarks owned by Wizards of the Coast, Inc. and are used by Interplay under license. All Rights Reserved. The BioWare Infinity Engine is a trademark of BioWare Corp. All Rights Reserved.
USE THIS MODIFICATION AT YOUR OWN RISK. This modification is not developed, supported, or endorsed by BioWare Corp., Interplay, or Black Isle. All images and contents of this mod are © BioWare Corp., Interplay, Black Isle or Wizards of the Coast, Inc.
This is a community modification, created as a hobby for free. You can distribute among your peers as much as you like. However, please display good faith and credit the authors of the modification if you intend to modify the BGT-WeiDU package in any way or use any part of this modification as a template to create part/all of a modification/fixpack/tweak that you intend to release to the community.
•BACK TO TOP
