Thanks for attaching the logs. I think I see the issue now.
However, it might take at least one more version to try a fix, since some stuff needs to be changed, and I'm not sure if it'll break other things badly or not yet.
Basically, there's a wrong check being done for the range, > range rather than < range to cancel early, which is why you see the "Movement cancelled, cancellation callback returned true.". However, there's also an issue where the logic assumes we need to keep LoS for the target location, which considering some of the random LoS issues, breaks that logic at times. Since that function is used all over the place, we need to retest with the changes to see if the bot doesn't break as a result of those conditions changing.
