The problem is not being in the room and staying there, rather that
when someone leaves, and the new room is saved, the player who left
keeps getting output from it and when going there again the MUD is
likely to crash because of a pointer conflict. removing people first,
and preventing them from entering a room being edited is a means to
avoid that situation
I've seen a situation like this before. It usually occurs when someone
attempts something akin to 'at #### redit'
-jac=
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 04/11/01 PDT