This fatal crash occurs after a command has been entered, but before the input can be fed into the buffer window. In this case, the command was z. While there are a lot of hyperlinks in this project, the particular problem happens with typed commands, too.
In this example, the “ordinary checking for content rule” from GEP would be the first to fire. I’m not sure if its failure to appear before the crash means that it had a problem, or if it never starts in the first place.
I wish I could be more specific. I can’t produce the problem on demand. Once the specific condition is produced, IE, in a saved game, I can repeat the actions and it will happen again, but I cannot start a new game and reliably produce it.
Does anyone have any suggestions re: things to check out or experiment?
I don’t know if it helps, but you could try to open the Developer Tools in Lectrote under the menu “Window → Toggle Developer Tools”, and then in the tools, switch to the “Console” tab. That might reveal more about the error.
This is a bug in Quixe. It shouldn’t be possible even for a buggy game file. Mind you, the bug was probably triggered by a bug in your game file.
If you send me the game file and a save file that demonstrates it, I can try adding more debugging output. Really, it would be helpful to have the gameinfo.dbg from that compile – I realize that’s enormous and you might not have it any more.
Hrm. since this is a roguelike using autosaves, I had to manipulate things before I could pass the project along. However, the problem is now stubbornly refusing to appear. Some people will be testing this week. I’ll hang onto everything and will share what I have if we can get it to pop.