Talk:Quest - Revision history

Aleigh at 23:33, 21 December 2021

2021-12-21T23:33:29Z

← Older revision		Revision as of 23:33, 21 December 2021
Line 24:		Line 24:
	* It would be nice to be able to give/take items in terms of the stages of a multi-part quest, as giving items and turn-ins as it stands require multiple quests, which is clunky. For example, the captain ought to send the player to the master-at-arms, who then gives them a sword, and then they go to the zombie field. Right now this requires two quests, one to complete to get the sword, and then another one to pick up to go kill zombies out in the field.		* It would be nice to be able to give/take items in terms of the stages of a multi-part quest, as giving items and turn-ins as it stands require multiple quests, which is clunky. For example, the captain ought to send the player to the master-at-arms, who then gives them a sword, and then they go to the zombie field. Right now this requires two quests, one to complete to get the sword, and then another one to pick up to go kill zombies out in the field.

	* quests.yml is currently one huge monolithic file, but this would be a lot simpler to work with - like for search/replace within a zone.		* quests.yml is currently one huge monolithic file, but this would be a lot simpler to work with if it was split into per-zone files - like for search/replace within a zone.

Aleigh: /* Limitations */

2021-12-21T23:33:13Z

Limitations

← Older revision		Revision as of 23:33, 21 December 2021
Line 23:		Line 23:

	* It would be nice to be able to give/take items in terms of the stages of a multi-part quest, as giving items and turn-ins as it stands require multiple quests, which is clunky. For example, the captain ought to send the player to the master-at-arms, who then gives them a sword, and then they go to the zombie field. Right now this requires two quests, one to complete to get the sword, and then another one to pick up to go kill zombies out in the field.		* It would be nice to be able to give/take items in terms of the stages of a multi-part quest, as giving items and turn-ins as it stands require multiple quests, which is clunky. For example, the captain ought to send the player to the master-at-arms, who then gives them a sword, and then they go to the zombie field. Right now this requires two quests, one to complete to get the sword, and then another one to pick up to go kill zombies out in the field.

			* quests.yml is currently one huge monolithic file, but this would be a lot simpler to work with - like for search/replace within a zone.

Aleigh at 23:32, 21 December 2021

2021-12-21T23:32:08Z

← Older revision		Revision as of 23:32, 21 December 2021
Line 5:		Line 5:
	* Incorrect: It's dangerous to go alone, take this.		* Incorrect: It's dangerous to go alone, take this.
	* Correct: The Master-at-Arms looks you over. "It's dangerous to go alone. Take this".		* Correct: The Master-at-Arms looks you over. "It's dangerous to go alone. Take this".

	~~= Technical =~~

	~~Quests.yml is YAML and has byzantine quote rules. Here is an example of a correct string with multiple double quote sets:~~

	~~<pre>~~
	~~'"If you are going to be of any use to us, you''re going to need a weapon." the Captain states. "Head downstairs and talk to the Master-at-Arms. He''ll set you up right."'~~
	~~</pre>~~


	= Works As Intended =		= Works As Intended =

Aleigh at 23:31, 21 December 2021

2021-12-21T23:31:58Z

← Older revision		Revision as of 23:31, 21 December 2021
Line 10:		Line 10:
	Quests.yml is YAML and has byzantine quote rules. Here is an example of a correct string with multiple double quote sets:		Quests.yml is YAML and has byzantine quote rules. Here is an example of a correct string with multiple double quote sets:

	~~{{blockquote\|~~		<pre>
	'"If you are going to be of any use to us, you''re going to need a weapon." the Captain states. "Head downstairs and talk to the Master-at-Arms. He''ll set you up right."'		'"If you are going to be of any use to us, you''re going to need a weapon." the Captain states. "Head downstairs and talk to the Master-at-Arms. He''ll set you up right."'
	}}		</pre>

Aleigh at 23:31, 21 December 2021

2021-12-21T23:31:46Z

← Older revision		Revision as of 23:31, 21 December 2021
Line 5:		Line 5:
	* Incorrect: It's dangerous to go alone, take this.		* Incorrect: It's dangerous to go alone, take this.
	* Correct: The Master-at-Arms looks you over. "It's dangerous to go alone. Take this".		* Correct: The Master-at-Arms looks you over. "It's dangerous to go alone. Take this".

			= Technical =

			Quests.yml is YAML and has byzantine quote rules. Here is an example of a correct string with multiple double quote sets:

			{{blockquote\|
			'"If you are going to be of any use to us, you''re going to need a weapon." the Captain states. "Head downstairs and talk to the Master-at-Arms. He''ll set you up right."'
			}}


	= Works As Intended =		= Works As Intended =

Aleigh: /* Works As Intended */

2021-12-21T23:03:35Z

Works As Intended

