- Screenshot 2021-02-02 143556.png (19.66 KiB) Viewed 504 times
Node state defaulting to active
Node state defaulting to active
I am trying to do something like this:
Each of the condition nodes should be inactive until I activate them via commands from the dialogue system, however when i give the quest to the player all of these nodes appear to be active. Each of these conditional tasks can be given in any order but the player can only have one at a time. How do I stop them from automatically becoming active?Re: Node state defaulting to active
Hi,
Whenever a quest starts, the Start node becomes active and then immediately true.
Whenever a node's state becomes true, it sets all of its children's states to active.
Add nodes that wait until they're manually activated instead:
Note also that I added a node below the 3 collection nodes. This node has a condition that all 3 parent nodes are true. Otherwise, as soon as one of the collection nodes were to become true, it would set the Success node to active. Whenever a Success node becomes active, it immediately sets itself true.
Whenever a quest starts, the Start node becomes active and then immediately true.
Whenever a node's state becomes true, it sets all of its children's states to active.
Add nodes that wait until they're manually activated instead:
Note also that I added a node below the 3 collection nodes. This node has a condition that all 3 parent nodes are true. Otherwise, as soon as one of the collection nodes were to become true, it would set the Success node to active. Whenever a Success node becomes active, it immediately sets itself true.
Re: Node state defaulting to active
Brilliant, thank you!
Re: Node state defaulting to active
Happy to help!