It is like the set visibility in the “then 1” path is locking the set visibility in the “then 0” so it does not trigger.
Please tell me I’m not going crazy?
Thank you.
This is for a quiz game and showing the score ui. This shows the flow of logic where I first hide or unhide some ui and then after a delay change the ui again. For some reason having the set visibility in the “then 1” from the sequence node breaks the ”then 0” logic. Without the connection to the set visibility logic, the “then 0” logic runs fine but I need the set visibility in the “then 1” logic.
It is like the set visibility in the “then 1” path is locking the set visibility in the “then 0” so it does not trigger.
It is like the set visibility in the “then 1” path is locking the set visibility in the “then 0” so it does not trigger.
When the interpreter sees a delay in a sequence, it will drop that line of execution, and come back to it after the delay has ended.
If other code it runs during the delay updates any relevant variables, things won’t work as expected.
Is there any way to fix this or get around it?
Don’t modify anything during the delay? 
( if this is the problem )