hmmorpheus
commented
13 years ago The code referenced by Operetta was something I wrote in MUSH years ago and did indeed function using rooms, uselocks and a few commands. How to make it work in the proposed way I haven't managed to come up with yet.
Current timestop objects appear to be bugged as of Oct 2009: undestroyable, and +timestop/clear does not work. Revamping timestop objects is desirable.
Necessary functionality:
1) Be an object summonable to a location. 2) Be enterable. 3) Accurately record the location/time/situation for which it exists. 4) Be dismissable.
Possible additional functionality:
5) Lodge a +judge request if not summoned by a staff member. 6) Log inits/dice rolls/whatever made while inside the object(?) 7) Full log possibly or unnecessary resources hog?
Morpheus opines that the functionality that should be in a +timestop code, IMHO, is either already covered by the +judge code, or should be included in the +judge code, rather than making an entirely separate command that in essence performs/requests the same function.
Operetta suggests that something similar to timestop objects might be used for rental rooms. (Another game is cited where code existed to allow players to rent, redesc, hold for an extended duration, and vacate apartments or hotel rooms. If this is code similar to the one Bradamante saw, this was handled via regular rooms, plus a few commands and uselocks.)
Something similar to timestop objects might also be used to ease the pressure on roleplay rooms.