bot frozen for some reason...

[demonD]

my bot just stopped for over 5 minutes standingstill so I have to press stop 2 times to stop it. (notice from 00:17:32,502 it does nothing till I stopped it). how to avoid this in future?


2018-02-11 00:17:30,306 [43] DEBUG Logger - [FinishCurrentAction][False] Waited 231 ms for the action to finish Bone Offering.
2018-02-11 00:17:30,458 [43] DEBUG Logger - [FinishCurrentAction][False] Waited 382 ms for the action to finish Bone Offering.
2018-02-11 00:17:30,607 [43] DEBUG Logger - [FinishCurrentAction][False] Waited 531 ms for the action to finish Bone Offering.
2018-02-11 00:17:30,746 [43] DEBUG Logger - [FinishCurrentAction][False] Waited 670 ms for the action to finish Bone Offering.
2018-02-11 00:17:30,880 [43] DEBUG Logger - [FinishCurrentAction][False] Waited 804 ms for the action to finish Bone Offering.
2018-02-11 00:17:31,022 [43] INFO Logger - [LatencyWait] Now sleeping 123 ms.
2018-02-11 00:17:31,303 [43] INFO Logger - [Logic] Using Convocation.
2018-02-11 00:17:31,315 [43] INFO Logger - [UseAt] convocation 1 True {466, 770} => None
2018-02-11 00:17:31,520 [43] INFO Logger - [LatencyWait] Now sleeping 123 ms.
2018-02-11 00:17:31,673 [43] DEBUG Logger - [FinishCurrentAction][False] Waited 0 ms for the action to finish Convocation.
2018-02-11 00:17:31,889 [43] DEBUG Logger - [FinishCurrentAction][False] Waited 216 ms for the action to finish Convocation.
2018-02-11 00:17:32,019 [43] DEBUG Logger - [FinishCurrentAction][False] Waited 346 ms for the action to finish Convocation.
2018-02-11 00:17:32,146 [43] DEBUG Logger - [FinishCurrentAction][False] Waited 473 ms for the action to finish Convocation.
2018-02-11 00:17:32,242 [43] INFO Logger - [LatencyWait] Now sleeping 124 ms.
2018-02-11 00:17:32,502 [43] INFO Logger - [Logic] Now moving towards the monster Bloodstained Vanguard because [canSee: False][pathDistance: 61.46475][blockedByDoor: False]
2018-02-11 00:25:14,745 [1] INFO BotManager - [Stop] Now requesting the BotThread to stop.
2018-02-11 00:26:23,723 [1] INFO Logger - [Deinitialize] Default.Abyss.Abyss
2018-02-11 00:26:23,745 [1] INFO Logger - [Deinitialize] AdvancedItemFilter.AdvancedItemFilter
2018-02-11 00:26:23,766 [1] DEBUG Logger - [AdvancedItemFilter] Deinitializing
2018-02-11 00:26:23,785 [1] INFO Logger - [Deinitialize] Alcor75PlayerMover.Alcor75PlayerMover
2018-02-11 00:26:23,808 [1] DEBUG Logger - [Alcor75PlayerMover] Deinitialize

 

[pushedx]

Moved to Support.

What area.map were you in? Typically a lockup like that would most likely be related to bad terrain data that locks up pathfinding. Various tilesets have generation issues that can trigger it, but that's about all I know of.