Exits are much like doors, only a bit of a strange concept, but they aren't two way. Now, in everyday real life, doors are two way, but its not always required for someone to go back the same path they came in, so if you want a two way door, you need to make two exits, one in, one out!

Syntax: '@open <exit>[=destination]'
You can also make exits as you would make actions - this means you can work one one room from a distance
Syntax: @action <exit>=<location>

The destination is optional, however, unlinked exits are not a good idea as it means people can come along and link from them - ie steal them! To link an exit which is currently unlinked, you can use '@link <exit>=<destination>' <destination> is normally reference by dbref number ie the #xxxxx number. As normally the item/room/program you are linking to is not within the current room so a name would not be resolved.

If you link something to the wrong place, or want to change its destination you can do @unlink <exit>. You may also link exits to programs - this creates commands.

Exits may have more than one name. Such as you may want an exit such as north east. However, You want to allow for people to type it with different names such as north east, north-east, ne. To achieve this the exit has ; separated names, so it would be @open north east;north-east;ne.

*** Do not leave exits unlinked, if you do they maybe recycled. ***

>> Descriptions, locks and more