Pixel Crushers Forum

As you can see from screenshots below, a completely new scene does not have the UILocalizationManager. But the moment I select the TextTable for the QuestContent, the UILocalizationManager appears in the scene.

But it does not happen at runtime. It happens in Edit mode when I add QuestContent to the Quest. Whatever scene is open at that time, the UILocalizationManager is added to it

Hi!

For some reason, when I am adding QuestContent, the UILocalizationManager is being added to my hierarchy.

Any ideas why that happens and how to stop that?

Hi Tony! I think there are more issues in regards to the Autostart. I will try to explain it below. So let us consider the following scenario: We have a Quest that has an Autostart QuestCondition The Quest is added to the player's QuestJournal This condition is true at the moment the quest is starte...

Great! Thanks a lot.

Hi again, I have created the previous post where I described my problem. In this post, I want to report the bug. Steps to reproduce the bug: Using an empty Unity project with only QuestMachine imported Locate "Pesky Rabbits" quest Set the "rabbits" counter value to 1 In Autostart...

Right after I have posted this issue, I have checked the CounterQuestCondition and found that it uses almost the same approach. Thus, my question is, do you know why my approach causes the error?

Hi! I require some help with the QuestConditon. What I was trying to achieve, is to have a custom QuestCondition which in StartChecking() would check if the condition is already true, and if it is, then calls SetTrue(). public override void StartChecking(System.Action trueAction) { base.StartCheckin...

Thank you for your explanation

Hi again! I am having a small problem where the StopTracking method of QuestCondtion is being called twice after calling SetTrue(). One.png The screenshot above should provide enough context. Please let me know if something is not clear. So after the textEvent is invoked, the console will print &quo...