It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like:Chrome,Firefox,Internet Explorer orOpera

Having loved BG1 back in the day, I recently built the GoG "enhanced" installation that includes BG1, ToTSC, BG2 and ToB, running under the BG2 engine, and began a new play-through. Not long after starting, I ran into a problem that I remember encountering the first time through: if you take on Minsc and his quest, but complete most of the first two chapters before setting off for the Gnoll Stronghold to rescue Dynaheir, you run out of time, Minsc goes bonkers and you have to kill him. This usually happens around day 20 of game time.

This time, I was determined to finish the Minsc quest, but my earliest saves were too recent to allow me to make the stronghold before Minsc blew up. Fortunately, a bit of judicious editing of the save game file can extend the time available to finish Minsc's quest before he loses it.

This solution requires the worthy Infinity Engine Savegame Editor, which is an older .NET application (1.1) written for Windows XP. I've had no problems installing and running it under 32-bit Windows 7. Have a spreadsheet or calculator handy as well.

1. Run the IESE and select your game type. Select Baldur's Gate if you've installed BG1 only; Shadows of Amn if you're playing BG1 under the BG2 engine.

2. Click File/Open and load the latest save game prior to when Minsc loses it (any save game will work, but using the latest means you won't lose much ground).

3. Click Edit/Party Infos. On the Global Data tab, note the Value field in the Time section. It should contain a moderately large number, which represents elapsed time in the game in some unknown scale (roughly, but not exactly, game minutes * 5). In my 20 hour, 20 minute save game, the Time Value was 150061.

4. Click the Global Variables tab, and locate the variable named MINSC. Its value is a somewhat larger number that represents the absolute time in some more precise scale (roughly, but not exactly, Time Value * 15) when Minsc will lose his marbles. I believe this variable is assigned when Minsc joints the party, and is calculated as (join time + some duration * some factor), as it remains constant once assigned.

5. All that's needed to extend your quest time is to assign a new value to the MINSC global variable. Take the Time Value from step 3), double it and multiply by 15:

150061 * 2 * 15 = 4501830

In game terms, this gives you roughly the same amount of time as has already elapsed since Minsc joined the party to finish the Dynaheir quest. Click the Set button, enter your new Value and click OK.

6. Click File/Save As, enter a new Savegame name, and click Get New Number, then Save, to avoid overwriting any of your prior saves. This way, if something goes wrong, you can always return to your original saved game.

Obviously, this technique is open to abuse, and I haven't attempted to discover the outer limits. My goal wasn't to radically change the outcome or order of quests, just to buy more time to finish a single quest line. Caveat emptor, and enjoy!
Post edited December 01, 2012 by santaDog78
Isn't it easier to just rescue Dynaheir in time?
Post edited December 01, 2012 by PetrusOctavianus
PetrusOctavianus: Isn't it easier to just rescue Dynaheir in time?
Yes and send her out front the first chance you get let those pesky knolls finish her off. Party gets Minsc without his pain of a witch Dynaheir. ;-)
PetrusOctavianus: Isn't it easier to just rescue Dynaheir in time?
Hindsight is always 20:20. But in case you didn't, here's a fix.
Thanks for the post dog, I'm sure it will be useful to someone new to the game.

I wanted to add some info in case it makes the process easier. Just a warning though, I haven't messed enough with it to know any shortcomings- only a little preliminary testing done.

In case you are more comfortable using the console than 3rd party programs, such as me, you can read the MINSC variable with the following command:


and then to assign a new value to it use:


where XXXXXX is the number you calculated above or, my guess, just a number sufficiently larger than the one you got from the first command.