pimp 0 Report post Posted February 17, 2016 (edited) There seems to be an issue with the bot navigating in Highgate, when bot access portal back to Highgate, it gets stuck near the entrance. Below are the logs; Lastrun 2016-02-17 14:48:00 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:00 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:00 [info] -> Moving to position(2600.925049, 4204.814453). State Priority: 92016-02-17 14:48:00 [info] -> Moving to position(2593.359863, 4211.833008). State Priority: 92016-02-17 14:48:00 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:01 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:01 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:01 [info] -> Moving to position(2600.576172, 4205.103027). State Priority: 92016-02-17 14:48:01 [info] -> Moving to position(2593.359863, 4211.833008). State Priority: 92016-02-17 14:48:01 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:01 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:01 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:01 [info] -> Moving to position(2603.308350, 4204.023926). State Priority: 92016-02-17 14:48:01 [info] -> Moving to position(2593.359863, 4211.833008). State Priority: 92016-02-17 14:48:01 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:01 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:02 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:02 [info] -> Moving to position(2600.166504, 4204.997559). State Priority: 92016-02-17 14:48:02 [info] -> Moving to position(2593.359863, 4211.833008). State Priority: 92016-02-17 14:48:02 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:02 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:02 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:03 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:03 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:03 [info] -> Moving to position(2555.408203, 4211.833008). State Priority: 92016-02-17 14:48:03 [info] -> Moving to position(2593.359863, 4211.833008). State Priority: 92016-02-17 14:48:03 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:03 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:03 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:03 [info] -> Moving to position(2582.781982, 4214.246582). State Priority: 92016-02-17 14:48:03 [info] -> Moving to position(2593.359863, 4211.833008). State Priority: 92016-02-17 14:48:03 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:04 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:04 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:04 [info] -> Moving to position(2583.135254, 4214.531738). State Priority: 92016-02-17 14:48:04 [info] -> Moving to position(2580.584717, 4211.833008). State Priority: 92016-02-17 14:48:04 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:04 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:04 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:04 [info] -> Moving to position(2574.850098, 4209.283203). State Priority: 92016-02-17 14:48:04 [info] -> Moving to position(2593.359863, 4211.833008). State Priority: 92016-02-17 14:48:04 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:05 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:05 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:05 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:05 [info] -> Moving to position(2582.903076, 4211.052734). State Priority: 92016-02-17 14:48:05 [info] -> Moving to position(2593.359863, 4211.833008). State Priority: 92016-02-17 14:48:05 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:05 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:05 [info] -> Moving to position(2605.203857, 4214.737793). State Priority: 92016-02-17 14:48:05 [info] -> Moving to position(2605.997070, 4211.833008). State Priority: 92016-02-17 14:48:05 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 92016-02-17 14:48:06 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 9 2016-02-17 14:48:06 [info] -> Moving to position(1701.086914, 3614.130371). State Priority: 9 Pathfinding 2016-02-17 14:48:06 [pathfinding] -> Raycast took 0 ms, wall found.2016-02-17 14:48:06 [pathfinding] -> Computing A* path from P(106, 394)->Pos(140, 492)2016-02-17 14:48:06 [pathfinding] -> A* from P(106, 394)->Pos(140, 492) took: 0 ms, cost: 137.0000002016-02-17 14:48:06 [pathfinding] -> Raycast took 0 ms, wall found.2016-02-17 14:48:06 [pathfinding] -> Entity(78, 332) is unwalkable, finding closest walkable position...2016-02-17 14:48:06 [pathfinding] -> Found new entity position: (117, 384)2016-02-17 14:48:06 [pathfinding] -> Computing A* path from P(106, 394)->Pos(117, 384)2016-02-17 14:48:06 [pathfinding] -> A* from P(106, 394)->Pos(117, 384) took: 0 ms, cost: 28.0000002016-02-17 14:48:06 [pathfinding] -> Raycast took 0 ms, wall found.2016-02-17 14:48:06 [pathfinding] -> Computing A* path from P(103, 395)->Pos(140, 492)2016-02-17 14:48:06 [pathfinding] -> A* from P(103, 395)->Pos(140, 492) took: 0 ms, cost: 136.0000002016-02-17 14:48:06 [pathfinding] -> Raycast took 0 ms, wall found.2016-02-17 14:48:06 [pathfinding] -> Entity(78, 332) is unwalkable, finding closest walkable position...2016-02-17 14:48:06 [pathfinding] -> Found new entity position: (117, 384)2016-02-17 14:48:06 [pathfinding] -> Computing A* path from P(103, 395)->Pos(117, 384)2016-02-17 14:48:06 [pathfinding] -> A* from P(103, 395)->Pos(117, 384) took: 0 ms, cost: 31.000000 Edited February 17, 2016 by pimp Share this post Link to post Share on other sites
jps42 138 Report post Posted February 17, 2016 Earlier I also had issues with bot moving back and forth between vendor and stash in Highgate. I didn't capture logs unfortunately, thought it was one-off and went to mapping. Other people seem to be having similar issues and even spotting other players wandering in Highgate. Share this post Link to post Share on other sites
Rooroosh 1 Report post Posted February 17, 2016 Bot also now spams blood rage instead of letting it run out before recasting. Share this post Link to post Share on other sites
jps42 138 Report post Posted February 17, 2016 Bot also now spams blood rage instead of letting it run out before recasting. I'm using blood rage now and it works perfectly.... do you have always recast buff and aura checked? You should only have always recast. Share this post Link to post Share on other sites
Rooroosh 1 Report post Posted February 17, 2016 (edited) I'm using blood rage now and it works perfectly.... do you have always recast buff and aura checked? You should only have always recast. Nope, doesn't work either way, worked fine the last few months, even with aura checked. Now he prioritizes blood rage recast over combat skills even though it hasn't ran out yet I reduced the priority and added a cooldown so now he doesn't spam it so much in combat. It seems like since the last patch bot thinks blood rage is a combat skill, not a buff and tries to attack mobs with it. Before this, I had it at priority 10 and 0 sec cooldown and bot still always waited till it ran out. Edited February 17, 2016 by Rooroosh Share this post Link to post Share on other sites
bugmenot 1 Report post Posted February 17, 2016 Rooroosh make sure no range (max min) for blood rage it will solve the problem at least worked for me. And i have stashing loop bug exactly same with previous version except its appears when no spaces left your bank slots. 2016-02-17 14:38:54 [info] -> Loading stash tab... 2016-02-17 14:38:54 [info] -> Selecting stash tab 1... 2016-02-17 14:38:54 [info] -> Loading stash tab... 2016-02-17 14:38:54 [info] -> Selecting stash tab 1... 2016-02-17 14:38:55 [info] -> Loading stash tab... 2016-02-17 14:38:55 [info] -> Selecting stash tab 1... 2016-02-17 14:38:56 [info] -> No stash tab available to stash items. 2016-02-17 14:38:56 [info] -> Moving to position(2506.281250, 5407.418945). State Priority: 3 2016-02-17 14:38:56 [info] -> Moving to position(2211.956543, 5657.608398). State Priority: 7 2016-02-17 14:38:56 [info] -> Moving to position(2211.956543, 5657.608398). State Priority: 7 2016-02-17 14:38:57 [info] -> No stash tab available to stash items. 2016-02-17 14:38:57 [info] -> Moving to position(2457.316895, 5439.102539). State Priority: 3 2016-02-17 14:38:57 [info] -> Moving to position(2211.956543, 5657.608398). State Priority: 7 2016-02-17 14:38:57 [info] -> Moving to position(2211.956543, 5657.608398). State Priority: 7 2016-02-17 14:38:57 [info] -> No stash tab available to stash items. 2016-02-17 14:38:58 [info] -> Moving to position(2469.362793, 5428.500488). State Priority: 3 2016-02-17 14:38:58 [info] -> Moving to position(2211.956543, 5657.608398). State Priority: 7 2016-02-17 14:38:58 [info] -> Moving to position(2211.956543, 5657.608398). State Priority: 7 2016-02-17 14:38:58 [info] -> No stash tab available to stash items. 2016-02-17 14:38:59 [info] -> Moving to position(2469.362793, 5428.500488). State Priority: 3 2016-02-17 14:38:59 [info] -> Moving to position(2211.956543, 5657.608398). State Priority: 7 2016-02-17 14:40:58 [info] -> Moving to position(2385.869629, 2298.913086). State Priority: 3 2016-02-17 14:40:59 [info] -> Selecting area... 2016-02-17 14:41:08 [info] -> Exiting bot 1 Share this post Link to post Share on other sites
Rooroosh 1 Report post Posted February 17, 2016 Rooroosh make sure no range (max min) for blood rage it will solve the problem at least worked for me. That fixed it, thanks. Share this post Link to post Share on other sites
bugmenot 1 Report post Posted February 17, 2016 Yw rorooroosh, btw i posted my issue to this topic because its refer same version of bot and stashing bug is annoying Share this post Link to post Share on other sites
Emdok 4 Report post Posted February 17, 2016 i have same isue if bot dont have maps to run stucks in highgate Share this post Link to post Share on other sites