Like the title suggests, in one of my behavior tree blueprints I use an “AI move to” which continues to function after the branch has changed, even calling itself again and moving to several different points. I’ve read in a few places that AI move to is a node that was somehow never intended to be used seriously, but is it really that bugged? Their behavior-tree based “moveto” has no real tweak-ability, and you can’t even tell whether it failed or succeeded. If I’m trying to make serious behavior trees in blueprints I feel like I need to use AI move to.
have you tried adding a decorator? with Inverted check? that way, the AI will only execute the MoveTo when its not on the location that is moving. else, it will execute that node on every tick
I have a blackboard decorator that aborts self, although I’m not sure what you mean by inverted check