Indeed!
I have never noticed this, but now I ask myself how I could have overseen that strange misbehavior!
I haven't had a closer look, but the reason is most probably that there is a short delay (about one second or so) before the "Game over! Play again?" request opens (to have a little bit more time to see what caused the game over). During this time, the game behaves just like when you have disabled the "play again" request -- wait for a key or button to return to the main menu. But it gets messed up here.![Sad :(]()
This brings up the general question of what to do with keys and buttons during that short delay (assuming that the door behaves correctly otherwise): Return to the main menu (just as in the case when there is no "play again" request)? Use it to answer the upcoming "play again" request (which would then be "yes, I want to play again")? Simply ignore it (which could be confusing if pressing "return" was meant to be the answer for the expected request)?
Nevertheless, this has to be fixed.
Thanks for pointing out this nasty bug!

I have never noticed this, but now I ask myself how I could have overseen that strange misbehavior!

I haven't had a closer look, but the reason is most probably that there is a short delay (about one second or so) before the "Game over! Play again?" request opens (to have a little bit more time to see what caused the game over). During this time, the game behaves just like when you have disabled the "play again" request -- wait for a key or button to return to the main menu. But it gets messed up here.

This brings up the general question of what to do with keys and buttons during that short delay (assuming that the door behaves correctly otherwise): Return to the main menu (just as in the case when there is no "play again" request)? Use it to answer the upcoming "play again" request (which would then be "yes, I want to play again")? Simply ignore it (which could be confusing if pressing "return" was meant to be the answer for the expected request)?
Nevertheless, this has to be fixed.
Thanks for pointing out this nasty bug!
Statistics: Posted by Holger — Wed Mar 27, 2024 1:29 pm