Well there have been some cases. Try to use some of the tank DH builds that you can find on various forums.
I've noticed that the bot will, on occasion, skip loot. I fired it up this morning and was watching in the background. Took down a champ pack and an arch axe dropped but the bot kept fighting for another 10-15 seoconds as there were a pile of other mobs around. After they all died, the bot hauled ass to the next waypoint. Seen this happen a couple times before as well. I had to manually move him back to grab the loot. Any ideas?
3 possible ideas; 1: Common DB bug mis-reading items and failing to recognise the item type so it got ignored. 2: Your loot-rules aren't loaded properly/are bugged/don't work with whatever version of DB you use/are too complex. 3: DB will ALWAYS chase monsters within kill radius first (if it's elites). By luck this can mean your character ends up far away from some loot by the time it kills the mob. If that loot is now out of loot radius, it won't be picked up (unless by chance the bot takes your character back close to that location anyway, eg to get back to a specific waypoint). There's not a lot you can do about #1 or #3
Hello again, I've been watching the profile trying to think of a way to help improve run speed. So far the best I have come up with and I'm not entirely sure it's possible. Think it would require an IF command, it would kind of be an extension of the Giles Monster Handler project. The easiest way I can think of to relay my idea is pseudo code. here would be the "WP call" with an added tag to ignore combat until next tag unless there is an elite here would be the next "WP call" with combat here would be the next "WP call" with combat here would be the "WP call" with an added tag to ignore combat until next tag unless there is an elite Ultimately the idea is to bum rush around A1 ignoring almost all mobs except elites. In my mind this is a secondary version of the original profile for those who can walk through 10 skeleton or zombies without much trouble. The Cemetery + The Weeping Hollow is my first thought on where to use this idea. Giles's plugin I think is great for people who can't handle being beat on by regular mobs but I think for those geared enough to fight in A3/4 reasonbly we need something even stricter on what it runs past. BTW Radonic I'm gonna try adding a new zone to your A2 Profile with the mapping plugin. I'll let you know if it works out.
1 - bummer... 2 - I'm actually using your stashreplacer w/ the lvl 61 rules. They work great by the way! I haven't seen this happen too often but oddly enough, it was with an arch axe the first time as well. 3 - I guess I wasn't aware of that. I probably have my kill radius set too high for my barb (it's at 40) and my loot radius is 110. I'll play around w/ the numbers a bit and watch the bot throughout the day.
How are you guys handling stucks? I get stuck once every few games, and unstucker 1.8 doesn't seem to get me unstuck. Profilerestarter freaked out and kept moving me for ever, but then never shut off. It ran me half way across the map randomly. Manually Quit that game, manually unstuck the other games. Not sure what to do for stucks, so I can actually afk the profile while i sleep.
GilesMonsterPriorityChanger GilesStashReplacer GilesWorldObjectHandler Profile Restarter Unstucker v1.8 Currently I have Profile Restarter disabled, it freaked out and ran me half way across the map. Unstucker is enabled, but didn't fix a few stucks I had. I came back to my toon stuck in the weeping hallows a few different times.
Ok, next time it gets stuck I'll post both. Do you use profile restarter? If so what settings do you use?
Hi, Just want to make a remark. From version Version 1.7 where you changed the starting area, the gold/hour has decreased significantly. This is because when you started back in Leorics M. the chances to get Nephalim V. right at the start were greater and this payed off while clearing the starting areas. Now it takes a lot more time to reach 5 stacks of N.V. Anyway. Thanks for your efforts.
It was moved because i added the Hunting grounds to the profile and it would make more sense when i looked at Diablofans.com forum for how most people farm act 1! I dont do things just to fuck people over, this moved was because my researched showed that ALMOST everyone who farm by hand start at graveyard and then move through hollow and pretty much go through the Waypoint list. So i my intentions where that when you use my profile, you would be "one in the crowd" because thats the only way to camouflage yourself to statistics... Hope you understand why i did move it.
I was actually thinking about this today too after watching my bot for a bit. In addition to your suggestion of ignoring normal monsters at certain WP calls, I think one big way to improve the speed of runs would be to provide alternate pathing routes after a set of criteria is met (i.e. an elite pack is killed). For example, right outside Leoric's Manner, there is always a pack of champion cultists. Usually they are right outside the door and engage you the moment you zone there, but sometimes they are up the stairs somewhere else in the courtyard. Well, the profile basically runs through the entire area to make sure you didn't miss them. It does this even after you've killed them during those times when they're right at the beginning. So you'll zone out, immediately engage and kill them, then spend the next 20 seconds running a gauntlet of WP calls. What I propose is: The above should theoretically save you a good chunk of time on almost every single run, and the logic can be applied all over the place in other maps. Unfortunately, it adds a significant layer of complexity when you're dealing with all kinds of potential routes the bot could take, and might make handling profiles a nightmare for authors themselves. But for those wishing to obtain perfection and peak efficiency, it would be worth it. Anyhow, I'm not entirely certain this functionality can even exist in profiles (if/then/else and variable/flags), but I imagine they'll implement it eventually if it doesn't. Food for thought!
Had the same problem. You need to uncheck the DBE (Demon Buddy Enh.) Plugin. After that it worked without any problems.
