It's just a ad, wait 5 seconds, and then press skip ad on the top right corner. Then it will redirect to download page.
Open belphagore combat routine, turn off all avoidance checkboxes. Avoid arcane / plague / etc. Did more harm than good to my guy.
so turn off all avoidance function ? do you use leap ? I using sprint to speed up farming . Do you think I need to switch that skill out ?
your block is very low make sure its a sacred shield im at 47% block on all my bots and hardly get scratched
Constantly gets stuck in the cursed hold, right above the entrance to Halls of Agony Level 3, it try to enter the door from above, doesn't realise it needs to go to the left and down the stairs. Ports back to town and runs the profile again, but ofcourse everything is dead so it is just time wasting now i know why the graph on buddystats always had some real long lows in it. G
I get the same thing. Also it has a hard time destroying logs and small rock piles which i often get stuck at... funny how it circles around the rockpile or just keeps on trying to do something to the log. Anyone got any advice on this? I have Giles world object,strash replacer,mob prio.
So I tried 204 with 2.0.2 profile and turned off avoidance. I tried using sprint as a barb to make farming faster, it did. But can sprinting fuck up the dungeon navigation? Because it doesnt seem to enter HOA 3 and gets random stucks?
Sprint isnt what fucks up the dungeon navigation. Demonbuddy's terrible dungeon solving is what does it Do the smart thing and just use 1.9.2!
I have a problem when the bot tries to target an elite that is surrounded by white mobs. When it's not able to hit the elite it will just stand there(the bot will also get really laggy at this time) and take damage from mobs, plague, desecration, etc. It usually ends up dying. I have leap on my skill bar but it doesn't always get to the elite. Anyone have any solutions to this problem?
Increasing "Ticks per second" in belphegor settings tends to help, but it doesn't fix the problem. Not sure if there's any real 100% fix, it seems to be a DB issue... (but change the ticks per second, it does help!)