1.x/Quester: Difference between revisions

Latest revision as of 13:49, 1 May 2012

Not Supported!
This page is about Citizens 1.x, while the current version is Citizens 2.0.2. This page's content may be outdated, and shouldn't be trusted as being correct. See this page's talk page for more information. If you were looking for the 2.0.2 equivalent of this page, try Quester. If you feel this message was displayed in error, please contact an administrator.

Questers allow players to go on many different types of quests. They can collect or place blocks, attack mobs, travel a certain distance, and more! Quests are fully customizable in the 1.x/Quests.yml file. You can assign these quests to a quester and send your players on fun quests. See below for information on setting up a quester and customizing your quests.

Commands

Quester Commands
Command	Args Description	Require Selected	Require Ownership	Permission	Description
/quester help	None	false	false	citizens.quester.use.help	View the help page for questers
/quester assign [quest]	quest - name of quest to assign to a quester	true	true	citizens.quester.modify.quests.assign	Assign a quest to a quester
/quester remove [quest]	quest - quest to remove from a quester	true	true	citizens.quester.modify.quests.remove	Remove a quest from a quester
/quester quests (page)	page - page number	true	true	citizens.quester.use.quests.view	View a quester's quests
/quest help	None	false	false	citizens.quester.use.quests.help	View the help page for quests
/quest abort	None	true	true	citizens.quester.use.quests.abort	Abort the current quest
/quest completed (page)	page - page number	false	false	citizens.quester.use.quests.status	View completed quests
/quest status	None	false	false	citizens.quester.use.quests.status	View the status of the current quest

Usage

To accept a quest, go to a quester NPC. Via left clicking, you can scroll through the descriptions of each possible quest that the quester has assigned to it and that you can accept. Right click to accept the quest.

Only one quest can be accepted at any time - use /quest abort to abandon the current quest.

The status of the current quest can be viewed at any time via /quest status. On completion of the quest, return to the original quester NPC and right click them to finish the quest.

Quest Configuration

See 1.x/Quests.yml for detailed information about writing and editing quest structure.

Troubleshooting Quests.yml

Many problems with quest files are caused by incorrectly formatted YAML. To make sure your YAML quest file is able to be parsed correctly, this handy tool may be of help. This online YAML parser will take input syntax in the left window, and if correctly parsed, will show a result in the right side. If errors occur, check your 1.x/Quests.yml formatting and try again.

When writing custom quests, check format thoroughly, especially objectives. The 1.x/Quests.yml page outlines each node required by quests.

Quick Navigation
Usage	Installation · Frequently Asked Questions · Commands · Editors · Characters · API ·
Configuration	Configuration · Text Syntax · Permissions · Waypoints · Data Storage

@@ Line 1: / Line 1: @@
-Description here.
+{{NoSupport}}
+'''Questers''' allow players to go on many different types of quests. They can collect or place blocks, attack mobs, travel a certain distance, and more! Quests are fully customizable in the [[1.x/Quests.yml]] file. You can assign these quests to a quester and send your players on fun quests. See below for information on setting up a quester and customizing your quests.
 == Commands ==
+{| class="wikitable collapsible collapsed" style="text-align: center; width: 100%"
+|-
+! style="width: 100%; background-color:#ADD8E6" colspan="6" | '''Quester Commands'''
+|-
+! style="width: 250px;" | Command
+! style="width: 200px;" | Args Description
+! style="width: 150px;" | Require Selected
+! style="width: 150px;" | Require Ownership
+! style="width: 170px;" | Permission
+! Description
+|-
+| /quester help
+| ''None''
+| false
+| false
+| citizens.quester.use.help
+| View the help page for questers
+|-
+| /quester assign [quest]
+| ''quest'' - name of quest to assign to a quester
+| true
+| true
+| citizens.quester.modify.quests.assign
+| Assign a quest to a quester
+|-
+| /quester remove [quest]
+| ''quest'' - quest to remove from a quester
+| true
+| true
+| citizens.quester.modify.quests.remove
+| Remove a quest from a quester
+|-
+| /quester quests (page)
+| ''page'' - page number
+| true
+| true
+| citizens.quester.use.quests.view
+| View a quester's quests
+|-
+| /quest help
+| ''None''
+| false
+| false
+| citizens.quester.use.quests.help
+| View the help page for quests
+|-
+| /quest abort
+| ''None''
+| true
+| true
+| citizens.quester.use.quests.abort
+| Abort the current quest
+|-
+| /quest completed (page)
+| ''page'' - page number
+| false
+| false
+| citizens.quester.use.quests.status
+| View completed quests
+|-
+| /quest status
+| ''None''
+| false
+| false
+| citizens.quester.use.quests.status
+| View the status of the current quest
+|}
 == Usage ==
