Bump. No-one answered this question. If you have an integer value that is LOCAL to a behaviour tree task and you increment it, the next time the task runs the variable is still incremented. I am not using any blackboard keys for this task, so all variables should be local and reset upon each call, To avoid this I have had to add a node at the start of execution that resets the integer back to 0, but this shouldn’t have to be the case. Seems like an engine bug