From the NannyMUD documentation
2001-01-13
area_d - Keep track of open and closed areas.
query_closed query_open
This daemon keeps track on what areas are closed in NannyMUD. If you have connections to other areas, you should check with the area_d before you add exits to that area. Likewise, check with the area_d if you consider cloning objects from other areas (and you should have the expressed approval of the creator before doing so).
Really only keeps a list of closed areas, but should perhaps hold a list of open areas, too. However it wasn't designed that way.
Here is a piece of code that uses the area_d to see if it is ok to add an exit to another area. The example takes for granted the use of a room object from the /std/ lib : if ("obj/daemon/area_d" -> query_open("players/brom/public")) add_exit("out", "/players/brom/public/r7");
NAME
query_closed - Query if area is closedSYNTAX
int query_closed(string area)DESCRIPTION
Returns 1 if the area is marked as closed.EXAMPLE
query_closed("players/brom/") will return 1 if Brom's area is marked as closed.
FUNCTION
NAME
query_open - Query if area is openSYNTAX
int query_open(string area)DESCRIPTION
Returns 1 if the area isn't marked as closed. This is really a logical not of query_closed().EXAMPLE
query_open("players/brom/") will return 1 if Brom's area is NOT marked as closed.