Top Mud Sites Forum - View Single Post

shadowfyr · 10-12-2003, 04:27 PM

Well. That is the one drawback. It only returns instances of loaded objects. But your method isn't any better, since it assigns each UID as the room loads (apparently) then removes it later when it is unloaded. Or I don't understand what you actually mean. In any case it wouldn't work if each new room got a premanent UID, either since removing room 3962-3965 out of a 10000 room mud leaves a gap. You would have to literally reassign everything above the start of the gap and adjust the number or the count would never be right anyway. Short of storing all rooms in a database and executing something like 'FROM Rooms COUNT ALL' or whatever the SQL would be for it, there is no way to do better than giveing a rough (and inaccurate) guess or counting the existing loaded rooms.

10-12-2003, 04:27 PM	#8
shadowfyr Senior Member Join Date: Oct 2002 Posts: 310	Well. That is the one drawback. It only returns instances of loaded objects. But your method isn't any better, since it assigns each UID as the room loads (apparently) then removes it later when it is unloaded. Or I don't understand what you actually mean. In any case it wouldn't work if each new room got a premanent UID, either since removing room 3962-3965 out of a 10000 room mud leaves a gap. You would have to literally reassign everything above the start of the gap and adjust the number or the count would never be right anyway. Short of storing all rooms in a database and executing something like 'FROM Rooms COUNT ALL' or whatever the SQL would be for it, there is no way to do better than giveing a rough (and inaccurate) guess or counting the existing loaded rooms.