[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
|
name:alias,...,alias |
name-and-alias,alias,...,alias |
@describe me as "A very fine fellow, if a bit on the short side." |
A very fine fellow, if a bit on the short side. |
.description
property. For multi-line descriptions, .description
can be a
list of strings.
@rename #4237 to "Rover the Wonder Dog":Rover,dog |
#-1
or
$nothing
. Unlike `@move', `@eject' does not
check to see if the object wants to be moved, and with the destination
being what it is, there is no question of the destination refusing the
move, either. Generally, you should only resort to `@eject' if
`@move' doesn't work.
The first form of the command removes the object from the current room.
The second form removes the object from the specified place (which, in
most cases, you'll have to specify as an object number). In either
case, this command only works if you own the room/entity from which the
object is being ejected.
The form of the command
@eject ... from me |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
$room
. An exit is an instance of
the generic exit class, $exit
. An exit can be thought of as a
one way tunnel leading from one room to another. If you wish to have a
two way exit, you have to use two exits: one going from the source
to the destination
and one going from the destination
to
the source
.
The following commands are used for creating and managing rooms and
exits:
names names|names |
@dig "The Conservatory" |
@dig north,n to "The North Pole" |
@dig west,w|east,e,out to "The Department of Auto-Musicology" |
@dig up,u to #7164 |
[ << ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |