Threaded Mode | Linear Mode

[email protected] · 04-20-2015, 09:34 AM

Has the bot been buggy for anyone else lately? seems like it would run smooth for maybe an hr or so. when i come back after a couple of hours the bot is stuck in on position and it doesnt seem like it did anything. I left the bot on over night ran for maybe 7hrs give or take. when i came back it was stuck in one position and also it looks like it barely ran anything or did anything. and when i come to bounties, samething..run it for long hours and come back it would be only like 2-3 bags....i also notice that the ping is like 300+ for me. is that any affect on the bot?

gimmeryce · 04-20-2015, 04:12 PM

I ran A1 Bounties overnight and it did around 2caches/hour which is kinda slow but I still ended up getting 17 caches. The problem I have is that after a little while, the bot stops using 5 of the 6 skills, so my Firebird Wizard is only using Magic Missle for some reason. I watched it for five minutes and buffing skills (Magic Weapon, Sparkflint) we inactive and it only attacked with the left-click skill.

tcujazzartist · 04-20-2015, 05:40 PM

(04-20-2015 04:12 PM)gimmeryce Wrote: I ran A1 Bounties overnight and it did around 2caches/hour which is kinda slow but I still ended up getting 17 caches. The problem I have is that after a little while, the bot stops using 5 of the 6 skills, so my Firebird Wizard is only using Magic Missle for some reason. I watched it for five minutes and buffing skills (Magic Weapon, Sparkflint) we inactive and it only attacked with the left-click skill.

Have the same issue, but it seemed to be fixed with the newest update. The bot is actually on 0.9.363 instead of 359. The announcement post hasn't been made yet for some odd reason, but try to update the bot and it should fix that issue.

gimmeryce · 04-21-2015, 01:59 AM

(04-20-2015 05:40 PM)tcujazzartist Wrote: Have the same issue, but it seemed to be fixed with the newest update. The bot is actually on 0.9.363 instead of 359. The announcement post hasn't been made yet for some odd reason, but try to update the bot and it should fix that issue.

Yeah I updated to 63 but same issue :\