Ironworks Gaming Forum - View Single Post

SixOfSpades · 12-23-2004, 02:01 PM

First thing to do when you hit a bug: Reload. Try your Autosave first, then your next oldest Save, no matter how far back it is.

LennonCook's mention of walking back out into the hallway is spot-on. Sometimes, script-driven NPCs aren't able to walk if they aren't in the party's sight range (such as Kamir in the Graveyard District). Don't ask me why.

If you absolutely have to cheat, the Guild Contact's creature name is BODFGT03.

12-23-2004, 02:01 PM	#9
SixOfSpades Dracolisk Join Date: September 16, 2001 Location: Bellingham, WA, USA Age: 48 Posts: 6,901	First thing to do when you hit a bug: Reload. Try your Autosave first, then your next oldest Save, no matter how far back it is. LennonCook's mention of walking back out into the hallway is spot-on. Sometimes, script-driven NPCs aren't able to walk if they aren't in the party's sight range (such as Kamir in the Graveyard District). Don't ask me why. If you absolutely have to cheat, the Guild Contact's creature name is BODFGT03. __________________ Volothamp's Comeuppance Everything you ever needed to know about the entire Baldur's Gate series......except spoilers.