destined2bgreat

I agree that I can't leave my bot in catacombs for more than 3-5 hours before it gets stuck. Sometimes it's stuck trying to pick up items, sometimes it's trying to pick an instance, other miscellaneous things happen too. I can run catacombs when I'm in the room, but it still needs work to be able to bot it afk. And yeah, the only way to stop the bot from trying to pick an instance is completely restart the bot, pressing f12 and moving around does nothing. I've tried this on my windows 7 64bit pc, and on the vm workstation windows 7 64bit virtual machine.

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

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

Yep, just had the bot get stuck for 7 hours again on another ornate chest, so I can confirm that it happens on ornate chests, at least in catacombs. EDIT: Happened on a third ornate (or maybe it's a large chest? Not sure, the one that has two opening sides).

Found another catacombs bug, but it could apply to other places as well. When using smart pickit and the bot uncovers a large amount of items at once (10+ from an ornate/monster), it will sometimes continuously attempt to check all of them to see if it should pick them up, and won't teleport/logout after the idle timer. Got stuck doing this for about 8 hours last night.

Playing on act 3 on cruel, when the bot goes to click clarissa it tries to hit sell slightly below the box, Anyone able to tell me why it's happening/how to fix it?

Because I recently completely changed my build, I added a good amount of level 1 gems . When there is at least one gem that is ready to be leveled, but can't be because your character isn't a high enough level for it, like above, the bot won't try and level any gems that appear below it, even if they can be. By the time this is fixed I'll probably have manually leveled them all, but I figured I'd point it out. Maybe a tickbox to "check all gems for leveling" so people who don't have this probably don't waste time checking them all. Or only check ones that aren't grey.

The new smart pickit, or the new default pickit?

I noticed that too, bot will walk to catacombs from the waypoint. Thanks for this, almost perfect timing!