How To: Create Playermade Quests

What is a Playermade quest?

Playermade quests are created by giving out blank QuestHolder books that have the PlayerMade property set to true. This would typically be done through the use of the XmlQuestMaker stone. They allow players to design quests for other players to complete.

When the PlayerMade property is set, players can edit blank QuestHolders by double clicking them. This brings up a quest-design gump that allows them to enter their own objectives, text, and attach their own rewards.

Playermade quests can be just designed just like normal quests that a GM or other staff might create with some additional restrictions and features.

These quests can be given to other players or placed on playervendors or added to the PlayerQuestBoard bulletin board.

The quests will automatically be configured for AutoReward when reward items are attached.

Differences between Playermade and non-Playermade quests:

So that player quests can always be distinguished from non-player quests by spawners and other triggering items, player quests will have "PQ: " automatically appended to the beginning of their name.

When playermade quests expire or are deleted before being completed, the reward item that was attached to them will be returned to the quest creator. This way, players can hand out quests without worrying about losing the committed reward if the quest isnt used or completed.
A return container can be specified to receive quest reward returns. If not set, then it is returned to the players backpack.

Playermade quests have the weight of the reward items that they contain. This is to prevent exploits involving use of playerquests as weight-free containers. Non-playermade quests are weightless.

COLLECT and GIVE type quests:

Players can design quests that require other players to go out and collect or retrieve specified items.

The items collected or given are returned to the quest creator and placed into the specified return container (or the creators backpack if nothing is specified).
This allows resource contract type quests to be made, in which players offer rewards in return for certain goods.

For example constructing a quest with this objective

COLLECT,goldingot,100

would create a basic contract for 100 gold ingots.

COLLECT,greatercurepotion,100

would create a basic contract for 100 greater cure potions.

KILL type quests:

Playermade quests can specify objectives that require certain creatures to be killed by using the same type of KILL objective specifications used in normal quests. For example

KILL,balron,5

would instruct the player to kill 5 balrons.

If suggested installation STEP 6 is followed, the playermade quests will support various types of player kill contracts.

For example, a player constructing a quest with an objective

KILLNAMED,playername,PlayerMobile

would create a basic contract that would give the reward when the named player was killed.

KILL,PlayerMobile,5,kills>10

would create a contract that would give the reward when 5 murderers with more that 10 kills were killed

KILL,PlayerMobile,5,kills=0

would create a contract that would give the reward when 5 innocents were killed

Note that specifying the PlayerMobile type avoids exploits that would be possible with just a simple name specification of the target (for example killing a pet named the same as the target player).

Special Playermade quest items:

The PlayerQuestBoard item is a bulletinboard that can be placed in the world and allows players to drop and received playermade quests (such as the player kill contracts).
Just place it with

[add playerquestboard

The XmlQuestMaker item is a stone that dispenses blank playermade quests to be edited (double click it to dispense).
Just

[add xmlquestmaker

to place it.

Examples:

The questbook.xml example in xmlextras spawns two mobs that drop quests and questbooks.


Original Document by ArteGordon - Modified for use on UO:Renaissance
Original Article - http://xmlspawner.fr.yuku.com/topic/146#.U6BuP5TiKy4