What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Stuck in Loop after Dom fight

M

mpo9k

New Member
Joined
Jul 21, 2015
Messages
8
Reaction score
0
Hio, so the bot is stuck after he kills dom going into endless loop :x
anyone has a solution for that?


[GridExplorer] Now segmenting the current area.
[GridExplorer] Area segmentation complete 00:00:04.4706878.
[ExploreTask] Now exploring to the location {3565, 368} (131) [6.294707 %].
[ExploreTask] Now exploring to the location {3522, 488} (138) [7.224607 %].
[LatencyTracker] AverageLatency: 88
[DominusFight] Now resetting the explorer.
[GridExplorer] Now segmenting the current area.
[GridExplorer] Area segmentation complete 00:00:04.6275649.
[ExploreTask] Now exploring to the location {3374, 316} (142) [6.509299 %].
[ExploreTask] Now exploring to the location {3312, 345} (156) [7.367668 %].
[LatencyTracker] LowestLatency: 51
[DominusFight] Now resetting the explorer.
[GridExplorer] Now segmenting the current area.
[GridExplorer] Area segmentation complete 00:00:04.7551200.
[ExploreTask] Now exploring to the location {3565, 368} (131) [6.294707 %].
[ExploreTask] Now exploring to the location {3522, 488} (135) [7.224607 %].
[DominusFight] Now resetting the explorer.
[GridExplorer] Now segmenting the current area.
[GridExplorer] Area segmentation complete 00:00:04.5895410.
[LatencyTracker] AverageLatency: 87
[ExploreTask] Now exploring to the location {3374, 316} (152) [6.509299 %].
[ExploreTask] Now exploring to the location {3353, 342} (128) [7.010015 %].
[DominusFight] Now resetting the explorer.
[GridExplorer] Now segmenting the current area.
[GridExplorer] Area segmentation complete 00:00:04.8719462.
[ExploreTask] Now exploring to the location {3565, 368} (129) [6.294707 %].
[Stop] Now requesting the BotThread to stop.
 
Actually, I'll add a fix for that, as it was happening to me in Piety as well (which I already fixed).

This game has no consistent means of handling boss deaths, so the tasks can get confused about what to do at times depending on what happens.
 
This will make it into a second update later today, didn't have time to do it in the previous.
 
pushedx said:
This will make it into a second update later today, didn't have time to do it in the previous.
Click to expand...
Ran into that same problem with Quest, pushedx gave me a fix for it and it's probably the same thing.

http://puu.sh/jgfBp/0416347194.txt

Is the unreleased version the Dev Group were running.
With the way pushedx set up the new buddy, this will be a LOT simpler.

The reason for some of the checks is;
1. If player dies, you don't want him going back to the "starting" position. This happened because I was removing and adding tasks on deaths, to reset their states. It's incorrect.
2. Some other reasons I forgot lol, but it worked xD.
 
yo now it doesnt get stuckd but its checing area too long after ascendat is dead :E
 
zamundabanana said:
yo now it doesnt get stuckd but its checing area too long after ascendat is dead :E
Click to expand...
That's very vague, how much is too long? 20 seconds?? Could it be trying to check for loot.. cause you know, if it's too fast and transitions to next stage without taking loot, you will post about it being too fast and skipping loot. Very hard to keep you happy it seems.
 
You must log in or register to reply here.
Back
Top