I'll deal with the general bug-issues first, then get to the specifics.
When dealing with possible bugs, the first rule is to play it safe. If you encounter something that may be a bug, DO NOT SAVE. Instead, keep playing (to see if it's really a bug, and not just something bad/weird that's actually supposed to happen), but do *NOT* leave the area in which you first noticed the bug. If it really is a problem, Reload your Autosave and see if the bug is present there as well. If so, Reload your next oldest Save, and so on.
If all of your Save files are corrupted in this manner, the congratulations, you're screwed. Your only options are to
1) Restart the game from scratch, or
2) Crack open Shadowkeeper and pray you know what you're doing.
Saemon telling you that he was going to teleport you out to the surface and sun, but clearly not doing so, is a definite bug, and you were right to try to use cheats to circumvent it, but you forgot to do two things:
1) Make a new Savegame (NEVER overwrite your old Saves in a case like this) with a name that states the game has a bug.
2) Alt-Tab out of the game, and similarly rename your existing Autosave file to carry a similar warning label. Doing this will allow the game to continually make new Autosaves without overwriting the (hopefully) uncorrupted one....the way your game did the instant you entered the Vulgar Monkey.
So, now you're at the "Damage Control" section of bugfixing. Go though your Savegame files and try to find one before you spoke to Saemon, and if you don't have one, your best bet is to Save your game (always Save before playing with fire), and keep trying area codes (starting with AR1514) until you find Saemon's ship. Then, Reload and send your party to the correct area. You'll miss out on a little bit of EXP, but so what.
Or, in point of fact, you actually could just try the portal.
__________________
Volothamp's Comeuppance
Everything you ever needed to know about the entire Baldur's Gate series......except spoilers.
|