STILL getting stuck on large chests in catacombs.

[destined2bgreat 0]

Well the title says it all, watched the bot try and pick up a couple wisdom scrolls after successfully picking up a rare item.  Waited a couple minutes, the bot didn't recognize it being idle and wouldn't teleport home.  Not sure if it's just me, but the bot will do this every single time it encounters a large chest, making botting catacombs impossible unless I'm at my computer.  Any suggestions to fix it, or is it the bot?

 

Pathfinding log shows these lines over and over for the time it was trying to pick up the items:

 

2014-01-21 23:04:06 [pathfinding] -> Set explored nodes took: 0 ms

2014-01-21 23:04:06 [pathfinding] -> Computing A* path from P(129, 1159)->Pos(131, 1159)

2014-01-21 23:04:06 [pathfinding] -> A* from P(129, 1159)->Pos(131, 1159) took: 0 ms, cost: 2.000000

2014-01-21 23:04:06 [pathfinding] -> Computing A* path from P(129, 1159)->Pos(135, 1168)

2014-01-21 23:04:06 [pathfinding] -> A* from P(129, 1159)->Pos(135, 1168) took: 0 ms, cost: 9.000000

2014-01-21 23:04:06 [pathfinding] -> Computing A* path from P(129, 1159)->Pos(129, 1162)

2014-01-21 23:04:06 [pathfinding] -> A* from P(129, 1159)->Pos(129, 1162) took: 0 ms, cost: 3.000000

2014-01-21 23:04:07 [pathfinding] -> Set explored nodes took: 0 ms

2014-01-21 23:04:07 [pathfinding] -> Computing A* path from P(129, 1159)->Pos(131, 1159)

2014-01-21 23:04:07 [pathfinding] -> A* from P(129, 1159)->Pos(131, 1159) took: 0 ms, cost: 2.000000

2014-01-21 23:04:07 [pathfinding] -> Computing A* path from P(129, 1159)->Pos(135, 1168)

2014-01-21 23:04:07 [pathfinding] -> A* from P(129, 1159)->Pos(135, 1168) took: 0 ms, cost: 9.000000

2014-01-21 23:04:07 [pathfinding] -> Computing A* path from P(129, 1159)->Pos(129, 1162)

2014-01-21 23:04:07 [pathfinding] -> A* from P(129, 1159)->Pos(129, 1162) took: 0 ms, cost: 3.000000

2014-01-21 23:04:07 [pathfinding] -> Set explored nodes took: 0 ms

2014-01-21 23:04:07 [pathfinding] -> Computing A* path from P(129, 1159)->Pos(131, 1159)

2014-01-21 23:04:07 [pathfinding] -> A* from P(129, 1159)->Pos(131, 1159) took: 0 ms, cost: 2.000000

2014-01-21 23:04:07 [pathfinding] -> Computing A* path from P(129, 1159)->Pos(135, 1168)

2014-01-21 23:04:07 [pathfinding] -> A* from P(129, 1159)->Pos(135, 1168) took: 0 ms, cost: 9.000000

2014-01-21 23:04:07 [pathfinding] -> Computing A* path from P(129, 1159)->Pos(129, 1162)

2014-01-21 23:04:07 [pathfinding] -> A* from P(129, 1159)->Pos(129, 1162) took: 0 ms, cost: 3.000000

2014-01-21 23:04:07 [pathfinding] -> Set explored nodes took: 0 ms

Edited January 22, 2014 by destined2bgreat

[destined2bgreat 0]

Bot is still doing this.  Can't run catacombs for more than an hour or two because of this.  Anyone have any advice...

[destined2bgreat 0]

Tried this on a vm workstation windows 7 virtual machine, same thing happens.  If anyone has any advice, such as config file settings to change, would be greatly appreciated...