Problem with custom QuestCondition
Posted: Fri May 28, 2021 8:12 am
Hi again!
I am having a small problem where the StopTracking method of QuestCondtion is being called twice after calling SetTrue().
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 "a" twice.
My question is if it is intended or maybe I am doing something wrong.
Thanks in advance.
I am having a small problem where the StopTracking method of QuestCondtion is being called twice after calling SetTrue().
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 "a" twice.
My question is if it is intended or maybe I am doing something wrong.
Thanks in advance.