What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

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

the only thing I can think of is adding a way to cast CB when there are a number of things active. For instance, I would like CB cast when i have Jade serpent + some other int proc, but not if just 1 of the 2 is active.
 
Oh, I must have missed that. It may just be lag but I got silenced a few times from his screech. Where can I get the HB Beta Build to try out the fix, by the way?
 
Hi Millz!

I'm using Honorbuddy Beta Builds and the CR isn't refreshing Doom on UVLS's proc for demo spec.

Btw, excellent work!
 
Hi Millz!

I'm using Honorbuddy Beta Builds and the CR isn't refreshing Doom on UVLS's proc for demo spec.

Btw, excellent work!
There are some things that he has to revert back to once the new build of HB is pushed. He had to do some "work arounds" to get it working with this version of HB. I'm sure once the new build of HB is pushed and he reverts back to his original coding setup then things will work properly.
 
the only thing I can think of is adding a way to cast CB when there are a number of things active. For instance, I would like CB cast when i have Jade serpent + some other int proc, but not if just 1 of the 2 is active.

There's no easy way to do that tbh. Nice idea but implementing it would be a bitch.

Oh, I must have missed that. It may just be lag but I got silenced a few times from his screech. Where can I get the HB Beta Build to try out the fix, by the way?

It doesn't cancel the current cast - only stops casting - that'll prevent 3 seconds of downtime constantly (as opposed to 2 seconds from being silenced). If it turns into a major problem then I could cancel cast when theres X milliseconds remaining, but see what it's like when HB updates.

Hi Millz!

I'm using Honorbuddy Beta Builds and the CR isn't refreshing Doom on UVLS's proc for demo spec.

Btw, excellent work!

Hey - Can you post a log? I've not had a chance to test the beta build out yet - but it used to work perfect so would suggest it's HB that has the issue.
 
Yeah millz, sadly I dont see how affliction can ever be very viable without the ability to snapshot multiple procs. That's kind of the only skill involved with the affliction rotation.

Dont get me wrong, this CR is God like for destruction. (aside from the little errors that happen, which you said are being resolved in the new release of HB) I just have been playing warlock for a long time and am no slouch. I am not the best in the world by any means, but i can out play the affliction CR without much effort.
And i think its entirely due to snapshotting. I could be wrong, but its my opinion.
 
Yeah millz, sadly I dont see how affliction can ever be very viable without the ability to snapshot multiple procs. That's kind of the only skill involved with the affliction rotation.

Dont get me wrong, this CR is God like for destruction. (aside from the little errors that happen, which you said are being resolved in the new release of HB) I just have been playing warlock for a long time and am no slouch. I am not the best in the world by any means, but i can out play the affliction CR without much effort.
And i think its entirely due to snapshotting. I could be wrong, but its my opinion.

You refresh DoTs on minor procs by hard casting them (with diagnostic level logging you'll see the log spamming messages about DoTManager). For large procs, you refresh them using SB:SS and cast Haunt etc.

You wouldn't waste a shard for SB:SS to refresh DoTs on a jade spirit proc (+1650 int) - whereas you would do it on one of the new trinkets (+5084 intellect).
 
You refresh DoTs on minor procs by hard casting them (with diagnostic level logging you'll see the log spamming messages about DoTManager). For large procs, you refresh them using SB:SS and cast Haunt etc.

You wouldn't waste a shard for SB:SS to refresh DoTs on a jade spirit proc (+1650 int) - whereas you would do it on one of the new trinkets (+5084 intellect).

ok.
 
On a side note I get those errors with both the current release and the beta.

Yeah, all but 1 of those errors is caused by the routine (it's nothing major though!). I've found 4 potential exceptions which I've fixed. Will be fixed in the next update.
 
i test affli on beta with milz cr on multitarget 4 25k-30k dmg +% nice nice more DOTS pls !more dots

SimulationCraft have updated their profile for affliction today, and it's got some interesting changes. I don't agree with how they're doing Soul Swap - it's a bit poor, but changes to Haunt might work.

Once I finish with this aura proc stuff I can get stuck into affliction a bit further.

*Edit* SimulationCraft profile link for anyone interested; https://code.google.com/p/simulatio...profiles/Tier16H/Warlock_Affliction_T16H.simc
 
sorry i mean 25k-30k DPS + not dmg ^^ but it feel much better soul swap recat much faster love it ! on beta pvp gear ( play only pvp)

Edit: pvp gear( play only pvp)
 
sorry i mean 25k-30k DPS + not dmg ^^ but it feel much better soul swap recat much faster love it !

Yeah, and it's still bugged from being a bit slow. Once HB's issues are resolved it'll be on fire :)
 
Here's the log about UVLS's proc Millz! :)

In that log it only caught the buff once where it managed to get Doom off.

[14:35:47.177 D] [Demonic ~ Debug] [DoTManager Added - Doom] [Int:33847] [SP:46097] [Crit:122.7056] [Haste:0.8404026] [Mast:53.71667]

The only other place it looks like it goes off is here - but it looks like it leaves Metamorphosis form right before the proc activates (which is just unlucky);

[14:40:12.520 D] [Demonic ~ Debug] [DoTManager] [Crit Buff - Refresh!] [Increased by: 99.31641]

Either the bots not seeing the DoT, or the trinket isn't going off. You really did just get unlucky with that second one - but the bot doesn't know when it's next going to proc so can't avoid that.
 
Back
Top