How to make and load perzes.
How to make restrings.
Adding helpfiles.
Tracing keywords in scripts.

Making Perzes

The following items can't be perzed: the Imm Uber items, timered items, temporary questzone items and Artifacts.

If a temporary zone has been put in, a note will be send to all imms with the zonenumber so that they know to avoid making perzes of items coming from that zone. Atm this includes zone 144, 259 and 261.

Objects coming from the zone 267 (The Gladiator Arena) can't be perzed either. Those items shouldn't even leave the zone. So if you catch a non-Gladiator having one of those items ask them how they got it and to hand over the item to an Imm.

Also the following items can not be personalized :
(This list will be shortened after we get the restrict double wear_loc scripts running, but more items may be added in the future).
- ALL Mine equipment
- Anything that is poison 3 or 4
- Heavy stone shackles
- The sword Orcrist
- The sword Memory
- The dark sword Sorrow
- Martin's Holy Armour
- The bloody horntips of the Minotaur
- The scaled legs of the green dragon
- Achilles' heel
- The *shining* armor of Achilles
- The scourge of Tisiphone
- A crinkled leaf
- Robin Hood's Official Greencoat Dagger
- The cool dagger
- The Rainbow Serpent's skin (May be perzed only once)
- A cosmic string (May be perzed only once)
- A -mythril- bracelet set with the Gravity Materia
- Grizzled fur
- Ghostly Shimmer
- Henna hand tattoo
- a spider fang (27022)

How to proceed?

The mortal will need to hand over the original item. Once you have that, you create a new object, (meaning perzed objects have a different vnum as the original) and you copy all the stats, flags and scripts that the original item has, into this new perzed object.

The alias of the new vnum should include the following:
1) the aliaslist of the original item + the alias for the new item
2) the name of the player asking the perz (only one playername is allowed)
3) the word perz
4) the vnum of the original item in case the item has multiple wear_locs or can be worn more than once (For instance an item flagged FINGER can be worn twice at the same time.)

Point 3) adding the word perz is so we can single out perzes from other objects in DTs.
The rest are to make checking someone's equipment easier. Also if the original item has scripts attached to it, those same scripts have to be added to the new perzed item.

Note that the same perz may never have the name of two players, unless one of them is an alt, or the item is a wedding ring. Even so, it's better to make 2 rings.
Back to the top.

Loading perzes

The owner can have their perz reloaded for a set fee, if they lose it.

There may however only be one of each perz in the game at the same time, so if they were pkilled and someone nabbed their perz instead of junking it, you cannot load a new one for them until the first one has been disposed of.
This can be a bit hard to keep track of, but the players usually know.
Back to the top.

Making Restrings

Rp-eq has no stats and thus there's no need to make a separate vnum for each rp-piece.
That's the reason why someone already created a list of non-statted equipment directly usuable for restrings, namely from vnum 19410 till 19430 +19433 +19435 +19497 +8428, a piece for each wear_loc. (Or do a where equipment if you prefer.)

So the easiest way to do restrings/rp-equipment would be to load the corresponding vnum and then use the string command to adjust the values: name, short desc and long desc.
By loading the item first, you'll ensure that you don't mistakenly restring another item in the game with the same alias, since the code will always call for the first item on the list you get while typing 'where < item-name >' (i.e. the latest loaded).
Syntax: string < obj > < field > < value >
Usage:
string < obj > name < value >
string < obj > short < value >
string < obj > long < value >

For a hold-object this would lead to:
Step 1 - load obj 19422
This will load a hold item. To make sure you don't restring another item in the mud.
step 2 - string hold name diandra
Here you change the name of the item (hold) to the new name (Diandra), make sure you use that new name for the following steps, otherwise you might end up renaming some other item in the mud.
step 3 - string diandra short a piece of freshly obtained meat
The item in your inventory should have changed to the new short name.
step 4 - string diandra long Some raw meat is dropped on the floor.
This is what you'll see when the rp-item is dropped.
step 5 - string diandra name meat diandra
This will change the name of the item again (namely from just Diandra, to 'meat diandra'), including the player's name helps to retrieve items when necessary, or to give them all at once to the right player.
If after this step you have to use string again, the name to be used however will be meat - the first noun followed after the 'string diandra name' command.
Back to the top.

Adding helpfiles.

At the moment we have lots of helpfiles with the keyword UNDEFINED. So when you make a new helpfile, type 'HEDIT UNDEFINED' and you'll get into the menu to change the current undefined helpfile. Follow the steps in the menu to add the helpfile and don't forget to change the KEYWORD undefined in option 1. All helpfiles must also have their KEYWORDS in CAPITAL letters so they're conform with the already existing helpfiles.
Back to the top.

Tracing keywords in scripts.

Usage: TSEARCH < ALL | BODY | NAME | ARGS > < phrase to find >
Tsearch is usefull to find out a script with a certain phrase or word in it, but you have no idea in which zone or area the trigger is at.
Back to the top.