Hi Toni,
I've been following along the exploration tutorials. Very helpful. I've noticed one thing you entered that noes not appear to be displayed in the Journal text.
In the first section of this tutorial (2nd video) at ~2:20, you enter in the root of the quest exploreCircle under States|Successful: "You explored the circle". In play mode, I never see this message appear in the Journal. I've tested this in the Scene 02 Final as well as the scene I setup following your instructions. Even if I leave the journal UI open, this successful text does not appear, the quest info in the Journal simply vanishes after entering the circle.
I ignored this and went through the rest of the tutorial, no issues, play mode behaves as expected within the settings of the quest "exploreCircleAndReturn", other than that initial successful message that you enter under the state|successful body text "You explored the circle".
That said, referring to the explore and return quest, in the "Return" condition|states|active, the journal displays "You explored the circle and now need to return to Captain." as expected.
I guess I'm not following the purpose of the journal text initially entered in the quest|state|successful because it never appears? Can you help me understand, am I misunderstanding?
Added Issue: I'm having trouble implementing tutorial 3 collection/counter quest. Ac couple of issues but one obvious one is the counter display is showing the counter code rather than the counter values, see attachment. DISREGARD, after comparing the code, noticed I had "Chest" capitalized and it expected lower case {#Chests}/{>#Chests} Chests.
Also, is there a way to display completed quests in the journal rather than simply have them vanish from the journal on completion? Looking for player to gauge overall quest completion progress.
Thanks, Tom
Explore Circle question
Explore Circle question
- Attachments
-
- Screen Shot 2021-10-25 at 4.31.52 PM.png (640.43 KiB) Viewed 979 times
Last edited by oldmantom on Mon Oct 25, 2021 4:48 pm, edited 2 times in total.
Re: Explore Circle question
Hi Tom,
Inspect the player's Quest Journal component. Expand Save Settings, and tick Remember Completed Quests.
(The tutorial video was recorded before Quest Machine had a 'Remember Completed Quests' option.)
Inspect the player's Quest Journal component. Expand Save Settings, and tick Remember Completed Quests.
(The tutorial video was recorded before Quest Machine had a 'Remember Completed Quests' option.)
Re: Explore Circle question
Thank you Toni.
Re: Explore Circle question
Toni,
After collecting the 3 chest and returning to the Captain, the journal still reports I need to return to Captain rather than marking the quest as complete. Maybe I missed in the tutorial is covered that. What am I doing wrong?
Tom
After collecting the 3 chest and returning to the Captain, the journal still reports I need to return to Captain rather than marking the quest as complete. Maybe I missed in the tutorial is covered that. What am I doing wrong?
Tom
- Attachments
-
- Screen Shot 2021-10-25 at 5.50.22 PM.png (572.79 KiB) Viewed 976 times
Re: Explore Circle question
Hi,
In your Return node, make sure the Message Condition's Message is "Discussed Quest" and the ID exactly matches the ID that you've assigned to the quest.
Does the example Scene 03 Final work correctly? If so, you can compare its quest setup to yours.
In your Return node, make sure the Message Condition's Message is "Discussed Quest" and the ID exactly matches the ID that you've assigned to the quest.
Does the example Scene 03 Final work correctly? If so, you can compare its quest setup to yours.
Re: Explore Circle question
Yep, making sure the ID's match worked. My brain was warped yesterday starring and comparing. Thank you.
Re: Explore Circle question
A tip: If you don't want to worry about typos, you can create a String Asset for your quest ID (Assets > Create > Pixel Crushers > Common > Text > String Asset). Then assign it to the quest's Quest Info > ID field and anywhere else you need to reference the quest ID -- no typing needed.