I've been using many bots, profiles, with a lot of success. But there's a handful of characters and situations where the bot will target a mob, and just stand there, till it DCs for inactivity. Recent example is my druid I am leveling, using JungleBook CC, and kick's questing. Around level 20-23, he just would target a mob, and stand there. If I manually moved him, he's get going again. I'm not sure if it's the pull radius (set to 25) or what. The other time I saw this was with a 85 hunter, farming SM for silk, on the final boss, using fpsware. Any idea what these symptoms would mean? What other info do you need to help? Thanks for everything.
Hey Eyrus, there was indeed a bug within JungleBook that causes this error. Can you please try it again? Grab the newest version and post a log if it happens again. I fixed this behaviour yesterday
I love the quick response! I had to finish shuffling some ore I bought, so I took a bit. @Handnavi I have the latest Junglebook as far as I know, updated in HB. This issue manifested about 6 hours ago. Running it again now to see if I can reproduce the issue... Okay, did it quick. Posting logs, gonna try Singular (want to count out CC)
BTW, looking at the logs, it seems rather uninformative, as it just says...nothing. But FWIW, the debug tab gives no hints either. (.NET programmer myself...)
Dropping pull distance to 10, seems to work better. Admittedly I am not sure of the effect of this, but it seems to help...
Hehe, in this Log i see that JungleBook updated to rev 123 - this version fixed these pull bugs. If you did not restart HB allready please do it now.
Awkward! My SVn shows it as updated 3 and a half hours ago, I had not tried it in that span, nor restarted HB in that time. Looking at the code, it looks like you indeed addressed my issue, might I ask what the proper pull distance in HB is then? Trying to get this MOSTLY AFK ready, though I do have teamviewer to get out of trees when necessary Also, thank you so much for you contribution! Working on my own at the moment ;P
Jup, i looked again into the issue you mentioned and tried to fix it! Every pull distance should work now.