...which wouldn't be that bad if it didn't queue the input. When the auto-save feature kicks in, player may not have any indication of it happening - the message about it can be partially cut off or even not appear at all, I also had it appear after saving. Then the game hangs up for a few seconds, on my computer at least, which makes it look as if the game didn't register the key you pressed. So you press it again, and again because nothing is happening and suddenly your PC moves not one but three tiles forward. Good thing there wasn't any karmic dragon two tiles away from me, right? Not this time at least. I haven't died or messed my PC up yet due to this but I can definitely see it happening for someone.

The solution would be to it either make the autosave notification always visible or, even better, to stop queuing the input when autosave kicks in.

Game version: public R60, was present in R59 too
OS: Windows 8.1 64 bit
Display mode: NotEye, standard tile mode, message buffer mode irrevelant (happens for all), full screen.