I guess the full message on the screen was "[Press SPACE to continue]"? This is odd because all pick commands don't create this message (I think).

Was some other message printed before that? Any additional information may help.

Which pick command did you use? Was an adom.err file created? Do you still have the save game (I guess not)?

Sorry I can't offer much more info than that. I did check the ADOM application directories for error or log files, but there was nothing there. I had to force-quit with task manager. The save file was gone too of course.

In the game, I was pcking up blessed arrows of demon slaying one by one from the floor after slaying a Balor and presumably adding them automatically to my quiver. So I would have been doing comma-space-right arrow, comma-space-right arrow. I was striking the keys fast, so maybe I double-spaced or entered them in the wrong order. I had already cleared out most of the monsters on the level.

Finally, I don't know if this is really a new issue--I've experienced fatal crashes before on D50 or other very crowded levels in v1.1 It's rare, but it does happen.

Too bad, I was looking forward to casting Wish for the first time with that character after saving the world. :-)

I might have found something, there are only three places in ADOM where the text "continue]" is used. The first place is when ADOM is waiting for the space key, this seem irrelevant here. But the other two places print messages like "[Press '@' to continue]". So, maybe because the message was not completely visible, you did not try the '@' key.

I'm not sure if this is a spoiler, just in case. :)

That is probably what happened--I guess it didn't crash after all. Dang it!

Thanks for looking into it, and I'm glad it's not a bug.

Ben

I'm very sorry... :(

It's still a bug that the message wasn't completely visible (the code responsible for it did not change since 1.1.1). I'll try to reproduce and fix this.

I could reproduce the problem. Sometimes if the message buffer wasn't completely empty, the important part of the message (i.e. the usage of "@" instead of the space key) wasn't visible. This is now fixed.