1.x/Quests.yml - Revision history

Aufdemrand at 02:57, 11 May 2012

2012-05-11T02:57:11Z

← Older revision		Revision as of 02:57, 11 May 2012
Line 150:		Line 150:
	The requirements: node checks for conditions before allowing a player to take a quest. Requirements types can be item, quest, time, money, health, rank, or permission.		The requirements: node checks for conditions before allowing a player to take a quest. Requirements types can be item, quest, time, money, health, rank, or permission.

	See also: [[List of Requirement node types]]		See also: [[1.x/List of Requirement node types]]

	''- Note by aufdemrand: need to double check each type to confirm they work. I know for sure quest, money & item work. I am assuming on the others.''		''- Note by aufdemrand: need to double check each type to confirm they work. I know for sure quest, money & item work. I am assuming on the others.''
Line 184:		Line 184:
	Initial types can be item, quest, time, money, health, rank, or permission.		Initial types can be item, quest, time, money, health, rank, or permission.

	See also: [[List of Initial node types]]		See also: [[1.x/List of Initial node types]]

	''- Note by aufdemrand: need to double check each type to confirm they work. I know for sure money & item work. I am assuming on the others.''		''- Note by aufdemrand: need to double check each type to confirm they work. I know for sure money & item work. I am assuming on the others.''
Line 204:		Line 204:
	The rewards: node is used to tell the quester what to reward the player with when conditions are met. If all the objectives are completed, the rewards: node is triggered.		The rewards: node is used to tell the quester what to reward the player with when conditions are met. If all the objectives are completed, the rewards: node is triggered.

	See also: [[List of Rewards node types]]		See also: [[1.x/List of Rewards node types]]

	<pre>rewards:		<pre>rewards:
Line 223:		Line 223:
	This section is the meat of the quest file. Objectives tell the quester what needs to be accomplished in order to complete the quest. Available objectives include hunt, deliver, destroy, and more. They can be used together to make quests as simple, or as detailed as you want.		This section is the meat of the quest file. Objectives tell the quester what needs to be accomplished in order to complete the quest. Available objectives include hunt, deliver, destroy, and more. They can be used together to make quests as simple, or as detailed as you want.

	See also: [[List of Objective node types]]		See also: [[1.x/List of Objective node types]]


Line 258:		Line 258:
	=== Breakdown of an objective ===		=== Breakdown of an objective ===

	Sub-objectives contain types and their nodes. With the [[List of Objective node types]], you can use various types to control the flow of the quest. Here's an example that uses a hunt objective and a delivery objective. Sub-objectives can be completed in any order.		Sub-objectives contain types and their nodes. With the [[1.x/List of Objective node types]], you can use various types to control the flow of the quest. Here's an example that uses a hunt objective and a delivery objective. Sub-objectives can be completed in any order.

	<pre>		<pre>

Aufdemrand: /* Texts */

2012-05-01T13:53:19Z

Texts

← Older revision		Revision as of 13:53, 1 May 2012
Line 122:		Line 122:
	completion: "Completion text."</pre>		completion: "Completion text."</pre>

	Default text is white. Special character combinations can be used for formatting text. See: [[Message Formatting]] and [[Quest Text Formatting Tips]]		Default text is white. Special character combinations can be used for formatting text. See: [[1.x/Message Formatting]] and [[1.x/Quest Text Formatting Tips]]


	== Repeats ==		== Repeats ==

Aufdemrand: /* Example Quest */

2012-05-01T13:50:06Z

Example Quest

← Older revision		Revision as of 13:50, 1 May 2012
Line 30:		Line 30:
	== Example Quest==		== Example Quest==

	The quest below takes advantage of multiple objectives, delays, message formatting, and multiple rewards. Check out [[More Example Quests]].		The quest below takes advantage of multiple objectives, delays, message formatting, and multiple rewards. Check out [[1.x/More Example Quests]].

	<pre>		<pre>

AgentKid: moved Quests.yml to 1.x/Quests.yml

2012-02-19T12:15:29Z

moved Quests.yml to 1.x/Quests.yml

← Older revision	Revision as of 12:15, 19 February 2012
(No difference)

AgentKid at 16:55, 18 February 2012

2012-02-18T16:55:15Z

← Older revision		Revision as of 16:55, 18 February 2012
Line 309:		Line 309:

	{{NavBox}}		{{NavBox}}
			[[Category:Citizens1]]

AgentKid at 01:44, 18 February 2012

2012-02-18T01:44:56Z

← Older revision		Revision as of 01:44, 18 February 2012
Line 1:		Line 1:
			{{NoSupport}}
	<br>		<br>
	<br>		<br>

AgentKid: NavBox

2012-02-14T23:01:25Z

NavBox

← Older revision		Revision as of 23:01, 14 February 2012
Line 306:		Line 306:

	[[Advanced Questing Ideas]] will explore the use of other plugins to supplement Citizens.		[[Advanced Questing Ideas]] will explore the use of other plugins to supplement Citizens.

			{{NavBox}}

Aufdemrand: /* Example Quest */

2012-02-14T01:19:19Z

Example Quest

← Older revision		Revision as of 01:19, 14 February 2012
Line 66:		Line 66:
	amount: 6		amount: 6
	npcdestination: 22		npcdestination: 22
	optional: True # Optional sub-objective triggers only if you bring slimeballs before the other ~~objectives are~~ complete.		optional: True # Optional sub-objective triggers only if you bring slimeballs
			# before the other objective is complete.
	message: "&6Quest: Slimeballs delivered.		message: "&6Quest: Slimeballs delivered.
	<delay=50><Theo> Oh, what's this?		<delay=50><Theo> Oh, what's this?

Aufdemrand: /* Quests.yml */

2012-02-14T01:18:07Z

Quests.yml

← Older revision		Revision as of 01:18, 14 February 2012
Line 3:		Line 3:
	= Quests.yml =		= Quests.yml =

	Quests are defined in the quests.yml file located in plugins/Citizens. Because of the power and flexibility of the quest system, it can be a bit of a finicky beast. Pay special attention to spacing and the use of special characters. Quests.yml should pass any YAML parser without any errors. Most problems that arise from setting up quests is result of invalid formatting.		Quests are defined in the quests.yml file located in plugins/Citizens, one after another. Because of the power and flexibility of the quest system, it can be a bit of a finicky beast. Pay special attention to spacing and the use of special characters. Quests.yml should pass any YAML parser without any errors. Most problems that arise from setting up quests is result of invalid formatting.

	Tool: [[http://yaml-online-parser.appspot.com/ YAML Parser]] allows the contents of your .yml file to be pasted into the left box. If formatted incorrectly, parse errors will show in the right panel indicating the problem.		Tool: [[http://yaml-online-parser.appspot.com/ YAML Parser]] allows the contents of your .yml file to be pasted into the left box. If formatted incorrectly, parse errors will show in the right panel indicating the problem.

	Quests.yml is reloaded when using /citizens reload~~. This combined with a development server makes it easier to test how quests interact with the player~~.		Quests.yml is reloaded when using /citizens reload.

Aufdemrand: /* Initial */

2012-02-13T22:07:36Z

Initial

← Older revision		Revision as of 22:07, 13 February 2012
Line 169:		Line 169:
	== Initial ==		== Initial ==

	- Note: Requires Citizens ~~dev~~ 1.1.4 or higher.		- Note: Requires Citizens 1.1.4 or higher.

	Optional.		Optional.
Line 196:		Line 196:

	You may have multiple entries, or just one.		You may have multiple entries, or just one.


	== Rewards ==		== Rewards ==