It seems I have a subtree instantiation bug here after some refactors :(, meaning that the subtree is not instantiated and instead the exact same instance is used in some cases. I will have to fix this ASAP.
The fix you’ve proposed will work fine for as long as the subtrees are not under a Parallel node, although it would be better if you first check/reset the subtree and then call execute:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
protectedoverride Status OnExecute(Component agent,Blackboard blackboard){