Most of you have already figured this out, but this message is for those of
you who have not:

When you try to do something in this mud by typing any command, you should, in
just about every case, see something. A typo message, for example. If you type
a command and you see absolutely nothing your prompt, then one of three things
has most likely happened:
a) your client gagged or otherwise ate the reply.
b) The command you are trying involves questionable code, and the response
somehow got lost in the shuffle.
c) There was a bug that broke the code long before the message was written.

Naturally, you should check your client first, if you have one. You might not
have thought you were going to gag lines like "A huge rock hits you on the
head" but hey, accidents happen. Assuming your client is not to blame (or you
have none, thumbs up my fellow raw telnet homies) the next thing you should do
is make a note of what you typed (the "history" command is good for this) and
make sure you typed what you thought you did, and if so, try it again. If you
still get no response at all (not even a typo message) it might be time to ask
an unidle wiz if there's a bug. A properly trained wizard, even a codeslave,
can read the bug log and tell you if something's up. If possible, you should
ask the coder of the area you're in, but that's not always obvious or
possible.

As always, you should use a properly formatted bug report when you are 100%
certain you have found a bug (for example, if the wizard you asked said "yes,
this is a bug"). When possible, stand in the room where the bug was found, or
holding the item/next to the monster you think was responsible. Be as detailed
as possible when describing your behavior. Short bug reports ("This room bugs,
fix it") will either be disregarded (because there's no info to go on) or left
unrewarded (because you weren't very helpful).

Thank you for your continued efforts to make BatMUD a better game.

Shinarae Lluminus