Thanks for the explanation. I think I see why an embedded flowscript can’t be used as a condition node now. Replacing the LHS sequencer with a parallel does not do exactly what I want, it does interrupt the RHS of the tree but it also executes the LHS log action every tick. I tried moving the sequencer underneath the new parallel (see attached), this works but then also causes the RHS tree to be re-evaluated every tick and it causes a strange flickering.
It would be nice to have two types of embedded flowscripts, a condition type and an action type. This way you can easily extend NC with your own conditions/actions and without ever needing to write any code! Well, except for maybe really special purpose stuff like constraint solvers.
elliot bulmer
