Bug? MoveToLocationOrActor cannot be cancelled

[IlliciteS]

Hello,

I have a simple Behavior Tree with a MoveTo task with a decorator, a vector on “abort self”. So everytime I right click on the map, a unit move to that location. It works pretty well.

Now if I create my create my own task with the node Ai MoveTo, it works too. My unit can direction anytime I click.

Now I just swap the Ai MoveTo for a Move To Location Or Actor, and if I click during the travel time, the unit will not change direction. It will first go to the location and then, once it arrived, go to the new one.

I’ve looked for an explanation, what would be the difference, why would we not be able to cancel the move, and the only thing I found was this old post:

BehaviorTree node MoveToLocationOrActor is not aborted by declarators

If you create a custom task using the MoveToLocationOrActor node, that node will not be aborted if a decorator result change occurs, regardless if the abort mode is “self” or “lower”. The only way I could find to abort the task was to add a BBKey boolean to it and check it during “Tick”, using the “End Task” node on the output of the MoveTo node’s “Async Task Proxy” output pin. In cases where a decorator is attached directly to the custom move node (“self” abort), workarounds using a service a…

The bug is supposed to be fixed.

So is it really a bug or have I missed something about that MoveToLocationOrActor node?