Hi,
Are you using your own quest system and custom C# method CheckQuestStatus() registered with Lua?
If so, keep the Dialogue Editor window open on that conversation while you're playing. The current node will be shown in green. Links to nodes whose Conditions are true will be green. Links to nodes whose Conditions are false will be red.
If you're using the Dialogue System's quest system, I recommend using the "..." to build the Conditions instead. This will use the correct functions and comparison values.
For conditions, False Condition Action - Block is the default value. I suspect that you'll want to keep it set to Block. Take this example:
- passthrough.png (9.22 KiB) Viewed 637 times
Say A1's Condition is false, and B's Conditions is true.
If A1's False Condition Action is Block, then as soon as it sees that A1's Condition is false, it will stop checking the A1 branch and immediately check B. Since B is true, it will show B.
On the other hand, if A1's False Condition Action is Passthrough, it will pass through A1 to check A2's Condition. If A2's Condition is true, it will show A2. Otherwise it will check B and show it.
That's the logic. Technically, it checks all possible nodes and then makes a decision. But it's easiest to think of it going one by one like I described above.
