RiderOnTheStorm wrote:Just curious, when the game supercrashes and stays down for more than a second, if you caused it, do you still get the

OMG! SOMETHING IN "<COMMAND YOU ENTERED>" BLEW UP THE GAME. STOP IT.

Or do those only show up on minor crashes? I always get worried when I'm in the middle of something and the game goes boom.

If you don't get the message, the game threw an unhandled exception and blew up. It can happen in major and minor crashes. It just depends on what error it was. Generally, major crashes are caused by corrupted data or some coder being naughty before they properly tested their changes. Corrupted data happens easily in DIKU because of how haphazardly coded it is.

--- ATTENTION ---Something in the last command you entered, 'quit', has crashed the MUD. Although it may have been due to a random memory corruption, please try to use this command as sparingly as possible after the recovery, just in case. A core dump has been generated to assist debugging, and a coder will look into this issue as soon as possible. Thank you for your patience. -----------------

wilesly wrote:--- ATTENTION ---Something in the last command you entered, 'quit', has crashed the MUD. Although it may have been due to a random memory corruption, please try to use this command as sparingly as possible after the recovery, just in case. A core dump has been generated to assist debugging, and a coder will look into this issue as soon as possible. Thank you for your patience. -----------------

Apparently I'm not allowed to leave ...

I think the oddest one I've got was a message saying I crashed it by using 'scan'.