Claim Building on CrystalMUSH

Finishing Up

Once you have built and described your claim and you think it's finished, run through each of the checks in the "Checklists" section below. If you need help with the +check, +spell or @edit tools, refer to "Tools".

When you have checked everything thoroughly, send +mail to Aria (+cc it to Brandy) telling her you're done. Leave the master claim object in the first room on the claim where it can be easily found. Aria will inspect the claim (it can take up to a few months for her to get to it), and if there are any problems she will ask you to fix them.

Once the claim is approved, it is @chowned to Ballybran (the character who owns all the stuff on the planet), and Brandy will set up the code for the crystal vein. The claim will be planted in the ranges for the Singers to find, and you can start another one!

Checklists

Rooms

1. Perform a +check on the room. Fix any warning tags that are not informational.
   
2. Perform a +spell on the room. It's better if you are not in the room when you do this, as it checks the spelling of not only the room but of every object in the room -- including you, if you're there. If there are any spelling errors, use the @edit command to correct them.
   
3. Make sure that the dbref of every room is listed in the &room-list attribute on your master claim object.
   
4. Make sure that the dbref of the room that will be the landing site is listed in the &landing_site attribute on your master claim object.
   
5. Make sure that the dbref of the room where the crystal vein will be is listed in the &vein_site attribute on your master claim object.
   
6. If there are dark rooms or any other special code, make sure that this is noted in the &note attribute on your master claim object.
   

Exits

1. Make sure that each exit has @desc, @succ, @osucc, and @odrop attributes.
   
2. Make sure that exits that may be locked have @fail and @ofail attributes.
   
3. Perform a +check on each exit. Fix any warning tags that are not informational.
   
4. Perform a +spell on each exit. If there are any spelling errors, use the @edit command to correct them.
   
5. Make sure that the dbref of every exit is listed in the &exit-list attribute on your master claim object.
   
6. If there are dark or locked exits, or any other special code, make sure that this is noted in the &note attribute on your master claim object.
   
7. If any exits need to be wiz-owned, make sure that their dbrefs are listed in the &wiz attribute on your master claim object.
   

Objects (other than the master claim object)

1. Make sure that any object on your claim that may be picked up has @succ, @osucc, @drop, and @odrop attributes.
   
2. Make sure that any object on your claim that may not be picked up has @fail and @ofail attributes.
   
3. Make sure that any object on your claim that may be entered has @idesc, @enter, @oenter, @oxenter, @leave, @oleave and @oxleave attributes.
   
4. Perform a +check on each object on your claim. Fix any warning tags that are not informational.
   
5. Perform a +spell on each object on your claim. If there are any spelling errors, use the @edit command to correct them.
   
6. Make sure that the dbref of every object on your claim is listed in the &other attribute on your master claim object.
   
7. Make sure that the use of every object on your claim is noted in the &note attribute on your master claim object.
   

Master Claim Object

1. If there is any reset code on your claim, make sure that it is set up in the &reset attribute. Test the code.
   
2. If you think that a hint may be in order on the claim, make sure that it is set up in the &hint attribute.
   
3. Make sure that your name is entered in the &builder attribute.
   
4. Perform a +spell on your master claim object. If there are any spelling errors (especially in the &basic_desc attribute), use the @edit command to correct them.
   
5. Leave the master claim object in the first room of your claim for the inspectors.
   

Tools

There are three tools or commands available to help you check your claim over and fix things. These are +check, +spell and the @edit command. All of these can be used on rooms, exits and objects.

+check

The +check tool checks that rooms, exits and objects are set up with all of the basic attributes they are supposed to have: @desc, @succ, @osucc, @odrop, @drop, @fail, @ofail, etc. It checks that exits going from one room to another are bidirectional (i.e., come back into the room). It will also make note of any rooms/exits/objects that are set dark, are locked, etc.

To use the +check command:

+check <room, exit or object>

The tool will present you with a report of informational and warning tags for the room/exit/object, if any problems are detected.

+spell

The +spell tool checks the spelling in each attribute on a room, exit or object. To use the +spell command:

+spell <room, exit or object>

The tool lists any spelling errors (or words it can't find in its dictionary) it finds by attribute on the room/exit/object. These can be corrected using the @edit command.

Performing +spell on a room checks each object and exit in the room.

@edit

The @edit command can be used to edit the contents of any attribute on a room, exit or object:

@edit <room, exit or object>/<attribute> = {<old text>},{<new text>}

where <attribute> is the name of the attribute that contains the text you want to change, <old text> is the text you want to remove, and <new text> is the text you want to replace it with. There should not be a space before or after the comma between <old text> and <new text>. If the text you want to remove/replace does not contain any commas, you can omit the curly braces around it. For example:

@edit here/local_desc = waving reeds,{tall, waving reeds}

would replace the words "waving reeds" in the &local_desc of the room you are standing in with the words "tall, waving reeds".

Introduction | Getting Started | Room Guidelines | Exit Guidelines | Puzzles and Pitfalls | Finishing Up

CrystalMush Homepage