The current system causes overlap with the loops, causing it to call the function AbortMovement() while aggroing.
The issue is most likely due to the eventloop still continuing after a new path has been computed. And then calling the function MoveTo() while the eventloop is still running. But, despite after changing it to not call the function MoveTo() if a loop is running, it still overlaps.
The current system causes overlap with the loops, causing it to call the function
AbortMovement()
while aggroing.The issue is most likely due to the eventloop still continuing after a new path has been computed. And then calling the function
MoveTo()
while the eventloop is still running. But, despite after changing it to not call the functionMoveTo()
if a loop is running, it still overlaps.