3.1 Creating a new roomIf the room you want to create doesn't already exist, create it with the @NEW ROOM <room number> command. Go into the room you just created with the GOTO command. Please use your virtual numbers assigned to you in order. Don't leave large gaps between used virtual numbers.
3.2 Setting the zone numberSet the zone number of the room for your zone with the @ZONE HERE <zone number> command, which is zone 1400. You might not have to do this in every room.
3.3 Describing roomsThis room is going to be a path leading up to a citadel, which is a kind of fortress. This path is through a field and is outside so we will need to describe and flag it as such. Remember, paths go in two directions, toward and away something. We don't want to assume which direction the reader is heading in.First, let's give the room a name. Room names are what appear at the very top of the room description and are always seen when entering a room even with the BRIEF setting on. Room names are like chapter titles in a book. They are phrases, not complete sentences and do not have punctuation. We will name the room using the @NAME HERE <room name> command:
Now we need to describe the room using the @DESCRIBE HERE command which opens up the multi-line editor. There are several things to keep in mind when writing room descriptions. First, always indent your first line with 3 spaces. Second, do NOT assume anything about the player reading the room description. This means do not use the word "you". Describe what they see without using the word "you". You should not use "you" because it is literally redundant. Of course they're looking at the room, they know that, they typed "look." Third, use grammatically complete sentences that are logical. Fourth, mind your spelling. Use the @SPELL HERE command after completing a room description. Fifth, end your lines before column 80 so it doesn't wrap in terminals. Sixth, keep your descriptions short and to the point. 3 to 5 sentences is enough to get your point across.
Let's check the spelling of the room with the @SPELL HERE command. If the spell checker doesn't find anything it will only display the version of the software. Keep in mind the spell check does not check grammar. You'll have to proof read your rooms yourself.
3.4 Assigning sector flagsThe difference between the sector flags is that they use more movement points when traversing from room to room - INSIDE uses the least (also isn't affected by day/night transition), MOUNTAIN uses the most. The water sectors have to do with what positions and actions are allowed in the room, for example you can't sleep on water. and the WATER-NOSWIM means players have to either be affected by waterwalking or be carrying a boat to enter.Since this location is outside we will need to change the INSIDE sector flag to a sector more logical using the @FLAG SECTOR <sector flag> command. After checking the list of available sector flags in the description of the @FLAG SECTOR command (you can also see a list by just typing @FLAG SECTOR) we see that the flag FIELD is more appropriate.
3.5 Sector flags explainedType @FLAG SECTOR to see a list of available sector flags. Each room can have one sector flag. Sector flags determine how many movement points it takes to enter or leave that room, what information is displayed to the occupants, special requirements for entering the room, and what actions are allowed in the room.Sector flags are also used in conjunction with the @ZONE RANDOM command to place objects and mobiles in a random fashion for sector types.
3.6 Linking roomsIf the room you are going to connect to doesn't already exist, create it with the @NEW ROOM <number> command. To create exits between rooms that don't already have exits in the direction you want to go, use the @DIG <direction> [<room number>] command. Since we're heading towards a citadel to the north, we need to start linking rooms together in that direction. Room 14001 already exists but doesn't have any exits so we'll use the @DIG <direction> [<room number>] command:
Detailing is encouraged. One of the things we can do to detail our areas is describe room exits. We can describe the exit north we just created with the @DESCRIBE <direction> command which opens up the multi-line editor. Exit descriptions should not be indented and should be complete sentences. Typically they are brief, 1 or two sentences. The exit descriptions are seen when a player is not in BRIEF mode and moves in that direction. It is also seen when a player looks in that direction.
3.7 Linking rooms with existing exits and creating one-way exitsIf a direction already exists in the room you want to link to you'll have to @DIG <direction> (without a room number argument!) first, then @LINK <direction> <room number> to get there. You can link as many exits into a single direction in a target room, but a room can only have one exit going out of a direction.You can also create one-way exits from a room to another room with the @DIG <direction> and @LINK <direction> <room number> combo. When travelling through one-way exits, players will see the following message: ""
3.8 Describing directions with no exitsIf you just want to create a direction for description purposes, use the @DIG direction command without the [<room number>] argument. Then use the @describe <direction> to attach a description to that direction that players can see when they look in that direction. If there is no link to another room in that direction, players will not be able to go in that direction.
3.9 Destroying room links and directionsYou can remove an existing room links and directions with the @DESTROY <direction> command. This command will completely remove the link inside the room and all its flags/descriptions/settings. This command will only destroy the link inside the room the command is executed in. If the link has a corresponding exit from another room into that room to destroyed link it will NOT be destroyed as well. You will have to go to the corresponding room and destroy the link from there to remove both ends of the link.Directions that are not links that were created for descriptive purposes can also be removed with this command.
3.10 Examining room settingsThis room is completed and let's take a look at what the players would see with the look command and what the actual room settings are with the @EXAMINE HERE command:
3.11 Copying roomsYou can either walk north or use the GOTO command to enter room 14001. Using the @DUPLICATE <room number> command, we can save a lot of creation time by copying room settings from a similar room. It is very important to note that one should not just blindly duplicate rooms and maintain the same room description. This gets tedious and boring to the player reading descriptions. It is okay to have a couple rooms in a row with the same description, but typically they should different in some way. In this case we are going to copy room 14000.
The room is going to be in front of the citadel so we need to name and describe it as such.
3.12 Linking rooms with keyless doorsNow we need to create the gate. The gate will be a "door" between the room 14001 and the room north of 14001 which will be 14002. Doors need to be created in both rooms the door is the link between. First, we need to create the the exit north with the @DIG <direction> [<room number>] command. Then we will flag the direction as a door with the @FLAG <direction> <door flag> command setting the flag IS-DOOR. Use the @FLAG <direction> without the flag argument to see the list of all available door flags. Next we will give the "door" a name with the @NAME <direction> <keyword(s)> command. Keep in mind that the game recognizes all keywords for operating the door but only displays the first one, so make the first one logical, not something like "white". Finally we will link the a key with the door at the same time as setting the door weight with the @LINK <key number> <direction> [<door weight>] command. Using the key value of -1 sets the key to nothing meaning it isn't lockable. For good measure, we're also going to describe the direction with the @DESCRIBE <direction> command. Remember! We have to do these commands to both sides of the door in room 14001 and 14002.
Now we go do the other side of the door in room 14002 south to 14001. We don't need to dig south from 14002 to 14001 because the exit already exists between the two rooms.
3.13 Linking rooms with keyed doorsNow were going to create a locked door north of here to room 14003 and set a key (object virtual number 14030) to be associated with the door using the @LINK <key number> <direction> [<door weight>] command. This means that the door can only be opened with the key 14030, picked by a thief or the "knock" mage spell. We could flag the exit "pickproof" or "wizard-locked" to give it further protection against picking and spells. We're also going to give it some weight so that only players with certain strength or greater can open it. Don't forget to do both sides of the door.Creating a door and binding a key is enough to establish a lockable door in the game, but in order for the door to be closed and locked when the game starts and the zone resets, we'll need to add a zone command entry. Use the @ZONE DOOR ("open" | "close" | "lock") <direction> command to set the state of the door. This MUST be done to both sides of the door. Using the "lock" action on the door will close it as well as locking it.
3.14 Direction (door) flags explainedType @flag <direction> to get a list of the currently available door flags. Doors can have more than one direction flag. Unwanted door flags can be removed by calling the @FLAG <direction> <door flag&t; command with an "!" placed in front of the flag to be removed. Door contribute to the behavior of a door. Doors should be set for "open", "closed", "locked" with zone command entries. Doors do not necessarily need a key to be locked or wizard locked. See @ZONE DOOR for more information.
3.15 Assigning room flagsRoom 14002 is the first room inside of the citadel which is a building of sorts. To the point, it is inside so we will need to flag the sector as such with the @FLAG SECTOR <sector flag> as well as the room flag INDOORS using the @FLAG HERE <room flag> command. Also, because there are no light sources inside the citadel, we'll flag it as dark so players will need to have a light source or infravision to see the room.
3.16 Room flags explainedType @FLAG HERE <room flag> to see a list of available room flags. Rooms can have more than one room flag. Unwanted room flags can be removed by calling the @FLAG HERE command with an "!" placed in front of the flag to be removed. Room flags contribute further properties to the room.
3.17 Creating and describing extra room itemsNow we will quickly describe and name the room. We're also going to create and describe an extra room item with the keyword crank using the @CREATE ITEM_HERE <item keyword(s)> command and the @DESCRIBE <item keyword(s)> command. If you want to re-edit the description of the extra room item by calling the @DESCRIBE <item keyword(s)> command. You can remove extra room items with the @DESTROY <item keyword(s)> command. Players can see the description you enter in by typing "look <item keyword(s)>". Extra room item descriptions are not indented and are typically one or two sentences long. There can be more than one group of keywords for separate room items.
3.18 Finding unused roomsSometimes when creating large areas, the virtual number you left off at can become lost. You can find unused room virtual numbers with the @FIND command.
3.19 Executing commands across multiple roomsUse the @NUMBERS ROOM command to execute a single command across multiple rooms. This is useful when forgetting a room flag that needs to placed in all rooms in a given section of your area. A command response will be returned for each command executed.
3.20 Saving your changesDon't forget to save the world after your work using the @SAVE world command. Saving the world file takes a while and uses a lot of system resources. Save often but not too often.
|