Hm. Can you please clarify a bit more on the said bug? I just tried a simple tree to reproduce some sort of problem, but everything was working fine.
This is the tree I’ve tested. When I Fire1 is down, the flow continues down running the branch and as soon as I let go (Fire1 Up), the flow is interrupted and Failure is returned to the root. Can you please let me know how to reproduce the problem you’ve encountered? 🙂
Make a dynamic selector with multiple branch, the last has to be true in all case and run forever. If you push the Fire button and release it, it will go to the everytime true branch, and will not release the interrupt (the interupt will be false instead of Resting). making the second time you push Fire to ignore the Conditional because you are on the Interupt instead.
In your case it works because the BT finish as soon as fire is up and release/reset everything when stopping.
Didn’t tested in a simple case like yours, but on our game, it’s like that.
Hey,
Sorry for the late reply.
Could you send me a simple preproduction project showcasing the behaviour you are getting and the expected behaviour you want to have please?
If so that would be really great. Please use (support_AT_paradoxnotion.com) if you want to!
Thank you.