View RSS Feed

Blogenstein

Healing Totems & Haste

Rate this Entry
I seem to be posting about Haste on a fairly regular basis at the moment. They’re all important topics, so there’s nothing that can be done about that. In any case, today’s subject is one for Restoration Shaman, and looks at the mystery surrounding healing totem breakpoints.

As you’re no doubt aware, there’s been some confusion about where the next tick for Healing Stream and Healing Tide Totems actually occurs. The mechanics of both were confirmed during the Beta, but our observed values were randomly off, with extra ticks occurring earlier than they should.

One of the theories I had as to why this occurred, which has been partially confirmed (I don't think this will ever be fully confirmed, but it does explain the behaviour) is that server load can add up to 200ms to the duration of the totem. This is consistent with the observed values, where we'd randomly get extra ticks, but the chance of getting an extra tick increased as we approached the next break point.

I'm just going to list the total haste percentages here, for reasons I'll explain shortly.

Healing Tide Totem
Extra Ticks Breakpoint +200ms
1 20.01% 17.61%
2 40.01% 37.22%
3 59.94% 56.80%
4 79.94% 76.44%



Healing Stream Totem
Extra Ticks Breakpoint +200ms
1 6.64% 5.24%
2 20.01% 18.45%
3 33.29% 31.54%
4 46.68% 44.77%
5 59.94% 57.92%



So we're looking at a 2.4-3.9% difference with just 200ms of delay for Healing Tide, while Healing Stream has a 1.4-2.0% difference. It's quite possible that latency contributes to this as well, but the variability of these means that we can't rely on either spell performing as expected.

It's entirely possible to reverse calculate the server latency from observed values. Using some data provided by Therya, who's running with a very nice 95ms latency (well, to me it is, but I'm usually 200-500ms), it's possible to get up to a 600ms delay due to server load.

This means that the desired breakpoints for Resto Shaman go from 12.51% for Earthliving +1 to 24.97% for Riptide +2. Since Haste is generally third place for Resto, it may be that after you hit 871 haste rating (assuming Ancestral Swiftness and a +5% haste raidbuff) you don't get any more, at all.

Submit "Healing Totems & Haste" to Google

Comments

  1. lvlark's Avatar
    This still seems to be off, but I do think my testing might be interesting?
    I usually run VERY low latency (it says 3ms right now, but as long as I plugged my cable and don't rely on WiFi it's hardly ever over 6), and these are my results as of tonight, no raid buff present:
    AS, 1714 haste rating: 9 ticks for 10 out of 10 casts
    AS, 3550 haste rating: 9 ticks for 10 out of 10 casts
    AS, 3950 haste rating: 9 ticks for 10 out of 10 casts
    no AS, 1714 haste rating: 9 ticks for 3 out of 10 casts, the other 7 were 8 ticks.
    Now with my low latency I'd expect this to rarely happen, yet it does.. I'm not sure if I should pay attention to breakpoints at all, since I tend to recall my HST anyway.
  2. Binkenstein's Avatar
    Quote Originally Posted by lvlark
    This still seems to be off, but I do think my testing might be interesting?
    I usually run VERY low latency (it says 3ms right now, but as long as I plugged my cable and don't rely on WiFi it's hardly ever over 6), and these are my results as of tonight, no raid buff present:
    AS, 1714 haste rating: 9 ticks for 10 out of 10 casts
    AS, 3550 haste rating: 9 ticks for 10 out of 10 casts
    AS, 3950 haste rating: 9 ticks for 10 out of 10 casts
    no AS, 1714 haste rating: 9 ticks for 3 out of 10 casts, the other 7 were 8 ticks.
    Now with my low latency I'd expect this to rarely happen, yet it does.. I'm not sure if I should pay attention to breakpoints at all, since I tend to recall my HST anyway.
    That's because it's server lag not local lag. You shouldn't really be aiming for the totem breakpoints anyway.
  3. lvlark's Avatar
    Quote Originally Posted by Binkenstein
    That's because it's server lag not local lag. You shouldn't really be aiming for the totem breakpoints anyway.
    Ah that makes sense. I do hope though, that Blizzard will think of a fix for this someday..
Leave Comment Leave Comment

Trackbacks

Total Trackbacks 0
Trackback URL:
Powered byvBSocial.com and MMORPG