Thanks for the detailed info.
This should definetely not happen and the most unfortunate thing, is that I can’t replicate this somehow. When I stop and then (re) start a behaviour, it always restarts as expected, starting with the first node.
Do you by any chance, stop the behaviour from within the behaviour tree itself (like for example calling StopBehaviour() with an Execute Function, or from within a custom action task)?
Do you think that you can replicate this problem you are facing with a simpler behaviour tree, or a behaviour tree that you can share with me through email?
Gavalakis
