Giles, any idea what could be done to improve rend? The majority of my dps comes from keeping this as close to 100% uptime as possible on surrounding mobs. I know not everyone wants rend prioritized this way, but perhaps a "rend spam" check box could be added in the plugin settings? Basically anytime there is a mob within rend range that does not have rend, just have it rend again.
THANKS for all your hard work on this.
Is there absolutely no way to check debuffs on the target? if not, well atleast let us have a timer to always cast it every X second if target is within range of course
1.4.1 doesn't seem to be using Rend at all.....
There is no way to check for debuffs on targets. Atm rend is set to;
- not use if you have <75 fury and wrath/berserker/earthquake is ready for cast and wants to cast, so it doesn't keep spamming rend and prevent a power-ability.
- Spam 4 seconds by default...
- OR Reduced to 1.1 seconds *IF* more enemies are in range than when last rend-used (eg if last rend only hit 1 enemy, and there are now 2+ enemies within 9 foot)
- OR you are at 65% max fury spam every 3 seconds instead of 4... reduced to 1.8 seconds if your current, primary target has changed (eg you are actively targetting a different mob to when last rending).
While I personally can see no reason to spam any faster than any of these situations, you can change this to experiment yourself. Find the rend code by searching for the phrase "Rend spam" within the code. Below this you could try lowering those various timers. You could also simply try reducing the main timer of Rend by replacing this line (which is found elsewhere);
{SNOPower.Barbarian_Rend, 4000},
With something like;
{SNOPower.Barbarian_Rend, 1200},
To justs pam at 1.2 second default instead of 1.4
1.4.1 seems to get me stuck quite often compared to 1.3.1, and just saw it ran past a elite pack with 3 mobs i was like.. whut?
Did you follow the "Updating" instructions on post #1. And be honest. If you did, did you try going through the "common problems" section of post #1? Be honest again. I don't mean to sound patronizing/rude, but I have found many people simply *SAY* they did a fresh install of DB, or *SAY* they followed instructions, when they didn't - because in their heads they don't believe following those instructions will actually do anything, and so they hope that by saying "yeah I did that, didn't work, what next?" they will get a magic solution.
If you *DID* those things, and you still have problems - let me know what type of mobs they are, and what routine/profile you were on (and in what part). Some routines/profiles set a very low kill-radius in particular parts of the map, to help avoid stucks, and my plugin will max at whatever kill radius the routine sets.
lol i went back to 1.3
msg to giles:
I feel you are over doing this plugin fixing to much and causing to many bugs errors your best work was 1.3. Ver 1.4 was decent too I think your over working this plugin and cause to much headache for yourself.
I could just go back to not doing any plugins at all and have no "headaches"?
This plugin does a lot. It's a complicated piece of work. Most people have no issues. Those that do - many of them didn't
really try the common fixes (deleting commonassemblies folder, deleting settings file, or a truly fresh install of Db without ANY copies files from the old folder). Those that still have problems - I can't help you if you don't explain the problem fully. Simply posting and saying "nah, don't like, going back to older version" is about as useful to me as a chocolate teapot is to somebody who has a phobia of chocolate. And teapots.
I'm reverting back to 1.4 first time doing that - 1.4.1 is not using Revenge, is not using Rend - stucks much more aswell, and yes I installed it correctly
Stop DB. Enable the status bar for debugging (in the advanced tab). Run the routine. Now when you stuck, explain the stucks in detail to me. Are you stuck trying to reach a monster you can't reach? Are you stuck trying to avoid things? Are you stuck standing behind every chest you try to open? Or are you stuck in a certain part of the map after fighting a monster because of the routine/profile you are using (which now that 1.4.1 has fixed the issue of incorrectly using a lower kill radius than was set by the routine, may be an indication that 1.4.1 has highlighted problems in the routine you are running that earlier versions were simply covering up). Try changing the timers for revenge to those above.
As for Revenge and Rend in general, one other thing to try would be this. In both the Rend and Revenge checks, change this small piece of code;
"targetCurrent.fThisDistance <= 9f"
To;
"targetCurrent.fThisDistance <= 12f" (or 11f or 13f - will need experimenting with).
That exact text is found in both the revenge, and the rend use - and might be the fix we need. I do need users helping me by experimenting and making code tweaks themselves, and then letting me know if it works or not - because frankly I can't test every single skill on every class in every situation myself *AND* keep working on other stuff.
@Giles: is there anyway to prioritize goblin over anything else, I saw my follower proc a goblin during Azmodan and it was very close, yet it totally ignored the goblin, also why is it that the bot clears trash before an elite pack? it's the most time waster for me personally, just get in there and destroy the pack then move on
The bot doesn't aim for trash over elites - but melee characters do have some preference for closer stuff - elites do get a hefty bonus, but the range of mobs might mean that it goes for the closer-things first, which as greys outnumber elites when you first meet packs, can mean greys get targeted. It will also add extra priority to mobs on low health - and given that greys frequently hit low-health within a hit or two from your follower, can mean the bot will go and "finish them off" with a quick hit since it detects a near-dead target.
