Resto Druid haste breakpoints slightly off?

Topics: Rawr.Tree
Oct 27, 2011 at 1:41 AM

Hi there, I always run with a Lock and are lucky enough to get their DI , along with the 5% haste from a Boomkin

So I always aim for the 1573 haste break point,(+ a few)
but Rawr is really keen for me to be over 1600, to the point its skewing the Overall value by a hundred or so.

Am I missing something?

Cheers

Oct 27, 2011 at 6:49 AM

From what I can work out, it looks like you have the Shard of Woe trinket.

From EJ's :-

  • 1573: 9th tick of Wild Growth and Effloresence with Dark Intent. If you have DI, you only have to make it to here instead of 2005 to get this nice bonus.
  • 2005: 9th tick of Wild Growth and Efflorescence. This point is very valuable, as these two spells make up a large portion of our healing.
  • 2032: 6th tick of Rejuvenation with Shard of Woe proc active. If you have a Shard, this is only a small leap from 2005 and makes your trinket use much more effective.

 

I assume that as the 2032 is 27 more haste than the 2005 then 1600 haste is 27 haste more than the 1573 which should be about right for the 6th tick of rejuv with DI and SoW active.

 

 

Developer
Oct 27, 2011 at 7:33 AM
Edited Oct 27, 2011 at 7:34 AM

Last time I checked and according to TreeCalcs, the instant heal from Gift of the Earthmother was buggy and ignored all haste buffs, which should be why Rawr wants you to get 1600+ haste for the unbuffed Rejuvenation breakpoint.
Try removing the Gift of the Earthmother talent points and see if things change; at any rate, the suggestion should be good in general.

However, I just noticed that this results in going for 1601 haste, while instead 1602 might perhaps be needed: I guess I'll try to see if I can get exactly 1601 and 1602 haste and test what happens, as soon as I have time.

Oct 27, 2011 at 8:02 PM

No unfortunatly I don't have the shard of woe, and with its 4.3 nerf, probably never will.

The specific haste sheet is http://goo.gl/wc19m on a google doc, provided by Tangedyn, more info on http://theincbear.com/math/resto-haste-breakpoints

The columns that apply to me are DI+Raid, and DI+NG+Raid, I have been careful to set up the buff section in Rawr,
3% haste from Dark Intent and 5% spell haste from Moonkin form (we have a boomy as well)

I can't tell exactly which haste break point Rawr is going for, 1601 / 1602, I just know its more than 1575, and it still values haste above anything else at 1595
I can put a character.xml up somewhere if it would help.

Thanks for your help

Oct 27, 2011 at 8:36 PM

Ok I have just compared 2 specs, the same apart from 1595 haste vs 1602 haste

  35871.35 35769.63
Haste 1602 1595
Crit 969 1062
Mastery 2101 1995
Raid S.Raid Rejuvenation 4757 4031
Raid B.Raid Rejuvenation 17298 16843

But I cannot see anything with a 1602 haste break point in the haste sheet?

Cheers

Oct 27, 2011 at 10:07 PM

TreeCalcs increases the Rejuv GotEM proc at 1601 (bases it on a 5-tick rejuv at that point).

 

Developer
Oct 27, 2011 at 11:26 PM

As already mentioned, it's most likely the 5-tick breakpoint for unbuffed Rejuvenation at 1602 which is applied to the GotEM instant heal.

Clearly, Blizzard's normal code for computing DoT ticks couldn't be used directly in the GotEM proc code, so they reimplemented it, but did a bad job and failed to account haste buffs; I haven't personally checked whether it also rounds differently resulting in 1601 like TreeCalcs suggest.

Oct 28, 2011 at 12:42 AM
Edited Oct 28, 2011 at 1:47 AM

1601 would set the tick rate at 2.66661s.  For HoT calculations that gets rounded to 2.667s  You'd get 4.5 rejuv ticks at 2+2/3s, so the rounded number is large enough, but the unrounded is not.

TreeCalcs does not do that rounding for its GotEM calculation (but does for all HoT break-point calculations).  I don't know if that omission is intentional or correct, and I don't know what Rawr does.

Edit:  Tested, and 1601 is correct for GotEM.  At 1600 Haste, GotEM was 60% of a non-harmony, normal tick (1723/2870).  At 1601 Haste, GotEM was 75% of a non-harmony, normal tick (2226/2966)