Hey Guys! I have a question about decorators in Behavior Tree. There is an option called “observer aborts” and I can set it as “Lower Priority” so that way whenever my condition is met it will play that specific branch. Question is kinda obvious… but I still hope that’s it’s not the case
So to check these conditions with decorators. Is it working on tick? All of my logic like, playing animation on damage or death is set in behaviour tree with “blackboard based condition” or sometimes with “at location”. I wanted to know if that would hit my perfomance. seems like it would
Hi @eromanga ,
the decorator set to Aborts Lower priority will abort all tasks that have a lower priority than the current node (the little numbers on top of the tasks). It will invalidate the complete part of the tree that is lower priority than the current node.
It’s useful to interrupt all the subsequent task that is providing a blackboard value or when you want to cut a task that is already running.
Concerning the performance, I would suggest not according importance to it concerning a simple decorator until you encounter a performance issue.
But yes, decorator checks are on Tick
Hi! thanks for your reply, I know how abort works but here is what I want to know. It makes sense that it’s on tick because it has to abort other tasks but if I don’t use that option then it’s not going to check on tick, right? I’m always trying not to use tick events, so far I don’t have any manual events on tick, but I have 6-7 basic boolean checks with decorator, having 5-10 NPCs at the same time, I don’t know how crucial it will be
The decorator just waits for the blackboard to notify key changes/set . Actually it is the BrainComponent that is referenced in the Blackboard component that ticks and sends the dispatches.
Your Decorator justs waits for the notifications and does not tick.
