What's this forum for?
This is not a Bugs forum.
If you've encountered a gameplay issue that you can reproduce, post a bug report in the Bugs forum for the appropriate game. The Troubleshooting forum is here to help you get your game working again when it stops working and you don't know why.
Mods broke your game? Post about it here. Edited saved game causing a crash? Post about it here. The community is here to help. This thread offers some solutions to common problems and answers to frequently asked questions. If you don't find the answer you're looking for in this thread, there's a good chance someone else in the community will be able to help.
What happened to the platform-specific forums? What if I'm having a problem with my iPad?
We've consolidated the platform sections to help us identify issues more efficiently. If your issue is something within the game, follow the steps described below to post a bug report in the forum for your game. If the issue is related to general performance on your system, start a thread here; the community has a wealth of experience and information with regard to a variety of devices, and we'll be more than happy to help fix the issue.
You can still view the old platform-specific forums here
, but no new posts or threads will be created there.This is not a bugs forum.
This section is just for troubleshooting technical issues with your hardware setup. If you are experiencing a reproducible bug in the game itself, please follow the instructions for reporting a bug normally.
What's the Best Way to Avoid Losing Progress?
Save your game often with unique slots. While this does take some space on your drive or tablet, it also allows you to go back to any point, should you realize you missed something or need to go back and fix an issue in your game.
When saving your game, use the quick save slot to save minor progress only. Use the regular saved game slots periodically to save progress throughout the game, and keep those saves around throughout your adventure. You never know when reverting to a save a few minutes back would save you hours of playtime and effort.
I found a bug! How do I report it?
First of all, thank you for helping to make these games even better! To report a bug you’ve found in one of these games, follow these steps:
Step 1: Check for Mods
Make sure that you have no mods installed. If you do, try to reproduce the issue with a new game on a clean installation. We can’t fix issues with mods, and it’s often hard to tell where a bug came from if it’s only being reported on a modified game. If you can reproduce the issue with no mods installed, move to Step 2.
(If it turns out the issue was caused by one or more of your mods, check out the Modding forum and see if the mod's author can help you identify the cause of the problem. Your issue may help a mod designer/maintainer make their mod better!)
Step 2: Reproduce the issue.
If it’s a gameplay issue, try to go through the same steps you took to make it happen. The simpler the steps are the better, but it’s important to be precise so that we can isolate the cause and fix the problem. Be sure to create a saved game just prior to the steps you took, so that we can retrace those steps exactly.
If the issue is related to graphics or text, take a screenshot. On Windows and Mac, pressing PrntScrn during play will generate a screenshot in your Documents\Baldur’s Gate – Enhanced Edition\ScrnShots folder; you don’t need any external programs to make it work.
Step 3: Submit a Bug Report
Visit our bug-tracking site on Redmine and create a ticket using the "Add an Issue" feature. Here are the links to the appropriate projects:
- BG:EE - http://support.baldursgate.com/projects/bg-ee-bugs
- BGII:EE - http://support.baldursgate.com/projects/bgii-ee-bugs
Note that if our QA staff determines that the behavior you describe is working as intended, they may change the Tracker type to "Feature". This doesn't mean your ticket won't be reviewed; it just means that it will be reviewed as a feature request (which helps us manage our internal processes).
Following the instructions for bug report format is essential; without a proper list of steps and a saved game, it can be just about impossible for us to locate and reproduce the issue, which will naturally interfere with our efforts to fix it.
How do I change the game’s speed?
Baldur’s Gate’s speed is determined by a setting in Baldur.ini, one of the files included with the game upon installation. You can find this file in the same directory as your saved games; see the platform-specific posts below for its specific location.
The line you’re looking for here is as follows:
'Program Options', 'Maximum Frame Rate', '30',
In that line, 30 is the default frames per second for everything that happens in-game. Increasing that number will make animations play faster; it will also make everything else in the game speed up, which may affect gameplay and cutscenes. Change this setting at your own risk.
What is this “Console” everyone keeps talking about, and how do I use it?
Baldur’s Gate offers an in-line command system called CLUA Console, which can be used to spawn creatures, items, gold, experience points, or even variables for quests or NPCs. It can perform other actions as well, such as revealing the current map or moving you to a different location. The mode exists for testing purposes and debugging, which is why it’s called “Debug Mode” in the system. To enable Debug Mode and the Console, you’ll need to find your Baldur.ini file in your local game files and open it with a text editor; I recommend WordPad.
When you’ve got the file open, find this line:
INSERT INTO options ROWS (
And add the following in the line after it:
'Program Options', 'Debug Mode', '1',
Then save the file and start the game. To bring up the console, press Ctrl-Space. Some basic commands are listed below; there are other more advanced commands that we use for deeper testing, but these are a decent start.
This moves the selected character(s) to the area, based on its area file name, such as AR1301. Be sure to put the area file name in quotes within the parentheses; also be sure to have your entire party selected when you enter this command, or you may leave one or more of your party members behind.
This command reveals the entire map for the current area. Note that it doesn’t remove the fog of war; if a creature is out of your field of vision it will still remain hidden.
This spawns a creature, based on its creature file name, to the center of the screen (or nearest valid point). If you’re spawning a creature you know will be hostile, you may want to pause the game before entering this command for the safety of your party.
This spawns an item, based on its item file name, or a stack of the same item, in the inventory of the current party leader.
This sets the Experience Point total for the currently selected character or characters to the value noted in parentheses. Note that this sets the total, rather than adding a value to your current experience points.
In contrast with SetCurrentXP, this command adds an amount of gold to your party’s total based on the number in parentheses.