@@ Line 10: / Line 79: @@
 The status of the current quest can be viewed at any time via /quest status. On completion of the quest, return to the original quester NPC and right click them to finish the quest.
 == Quest Configuration ==
-=== Basics ===
-Quests are defined in the quests.yml file located in plugins/Citizens. Each root node in that file is a quest name - below, the two example quest names in quest.yml are 'example' and 'example2'. This is what you will use ingame to identify each quest.
-Inside this, there are text nodes - pretty self-explanatory. Note that you can use <br> to denote a line break.
-The repeatable option allows a quest to be repeated. Set it to false for once-off quests.
-=== Objectives ===
-Thus far, objectives have a set structure - a number of different 'steps' and a number of objectives within each step. This allows for more free-form quest design. Note that each step should be marked by an ascending number '''with single quotes''' around it. Each objective within a step is incremented concurrently.
-The message variable is sent to the player on completion of each objective.
-'''Objective Types'''
-To aid with generic objective design, each objective can use one of a common set of variables:
-* amount
-* string
-* materialid
-* location
-* item
-* npcdestination (destination NPC ID)
-Each objective type may use one or more of these variables - a reference is provided below.
-- Specifying item and locations -
-Item nodes have three sub-nodes, two that must be included and one optional.
-The ''id'' sub-node designates the item/block ID.
-The ''amount'' sub-node specifies the item amount.
-The optional ''data'' sub-node specifies the item data value to be used.
-Location nodes have 4 required sub-nodes, two optional.
-The ''world'' node specifies the world name of the location.
-The ''x'', ''y'', and ''z'' nodes specifies the x, y, and z values.
-The optional ''pitch''/''yaw'' nodes specify the rotation (think aeroplanes) of the location.
-=== Quest Types ===
-Build quest (build) - place a certain number of blocks
-Uses: ''materialid'' - the block ID to place. amount - the amount that must be placed.
-Location quest (move location)- be within a certain range of a location.
-Uses: ''location'' - the base location to move to. amount - the amount in blocks that the player can be away from the location before finishing.
-Hunt quest (hunt) - kill a certain number of monsters.
-Uses:
-* ''amount'' - the number of monsters to kill.
-* ''string'' - which monsters should be killed. Using '-' as the first character makes a whitelist. '*' represents all.
-Distance quest (move distance)- walk a certain number of blocks.
-Uses:
-* ''amount'' - the amount of blocks to walk.
-Block destroy quest (destroy block) - break a certain amount of blocks.
-Uses:
-* ''amount'' - the amount of blocks to break.
-* ''materialid'' - the block ID to break.
-Delivery quest (delivery)- deliver an item to an npc.
-Uses:
-* ''npcdestination'' - the NPC ID to deliver to.
-* ''materialid'' - the material that must be in hand.
-* ''amount'' - the amount of the material that must be in hand.
-Combat quest (player combat) - kill a certain number of players.
-Uses:
-* ''amount'' - the amount of players to kill.
-* ''string'' - which players should be killed. Using '-' as the first character makes a whitelist. '*' represents all. g:group represents groups.
-Collect quest (collect) - pick up a certain number of items.
-Uses:
-* ''amount'' - the number of items to pick up.
-* ''materialid'' - the ID to pick up.
-=== Rewards ===
-'''Format:''' Name (''type specifier'') - '''description'''
-These can be used as both rewards ''and'' requirements to start a quest. As rewards, they can be either give rewards, or take rewards. As requirements, they can only be used to take from a player.
-Rank reward (rank) - grants a group ('rank') to a player.
-Specified by the rank: node.
-Permission reward (permission) - grants a permission to a player.
+See [[1.x/Quests.yml]] for detailed information about writing and editing quest structure.
-Specified by the permission: node.
-Quest reward (quest) - grants a quest to a player. Note that it cannot be taken away from a player.
+== Troubleshooting Quests.yml ==
-Specified by the quest: node.
-Item reward (item) - gives an item to a player.
+Many problems with quest files are caused by incorrectly formatted YAML.  To make sure your YAML quest file is able to be parsed correctly, this handy tool may be of help. [http://yaml-online-parser.appspot.com/ This online YAML parser] will take input syntax in the left window, and if correctly parsed, will show a result in the right side.  If errors occur, check your [[1.x/Quests.yml]] formatting and try again.
-Loaded from the item: nodes.
-Health reward (health) - gives health to a player.
+When writing custom quests, check format thoroughly, especially objectives. The [[1.x/Quests.yml]] page outlines each node required by quests.
-Loaded from the amount: node.
-Money reward (money) - gives money to a player.
+{{NavBox}}
-Loaded from the money: node.
+[[Category:Citizens1]]