The *.wld file, or the world file, contains all the rooms in your zone. It is loaded once and only once at boot.

Notes:

• First Line: The first line of the file should be: <*> File Version 1 <*>
• Last Line: There must be a blank line at the bottom of the file.

• Human Readable Fields: These are new and are completely optional. If used, the flags should be delimited by commas. They can take the place of the additive flags or be used in addition to them.

A unique number for the given room. No two rooms may have the same number. The room number must always increase when browsing down the world file (but increments can be larger than one). Placing rooms in your .wld file out of order or out of your zone's range will lead to bootup errors.

This name is the "title" of the room. Please note that all room titles should be capitalized. i.e. all the major words except ones like, and, the, of, etc need to be capitalized. You can use ANSI here.

This is the general description of the room.

• It must be indented with 3 spaces on the first line (don't use tab) as well as at least 5 lines long.
• Reusing descriptions is discouraged.
• Descriptions should be objective, avoid the use of personal pronouns. Don't assume the player is in the room when writing the description as there are many ways to see into a room from elsewhere. (Example: Clairvoyance)
• Don't put actions or activity into the room description, save these for echoes in the social file.

The number of the zone in which this room is located. This number is used for resetting zones and monster zone movement. The number usually equals the room numbers divided by 100 , i.e. zone 700 would contain rooms 70000-70099.

No Longer Used

The length, width and height of rooms can be set manually or auto-created on by testmud when the files are converted. Make sure you talk to your areas supervisor before manually setting these values as they can affect your zone in very subtle ways, for example: aggro archer's not firing from adjacent rooms, falling damage increasing by too much, rooms becoming single file without the actual flag.

Sector type has an influence on many things, not just movement cost and a mob's ability to leave them (see STAY_SECTOR). We'll try listing some examples below the chart.

• Use the Bit # to assign a sector in the WLD file. You may only select 1 sector for each room.

• Use the Bit Value to assign sectors to a Distro Machine. You can add more than one of these together to include multiple sectors in your distro.

• Setting a sector related to the planes will cause the room to be ignored when gating prime/planeshifting prime, the reverse is not however, true. Setting your zone with the sector FIRE_PLANE will not make portals to your zone open upon gating fire/planeshifting fire.
• Using Sector NO_GROUND with no down exit equals a death trap, players who are not flying will die with no warning.
• Using the UNDRWLD sectors will mean that only evil races will be able to relocate/open portals to that room.
• Many of these sectors restrict camping, some of them have very unique messages.

Sub zones are a new way or expressing arbitrary sections inside of a zone. Each room can be tagged with a subzone number from 1 to 32,768. Mobs with the new STAY_SUBZONE flag will respect their subzone boundaries just as they do with zone boundaries - they won't hunt or move outside of their subzone for any reason. We can use this to set up sections inside of zones where patrols and hunters will not leave. This also works nicely with the new AUTO_HUNT flag.

Note: Subzones are exclusive to each zone, so even if two zones connect to each other, and both rooms in zone A and zone B are marked with the same sub zone number, the mob will not cross over.

Note 2: With the addition of the new .config and .tpl files, this option has been depreciated in favor of subzones created in the .config file.

#70004
&+RThe Main Road&N~ 
&+L This road is the vital vein of the community. Wagons 
&+Land packages are carried down this road from the northern 
&+Lstores on Market Square to the gates towards the south. 
&+LScores of batiri and hobgoblins traverse this pathway to 
&+Ltrade with each other. Smoke rises from some chimneys 
&+Loff to the east, and the bones of dead humans litter the 
&+Lroadway. A hatch is visible against the side of a building 
&+Lto the east, and you see a sign at the end of the road.&N 
~
700 1 1 30 75 500
FLAGS: magic light, heal 
SECTOR: city 
SUBZONE: 23 
D0 
~ 
~ 
0 0 70007 
E 
sign~ 
&+rA smear of blood covers the name of the town.&N 
~ 
S

Format:

D[exit number]
[exit description, (*optional*)]
~
[keyword list]~
[Door flag][key number][to_room][trap fields (optional)]

The direction the exit leads to. It is one of:

Exit descriptions are currently not visible thanks to the "scan" command.

Used for commands like open and close. Should be 'door' for ordinary doors but can have multiple entries, like door, secret, entrance, trapdoor - all separated by spaces....

The state of the doors after reset may be controlled by a command in the .zon or .tpl files (see the zon file or Zone Commands). The default state of a door is open (0).

The number of the object which can unlock/lock the door. If [Door flag] is 0, the value of this field is ignored.

• To make the door magical and open only when a special word is spoken (like the magic gate east of WD), make this field -2. The last word in the door [keyword list] will be the triggering word.

The virtual number of the room to which the exit leads.