Your First Quest - Revision history

Silvematt at 11:55, 21 August 2023

2023-08-21T11:55:12Z

← Older revision		Revision as of 11:55, 21 August 2023
Line 465:		Line 465:

	And that's it! The quest is now completed and it's robust, it will react accordingly to the player's actions. In the last section below we'll see how to add the Compass Markers, that will allow us to have the Red arrow pointing to the Bandit Camp if we're at Stage 20, and pointing at Uriel if we're at stage 30.		And that's it! The quest is now completed and it's robust, it will react accordingly to the player's actions. In the last section below we'll see how to add the Compass Markers, that will allow us to have the Red arrow pointing to the Bandit Camp if we're at Stage 20, and pointing at Uriel if we're at stage 30.

	~~== Adding Compass markers ==~~

	== Files & Downloads ==		== Files & Downloads ==
	You can download all the files we've created for this quest [https://drive.google.com/file/d/12QnzPGSxVvaElKY727qTDtuDZhiO1QNK/view?usp=sharing here].		You can download all the files we've created for this quest [https://drive.google.com/file/d/12QnzPGSxVvaElKY727qTDtuDZhiO1QNK/view?usp=sharing here].

Silvematt: /* And what if... */

2022-03-09T14:43:10Z

And what if...

@@ Line 440: / Line 440: @@
 == And what if... ==
 == Adding Compass markers ==
 == Files & Downloads ==

Silvematt: /* And what if... */

2022-03-09T12:50:59Z

And what if...

← Older revision		Revision as of 12:50, 9 March 2022
Line 424:		Line 424:

	However there's still a problem, which is the same as the Quest Dealer one, when the Dialogue ends if we talk again to Uriel he will still have the "''[DIALOGUE] UrielsWaitingForBanditsToBeDead''". So we need to do the same thing as before, creating a new Dialogue and let Uriel switch to it after the quest has been completed.		However there's still a problem, which is the same as the Quest Dealer one, when the Dialogue ends if we talk again to Uriel he will still have the "''[DIALOGUE] UrielsWaitingForBanditsToBeDead''". So we need to do the same thing as before, creating a new Dialogue and let Uriel switch to it after the quest has been completed.

			So go ahead and create a new Dialogue Graph, I'll name it "''[DIALOGUE] UrielAfterQuest''" and it will just contain a single Dialogue Line, that will make Uriel say "Thanks again...". But I do not want the whole Dialogue interface to appear, so I'm going to make this a [[Dialogues\|'''Plain Dialogue''']] by just having an Entry Node that redirects to an NPC Dialogue Line that has those settings:

			[[File:Yfq n 15.png\|479x479px]]

			''Notice the Plain Line checkbox and the AfterLine set to '''EndDialogue''' - that's how you have a Plain Dialogue.''


			'''Update the Databases.''' Now the very last thing we need to do is to go back in the "''[DIALOGUE] UrielsWaitingForBanditsToBeDead''" and add a '''Change Dialogue''' node before ending the Dialogue, just like that:

			[[File:Yfq n 16.png\|623x623px]]


			You did it! With that done, the quest is completed and you should be able to play it from start to finish. Go ahead and do that! You may take a little break and then continue with the last two paragraphs.

	== And what if... ==		== And what if... ==

Silvematt: /* Implementation - Stage 30: Ending the Quest */

2022-03-09T12:33:24Z

Implementation - Stage 30: Ending the Quest

← Older revision		Revision as of 12:33, 9 March 2022
Line 389:		Line 389:
	"If GetStage of the quest with ID "SQ_ToBreakTheQuiet" is equal to 30", and		"If GetStage of the quest with ID "SQ_ToBreakTheQuiet" is equal to 30", and

	[[File:Yfq n 8.png\|~~552x552px~~]]		[[File:Yfq n 8.png\|570x570px]]


Line 420:		Line 420:


	At this point, the quest and its implementation is completed. However there's still a problem
			At this point, the quest and its implementation is completed.

			However there's still a problem, which is the same as the Quest Dealer one, when the Dialogue ends if we talk again to Uriel he will still have the "''[DIALOGUE] UrielsWaitingForBanditsToBeDead''". So we need to do the same thing as before, creating a new Dialogue and let Uriel switch to it after the quest has been completed.

	== And what if... ==		== And what if... ==

Silvematt: /* And what if... */

2022-03-09T12:30:08Z

And what if...

← Older revision		Revision as of 12:30, 9 March 2022
Line 408:		Line 408:

	"''Thanks again.... you saved me!''" -> The quest gets completed.		"''Thanks again.... you saved me!''" -> The quest gets completed.


			So click on Show/Hide on the second ''NPC Dialogue Line,'' we are going to add two Consequences: '''Add In Inventory''' and '''Alert Message,''' the first one adds the Golds to the Player's Inventory, while the second one shows an Alert Message for the Player.

			[[File:Yfq n 12.png\|425x425px]]


			Click again on Show/Hide to minimize the node, and let's open the third NPC Dialogue Line. We'll have to add a '''Quest Updater''' that completes the Stage 30, and completing a Stage that has "Complete Quest" checked, will complete the quest itself:

			[[File:Yfq n 13.png\|367x367px]]


			At this point, the quest and its implementation is completed. However there's still a problem

	== And what if... ==		== And what if... ==

Silvematt: /* Implementation - Stage 30: Ending the Quest */

2022-03-09T00:16:56Z

Implementation - Stage 30: Ending the Quest

@@ Line 172: / Line 172: @@
 To solve this, we simply have to make Uriel change his Dialogue as soon as the previous one is completed, we can do this directly in the Dialogue Graph, using the '''Change Dialogue Node'''.
-Before adding this node, we need to create the Dialogue we want to switch to. Create a new Dialogue Graph, name it "''[DIALOGUE] UrielsWaitingForBanditsToBeDead''", set the ID to "''DIALOGUE_UrielsWaitingForBanditsToBeDead''" ''', update the databases''', and then open it. We are going to create this Dialogue propertly later, for now just insert just an Entry Node and one NPC Dialogue Line that says anything and has as After Line "'''End Dialogue'''".
+Create a new Dialogue Graph, name it "''[DIALOGUE] UrielsWaitingForBanditsToBeDead''", set the ID to "''DIALOGUE_UrielsWaitingForBanditsToBeDead''" ''', update the databases''', and then open it. We are going to create this Dialogue properly later, for now just insert just an Entry Node and one NPC Dialogue Line that says anything and has as After Line "'''End Dialogue'''".
 Now let's get back to the UrielsDefaultDialogue, the Change Dialogue Node will go after the last NPC Dialogue Line and it will be followed by an End Node. Notice that the Change Dialogue Node is set to change the dialogue of the NPC who's currently speaking to the one we just created (''UrielsWaitingForBanditsToBeDead''):
@@ Line 355: / Line 357: @@
 == Implementation - Stage 30: Ending the Quest ==
 == And what if... ==
 == Files & Downloads ==

Silvematt: /* Implementation - Stage 30: Ending the Quest */

2022-03-08T22:55:20Z

Implementation - Stage 30: Ending the Quest

← Older revision		Revision as of 22:55, 8 March 2022
Line 355:		Line 355:

	== Implementation - Stage 30: Ending the Quest ==		== Implementation - Stage 30: Ending the Quest ==

			== And what if... ==

			== Files & Downloads ==

Silvematt at 22:46, 8 March 2022

2022-03-08T22:46:44Z

← Older revision		Revision as of 22:46, 8 March 2022
Line 345:		Line 345:
	</pre>And we're done. The structure is the same for every other time you'll want to check during a quest if an NPC is alive or not. You can just literally copy and paste this code to another Quest Script and all you need to change is the IDs, the objects names and the stages.		</pre>And we're done. The structure is the same for every other time you'll want to check during a quest if an NPC is alive or not. You can just literally copy and paste this code to another Quest Script and all you need to change is the IDs, the objects names and the stages.

	You can view the whole script here:		[[ToBreakTheQuietQuestScript\|You can view the whole script here.]]

	Save the script and go back in Unity.		Save the script and go back in Unity. Open the Quest with the Quest Window and set as the "Quest Script" the one we've just created.

			[[File:Yfq n 4.png\|526x526px]]


			'''Save''', and get back in the game. Pickup the quest from Uriel, the reach the bandits and kill them, the quest will update shortly after to Stage 30, and you'll see the Stage 20 completed on the screen.

			== Implementation - Stage 30: Ending the Quest ==

Silvematt: /* Implementation - Stage 20: The Quest Script */

2022-03-08T22:43:06Z

Implementation - Stage 20: The Quest Script

← Older revision		Revision as of 22:43, 8 March 2022
Line 300:		Line 300:

	Okay now for the substantial part, we need a way to check if the two NPCs are alive, and if they are both dead we should update the quest. This is something we need to check constantly, so that code will go inside the '''CustomUpdate()''' block. Not only, this is something that we need to check constantly but '''only if the current stage of the quest is 20''', so only if the Player's objective is killing the bandits.		Okay now for the substantial part, we need a way to check if the two NPCs are alive, and if they are both dead we should update the quest. This is something we need to check constantly, so that code will go inside the '''CustomUpdate()''' block. Not only, this is something that we need to check constantly but '''only if the current stage of the quest is 20''', so only if the Player's objective is killing the bandits.

			The code we need to do the following is just that:<pre>
			// CustomUpdate runs once every (quest.questScriptExecutionDelay) seconds
			public override void CustomUpdate()
			{
			base.CustomUpdate();

			// If the Current Quest Stage is 20
			if (quest.currentQuestStage == 20)
			{
			// If the bandit data has not been assigned
			if(bandit1 == null \|\| bandit2 == null)
			{
			// Those two lines tries to get the NPCs, if they're loaded
			CellInformation.TryToGetAI("UQBandit001", out bandit1);
			CellInformation.TryToGetAI("UQBandit002", out bandit2);
			}
			else
			{
			if (bandit1.isAlive == false && bandit2.isAlive == false)
			{
			// This block runs if the bandit data has been assigned and both bandits are dead
			RCKFunctions.CompleteQuestStage(quest.questID, 20);
			RCKFunctions.SetQuestStage(quest.questID, 30);
			}
			}
			}
			}
			</pre>Let's get to it step by step.

			The first block "if (quest.currentQuestStage == 20)" means "execute the following block only if the Player's Current Quest Stage is 20".

			The structure if(...) else if (...) below is used to check if the bandits are loaded inside the game or not.

			The first block '''if()''' runs if the bandits are not loaded and far away from the player, hence we can't get their fields and properties. If bandit1 doesn't contain the data we want, or if bandit2 doesn't contain the data we want, we constantly call the function '''CellInformation.TryToGetAI("UQBandit001", out bandit1);''' which tries to assigns to an object (which is bandit1) the respective data. You may notice two familiar things here, the ID "'''UQBandit001"''' and the '''bandit1''' object we've created. If you've used a different ID for the bandit, you should replace it. If you used a different name for the object, you should replace it as well.

			We obviously do that two times because we need two NPCs, and we need them at the same time. Notice the following line to be the same, but the only thing that changes is the ID and the object name.

			The second block '''else {...}''' runs if the Bandits are loaded and near the Player.

			Inside this block we check if their fields "'''isAlive'''" is false, so we check if they're both dead. If they are we call the two lines:<pre>
			RCKFunctions.CompleteQuestStage(quest.questID, 20); // That completes the quest stage 20.
			RCKFunctions.SetQuestStage(quest.questID, 30); // That sets the current quest stage to 30.
			</pre>And we're done. The structure is the same for every other time you'll want to check during a quest if an NPC is alive or not. You can just literally copy and paste this code to another Quest Script and all you need to change is the IDs, the objects names and the stages.

			You can view the whole script here:

			Save the script and go back in Unity.

Silvematt: /* Implementation - Stage 20: The Quest Script */

2022-03-08T22:15:12Z

Implementation - Stage 20: The Quest Script

@@ Line 235: / Line 235: @@
 == Implementation - Stage 20: The Quest Script ==
 It's time for a script! We've already seen how to update a quest when an NPC dies, that was in the [[A First Look, Part 1|A First Look]] tutorial, here we will see how to effectively create a new [[Quest Script]] from scratch that detects when an NPC (or more than one NPC) dies and updates the quest if it was meant to be updated.
@@ Line 258: / Line 260: @@
+    }
+}
-</pre>The Quest Script has two parts, a '''Start''' and a '''CustomUpdate'''.
+</pre>The Quest Script has two parts, a '''Start''' and a '''CustomUpdate'''. Start gets called as soon as this Quest Script runs, hence as soon as the Quest starts.
 CustomUpdate is called every '''''questScriptExecutionDelay''''' seconds, where '''''questScriptExecutionDelay''''' is a just a value that we can set to decide how often the CustomUpdate code will run.
@@ Line 273: / Line 273: @@
       RunQuestScript();
+   }
-</pre>With this line we've decided that the Quest Script will run its update every second, which is a good thresold between performance and result.
+</pre>With this line we've decided that the Quest Script will run its update every '''1''' second, which is a good compromise between performance and result.
 The "'''''quest"''''' written there is the Quest Object that contains all the information about the quest, like the stage we're at, the questScriptExecutionDelay, the stages we already completed, the ones we failed and other things. If you type '''''"quest."''''' if you're using Visual Studio the Intellisense should let you see all the fields and property of the quest.