← Older revision		Revision as of 23:03, 21 December 2021
Line 8:		Line 8:
	= Works As Intended =		= Works As Intended =

	This section enumerates issues that, at least for the time being, are working-as-intended ~~and~~.		This section enumerates issues that, at least for the time being, are working-as-intended.

	* Changing the quest name in the quests.yml file breaks quest progress (a new name will generate a new UUID resulting in disassociation in the database. So do not casually rename quests, even if they are poorly named.		* Changing the quest name in the quests.yml file breaks quest progress (a new name will generate a new UUID resulting in disassociation in the database. So do not casually rename quests, even if they are poorly named.

Aleigh: /* Works As Intended */

2021-12-21T23:03:28Z

Works As Intended

← Older revision		Revision as of 23:03, 21 December 2021
Line 7:		Line 7:

	= Works As Intended =		= Works As Intended =

			This section enumerates issues that, at least for the time being, are working-as-intended and.

	* Changing the quest name in the quests.yml file breaks quest progress (a new name will generate a new UUID resulting in disassociation in the database. So do not casually rename quests, even if they are poorly named.		* Changing the quest name in the quests.yml file breaks quest progress (a new name will generate a new UUID resulting in disassociation in the database. So do not casually rename quests, even if they are poorly named.

Aleigh: /* Limitations */

2021-12-21T23:03:14Z

Limitations

← Older revision		Revision as of 23:03, 21 December 2021
Line 15:		Line 15:

	= Limitations =		= Limitations =

			This section enumerates issues / limitations that would improve the game if they were otherwise.

	* The NPC quest-givers do not filter their advertisement based on requirements when they offer multiple quests; they only filter if the player has completed the quest. It is only when the player attempts to take the quest that they are told they cannot. This is bad design resulting in a tedious play experience.		* The NPC quest-givers do not filter their advertisement based on requirements when they offer multiple quests; they only filter if the player has completed the quest. It is only when the player attempts to take the quest that they are told they cannot. This is bad design resulting in a tedious play experience.

	* It would be nice to be able to give/take items in terms of the stages of a multi-part quest, as giving items and turn-ins as it stands require multiple quests, which is clunky. For example, the captain ought to send the player to the master-at-arms, who then gives them a sword, and then they go to the zombie field. Right now this requires two quests, one to complete to get the sword, and then another one to pick up to go kill zombies out in the field.		* It would be nice to be able to give/take items in terms of the stages of a multi-part quest, as giving items and turn-ins as it stands require multiple quests, which is clunky. For example, the captain ought to send the player to the master-at-arms, who then gives them a sword, and then they go to the zombie field. Right now this requires two quests, one to complete to get the sword, and then another one to pick up to go kill zombies out in the field.

Aleigh: /* Works As Intended */

2021-12-21T23:02:47Z

Works As Intended

← Older revision		Revision as of 23:02, 21 December 2021
Line 11:		Line 11:

	* The order of the quests in the quests.yaml file matters. Quests that refer to other quests must appear later in the file.		* The order of the quests in the quests.yaml file matters. Quests that refer to other quests must appear later in the file.

			* The rewards for the quest are not stated mechanically, so it is up to the author to include flavor text which indicates the reward (if this is required). It's our general impression that most players most of the time are going to require a clear explanation of the reward of the quest. This is a contentious point re: [[Reputation]]. [[CaptainOHair]], who in general wants all information up-front all the time because he fears and hates mystery, wants quests to clearly state all rewards.

	= Limitations =		= Limitations =

Aleigh: /* Limitations */

2021-12-21T23:02:42Z

Limitations

← Older revision		Revision as of 23:02, 21 December 2021
Line 14:		Line 14:
	= Limitations =		= Limitations =

	* The NPC quest-givers do not filter their advertisement based on requirements when they offer multiple quests; they only filter if the player has completed the quest. It is only when the player attempts to take the quest that they are told they cannot. This is bad design resulting in a tedious play experience.		* The NPC quest-givers do not filter their advertisement based on requirements when they offer multiple quests; they only filter if the player has completed the quest. It is only when the player attempts to take the quest that they are told they cannot. This is bad design resulting in a tedious play experience.

	* The rewards for the quest are not stated mechanically, so it is up to the author to include flavor text which indicates the reward (if this is required). It's our general impression that most players most of the time are going to require a clear explanation of the reward of the quest. This is a contentious point re: [[Reputation]]. [[CaptainOHair]], who in general wants all information up-front all the time because he fears and hates mystery, wants quests to clearly state all rewards.

	* It would be nice to be able to give/take items in terms of the stages of a multi-part quest, as giving items and turn-ins as it stands require multiple quests, which is clunky. For example, the captain ought to send the player to the master-at-arms, who then gives them a sword, and then they go to the zombie field. Right now this requires two quests, one to complete to get the sword, and then another one to pick up to go kill zombies out in the field.		* It would be nice to be able to give/take items in terms of the stages of a multi-part quest, as giving items and turn-ins as it stands require multiple quests, which is clunky. For example, the captain ought to send the player to the master-at-arms, who then gives them a sword, and then they go to the zombie field. Right now this requires two quests, one to complete to get the sword, and then another one to pick up to go kill zombies out in the field.