I dinged level 45 by killing the last monster on a princess quest. I returned to Gondolin and did the Maeglin quest; then, I tried to recall to Mordor. The game autosaved while waiting for the recall, then crashed when the recall went off. Now when I load the save file, the game crashes immediately.

I'm guessing there was some edge case not taken into account where the princess quest and the maeglin quest going off at the same time, and then that got saved into my save file.

Is there any way to recover the save file?

--AustinMcDonald

ShoOb: this should be fixed in the 2.3.5 version (I think), but as yet is is only released as a source.

NeilStevens: Try deleting the panic save to get to the autosave, then recall again to cancel the recall.

AustinMcDonald: There is no panic save :). I think I got ridiculously unlucky and it autosaved *on* the recall. I think I'm just screwed, unless running 2.3.5 will get around it.

NeilStevens: Yeah that sounds bad. I'm not sure I understand what the bug is, so I have no idea if it's fixed in 2.3.5 though.

AustinMcDonald: Yeah, it sounds like a horrible bug to try to replicate. To clarify, I think it shows up when you kill a single monster that dings you to level 45 and that same monster kill is the last one for a princess quest. I accepted the Maeglin quest, which recalled me out of the dungeon. Without looking at the code, I'd say that it assumed I was still in the dungeon while it executed part of the princess quest script, but I was actually back in Gondolin, so something got screwed up. I'll fiddle with debug mode and see if I can't replicate it.

NeilStevens: Oooh that makes sense and is indeed nasty.

ShoOb: heh, I guess the game needs to reorganize its priorities, I am not sure then if it is fixed, I know similar cases were dealt with.

BugReport911 (last edited 2008-05-16 17:26:57 by ShoOb)