Zones
Zones are organizational units for builders. Each zone houses a list of
mobiles, objects, rooms, triggers, reset instructions, and potentially other
additions, henceforth called contents. Each zone can be assigned a list of
builders who have editing access.
Zone Keys
Each zone has a unique reference key associated with it. Likewise, each zone
content also has a unique zone-relative key. Most muds accomplish this with use
of a virtual number (vnum) based referencing system. That each, each unique
zone, room, object, mobile, etc... has a unique key number associated with it.
In many DIKU muds, the default start room has a vnum of 1204. Whenever a builder
would want to reference this start room, they would use the number 1204 as a
reference key to access it.
NakedMud uses a string based referencing system. Each content of a zone is
assigned a unique string-based key (e.g., fido, mayor, town_square) instead of
a number. Contents of different types (e.g., mobiles vs. objects) can share the
same unique key. Key reference is context-dependent, and will identify the
correct type of content you are referring to. Zones also have unique keys. When
a content key is referenced, it is implicit that the user means the content key
of the zone they are currently within. For instance, using the command:
> goto town_squarewould attempt to take you to the room with key town_square in city1 if you are currently in city1, or the room with key town_square in city2 if you are currently in city2. Keys from other zones may be referenced by following the content key with an '@' symbol and the relevant zone key. For instance, if you are currently in city1 but would like to go to the town square of city2, you could use the command:
> goto town_square@city2
Zone contents
By default, zones support room, object, mobile, and trigger contents. However,
new content types can be added to the game (discussed in C basics). Additional
modules are available for Quest and NPC dialog contents.