Building
on the MUCK
Definitions:
IC: In Character (Virtual mode -the character being played)
OOC: Out of Character (Real Life mode -the player behind
the character)
RL: Real Life (Life outside the domain of the MUCK)
This
MUCK has no building quota per se, but endless creation
of completely useless items and rooms without having the
decency to @recycle them will be frowned upon. All links
to areas will be handled by the area's owner or by a Building
wizard. Before beginning a large or particularly expansive
project, contact a Building wiz for funding as well as to
check if there is a place in the grid for linking. We prefer
that 'floating rooms' (those not linked to the grid) not
exist and request that all rooms, homes, etc. be linked
to the grid within 60 days of project creation. Trespassing,
defined as entering what is obviously another character's
private dwelling or building without their permission is
a serious offense and repeated offenses can lead to @newpasswording
for 30+ days and possible @toading.
Specifics:
All Rooms built should have a name denoting where in
the world they are for the sake of continuity. For example,
if you were building a clothing shop called Leathers for
Furs, and had spoken to a Building wiz and had gotten permission
to link to Ruby Road, the name of the room directly off
the Road should be named:
Ruby
Road - Leathers for Furs.
A
dressing room in that same shop, however, could be named
this:
Leathers
for Furs - Dressing Room.
All
Descriptions and Exit Messages should be free from misspellings
and grammatical errors. All Exits should follow the same
format MUCK-wide if they're to be visible. The format at
creation must be exactly like this: @open North <N>;north;n=#<wherever>
Always
have more than one exitname option, and use the four cardinal
directions if your area is one of an outdoor theme. For
indoor themes, exitnames can be anything (i.e. 'Up <U>',
Down <D>', 'Bedroom <B>', 'Bathroom <BR>',
etc.) but the shortest logical shortening must be included
in < >, like the <N> in the example above (i.e.
viewable as 'North <N>').
All exits must have the @desc, @succ, @osucc, and @odrop
messages set. If you're not sure if you're missing any,
use @check to see what's done. If it returns nothing, you're
covered. A locked exit must also have @fail and @ofail messages.
Read the helpfiles on those subjects for more information.
All
public areas must meet these requirements in order to be
linked to the public grid, and all areas considered public
must be inspected by a Building wiz for approval before
linking. Any further building within and area already approved
by a Building wiz must be @locked until re-inspected by
a Building wiz.
Public
is defined as any area for free use by anyone, private areas
are defined as spaces for use by your player or a select
group of players. Private areas such as homes may be linked
to the main grid without the main exit being @locked, but
private areas contained in a larger public space must be
@locked to the public.
Violation
of building code can lead to removal from the grid, @newpasswording,
or possible @toading.
|