[PAID] [Warlock] Demonic - An Advanced Honorbuddy Warlock Routine [PvE/PvP]

Destro is amazing .. when you set the settings right. using kink's setting jumped my dps by avg 60k on each boss i could just imagine what a couple more tweeks would do.

 

Ha sorry, got distracted by the world cup. It's up now though.

Post a log file

It's not soul swapping because you've got AoE disabled.

The manual cast detection over-rides the hotkey stuff. Use a modifier key (like shift+q) and it won't trigger the manual cast pause.

Facing -> Again, enable the setting.

Mannoroth's Fury -> Update from SVN - think you're on an old version.

Post a log file please

 

Is anyone else having trouble when using Questing? I did just level a Warlock from 1 to 90 using Kicks profiles combined with some DungeonBuddy and thus far the presets PvE and Questing has been working really well. I'm going "Destruction" and the only thing I have fiddled with in the settings are the two Framelock Anti-Lag and I have set "Auto Summon Demon" to Auto instead of Voidwalker / Voidlord"

But during questing the bot will have a hard time actually attacking mobs at times. It doesn't seem to matter if they are natural / passive or red / aggressive. A lot of times the bot will target a mob but stand there doing nothing, it's not sending the pet / demon to attack, nor does it use any abilities at all. It will sit there until Honorbuddy logs out because of inactivity, but I got HBrelog running so it will log back in and then all of a sudden it will start killing and keep on going for anything from 20 min to several hours until it will all of a sudden get to another mob where it wont attack, nor send the demon / pet so it will stand their idle if the mob does not get within aggro range.

This is really slowing down my efficiency a lot. And I had to disable "log out due to inactivity" in Honorbuddy settings due to the fact that logging out due to inactivity will send a message to HBrelog to not log back in again and this of course increase the risk of the bot getting stuck and various other things.


I'm not entire sure what may cause this behaviour? I was going to simply set the pull distance low enough to make certain the bot will always get aggro when attacking / targeting mobs as that would automatically solve the problem but I can't seem to find any option for setting pull distance in the settings?


I'm using Demonic Premium (paid version) and I've tried to do a SVN update but it's still happening from time to time.

 

Post a log file from where this has happened please. Could try enabling force combat too?

 

I had the same problem, altho I don't have any logs from it.

Also, my problem was that the bot seemed to ignore to engage neutral mobs/passive mobs for some reason which led to me having to help the bot.

To bad I dont have the logs... :-/

 

I will try to replicate it and post a log when I get back from work. I will remote home and enable Forced Combat to see if that might help.

 

hey guys , the new HB version is good now? i mean we can use it even if there is more than 1 lock nothing will effect? plz let me know thanks <3

 

Cheers. Yeah I'll need log files for this issue.

Yeah it's fine.

 

found a possible improvement for affliction.
The routine is correctly waiting for a high int proc to pop dark soul but doesn't refresh dot on main target before swapping them around.
example: 4 targets, dots rolling, immerseus trinket procs and routine pops dark soul but then just continues to soulswap dots around not applying boosted dots first on a target and then ss-ing them around.
Also on pull it wastes shards by refreshing dots proc after proc.
example: you pull with pot + haunt, routine applies dots with SB:SS, then after another trinket procs it uses darksoul and refreshes dots again. you could make SB:SS have internal 2 sec no cast after initial application of dots maybe or something.
sometimes it uses it 3 times on pull putting you on 0 shards in just a couple of seconds.

I've been trying out affliction with a friend with simmilar gear and he's pulling 1.4 mil on start and after 100mil damage around 1.1 mil on 4 target dummys. Routine pulls 900ish and drops to 500ish after 100mil damage, that's a big difference. Still trying to find out how to improve it

Problem is also it ofter doesn't have a shard ready before using DarkSoul. You could make it have atleast 1 shard before using darksoul on trinket proc to ensure it can do SB:SS afterwards.

 

nice to see u also here nilrem, means good supp for affliction^^

 

Thanks for the post.

It does have an internal delay of 1 second. It was reduced down from 3 as it was missing catching procs before they expired. I'll increase this delay to 1.5 seconds (which should cover 2x GCDs). 3x SB:SS on the pull is pretty standard...

1x Initial application
1x Trinkets procced
1x Application before least trinkets expiring

Will add in minimum 1 shard before Dark Soul on trinkets.

 

what is happening is:

1x initial application
1x trinket proc
1x more procs or second trinket
0 shards left since u start with haunt
not every time but quite noticeable

regarding dark soul try to make it not use shards 10 seconds before it comes off CD and save 1 shard for DS. If you have 2+ shards then it can use 1 before DS comes off cd.

 

couple more questions also. That setting "any duration refresh power" does it only applies to reapplying dots or also for SoulSwapping from other target.
Also does it take into account the predicted damage dots will do in regards of their duration when soulswapping from another target or just the power of the dots (tick strengths) ?

example: target 1 has all the dots and in their remaining duration they will do 500k damage, target 2 has all the dots and in it's duration they will do total of 400k damage but since on target 2 duration is much lower than on target 1, which means empowered dots are on target 2. Will it soulswap from target 2 to target 1? Since that would be actually a dps decrease.

 

I'll put in a check for <= 6 seconds prevent haunt and see how it goes. 10s on everything seems a little too long.

Nah doesn't work like that. It goes off the DoTs duration + power rather than overall predicted damage done. Most of the time the unit with the longest duration on the DoTs has the most powerful DoTs too (since we refresh on procs), so it's just swapping around for whichever has the lowest remaining time on the DoTs.

The any power refresh is a bit redundant at the moment. That only triggers when there's no shards for SB:Soul Swap (SB:SS isn't required).

 

if any power is redundant then on what percentage is the routine actually going for soulswapping from 1 mob to another?

 

Swapping from 1 mob to another is just constant to keep the DoTs rolling.

[video=youtube;JXymugBjoJQ]https://www.youtube.com/watch?v=JXymugBjoJQ[/video]

 

yup and on that guide you can see sparky doing 1.7 mil dps. I'm 584 ilevel and with demonic can't go past 1.2 mil.And in mid fight his dps drops to 1.2 mil prolly till the end, mine drops to 600k. That is double the difference. So I'm trying to find out what needs improvement

 

In the video he's swapping to all units which don't already have all of the DoTs, and then aims to swap to units with the least duration remaining on the DoTs after that. You've always got to exhale -> inhale to keep them rolling however.

Should be doing more than 1.2m at that ilvl. Can you post a log file please?

 

One other thing on what percentage will routine use SB:SS to apply empowered dots or it just does it on trinket procs from the table?

I doubt I have log from protectors but I can make you a log on 4 dummies where I can't go over 900ish burst while my friend in same ilevel does 1.4 mil if you want.

I'll just find a flex group and make a log on protectors.

 

It just runs off the amount of trinket procs in the aura list - that's the main reason I want to see the log file - you pretty much want all 'good' buffs ticked. Things life lifeblood / lightweave(?) etc can be skipped as it's only a small increase, but any trinkets, heroism, dark soul etc should be enabled.

Log from dummies is fine (probably easier to analyse tbh).