changed logic to check if move_to_fort is stuck

[ChiefM3]

Short Description:

• The existing logic to check if the bot was stuck was to compare the current distance to fort with the previous 5 distances to fort and say that it's stuck if there was 1 match.
• This would lead to a false positive very often because of the noise when the bot is set to move rather slow.
• I changed the logic to compare the previous 1-5 distances to fort vs previous 6-10 distances to fort to see the trend instead of a specific value. So if the trend is decreasing, the error_moving = True will not be triggered.

Fixes/Resolves/Closes (please use correct syntax):

• Fixes Having difficulty walking to XXXX #6099

[MerlionRock]

👍

[MerlionRock]

Let's test it