Yes, that's bot coding. All the profile does is give waypoints for the bot to follow along. The targetting, how the bot moves to get there, and skill usage has nothing to do with this profile.
After coming home from work, no gettting stuck. I do wish it was more gph, I am going to tweak my routine and get more GF see if that helps
Have same stats... Share which profile you're using, loot/kill/break values, skills and skill stats? (when they're used) Would be awesome
I had the same as ronso an hour back but now im at 300k GHP again. Anyone got an idea why the GHP is so unstable? I let it run for an hour and got 290-310k GHP and earlier today I had 400-450k.
http://www.thebuddyforum.com/attach...rking-core-arreat-a3-nightmare-runes.jpg.html http://www.thebuddyforum.com/attach...rking-core-arreat-a3-nightmare-build.jpg.html 40/40/40 for loot/kill/radius
Oh I already copied that on another thread from you haha. What Profile you use tho and what loot range?
I prefer 0,5 sec moar of smokescreen at 100% xD dnt know, already tested and its best (for me) with that rune
Hmm ok.. Apart from that my build is exactly the same as yours. Going to test your profile I guess. (Once these nav problems are fixed)
Code: [21:03:07.832 D] Waiting for path request to finish... [21:03:07.966 D] Generating path to First Anti-Stuck checkpoint - <523.6755, 658.4722, 0.1000153> [21:03:07.967 D] Waiting for path request to finish... [21:03:08.099 D] Generating path to First Anti-Stuck checkpoint - <523.6755, 658.4722, 0.1000153> [21:03:08.099 D] Waiting for path request to finish... [21:03:08.237 D] Generating path to First Anti-Stuck checkpoint - <523.6755, 658.4722, 0.1000153> [21:03:08.237 D] Waiting for path request to finish... [21:03:08.371 D] Generating path to First Anti-Stuck checkpoint - <523.6755, 658.4722, 0.1000153> This