So, this has happened twice now (two of two, in fact). I'm running a mac version, and there were a few glitches coming out of compile, but it seemed to be working fine other than this.
- I start out in my starter dungeon. I futz around in there for a little while, then ascend to the worldmap.
- Once at the worldmap, I head for and enter a town.
- upon leaving that town, it enters into an infinite loop, where it saves, then enters, then saves, then exits, and so on, without further input from me. I am forced to force-quite the game. On the bright side, I am then able to reload the character, and it works fine, with a handy save, even. On the not-so-bright side, this only lasts until the next town.
- actually, playing further with this, when I make my way out of a dungeon with a one-way stair (the trapped quest, in this instance) I get spammed with "there is no way out of this dungeon here" messages - and then instantly enter (and begin the inevitable enter/exit/save cycles with) the next place I come across.
[b31] town exit cycling
Moderator: Moderator
Re: [b31] town exit cycling
I've hit this bug too, if you quickly hit a direction key when the map comes up, you can break the loop, and save your character from the bug.
EDIT: also on a mac.
EDIT: also on a mac.
Last edited by lukep on Mon Aug 22, 2011 1:41 am, edited 1 time in total.
Re: [b31] town exit cycling
I've had this happen too, but only on a mac.
The best workaround is to enter the worldmap via the "Change Level" option in the right-click menu.
The best workaround is to enter the worldmap via the "Change Level" option in the right-click menu.
Re: [b31] town exit cycling
Happened to me, also on a mac, etc...
Not game-breaking, though.
Not game-breaking, though.
Sorry about all the parentheses (sometimes I like to clarify things).
Re: [b31] town exit cycling
actually, the "hit a direction key" trick worked just fine - and hitting it once while the level is loading works - no need to time it or anything.
My suspicion is that somehow there's a buffer for move commands that's saving the buttonpress even after executing it, then trying to execute it again, but I've no real idea.
My suspicion is that somehow there's a buffer for move commands that's saving the buttonpress even after executing it, then trying to execute it again, but I've no real idea.