We have found on our mud that if a user (and they have, believe me), does a #loop command in tintin at the mud logon screen, they can effectively crash the mud.. We have made a semi-fix to this problem, but we think it may have caused other things to go wrong, so I'm asking if anyone else can come up with a GOOD solution to this problem.. Is there any way to stop something like a #loop command? Thanks, Andrew
This archive was generated by hypermail 2b30 : 12/18/00 PST