It could be that a GoSF just sees how many ticks you would get from a 3s MF (2 ticks for any normal amount of haste) and adds that to the MF. At 67% haste, that would increase to 3 ticks.

It could also be that GoSF sees how many ticks you would get from adding 3s to the current duration (starting after the next tick). That would typically be two additional ticks, but in conjunction with a large change in Haste, it might be more than that (or even a reduction in the number of ticks).

It could also be that Blizz just decided that adding 2 ticks was easier to implement (and usually correct) and did that.

If GoSF updates MF haste, you probably want the third SF to complete with NG. That would argue against using IS shortly after Eclipse.

Ok, haven't had time today to finish off the multiple items with same item ID issue, uploading the change that puts a blank entry on the reforging dropdowns for now.

After doing some tests, I believe I've come to the conclusion that the tick rate is recalculated when Starfire lands.

Duing my first run through, I would cast Moonfire, then immediately cast 3 Starfires. The result was an astounding 21 ticks (normally, I would only get 11 ticks). I then ran a test by casting Moonfire then delaying the Starfires until after Nature's Grace expired. The result was only 18 ticks. Here's where things begin to get extremely tricky though... When I cast IS first (to get Nature's Grace up) then immediately extended the Moonfires, I wound up with only 20 ticks of Moonfire, instead of 21. I didn't bother waiting until after Nature's Grace expired to see the result, I have no doubts that it would have been a lower tick count.

So here's my major question. I've proven that the tick rate is recalculated when the spell lands, but then how is it possible to gain an extra tick by extending with Nature's Grace active, when it was not active during the application of the ability? The only conclusion that I can reach is that it recalculates duration and tick rate based on the remaining duration and the tick rate of the spell already active.

Considering that a) the tick interval depends on haste and b) DoTs now always seem to end with their last tick, it was to be expected that the glyph wouldn't be giving a consistent additional 3 seconds. From a design perspective it doesn't even make sense for the glyph to still add 3 seconds now that MF ticks every 2 seconds so I expect it either to be an oversight from when they reduced the MF tick interval or an estimation to make the tooltip less complex.

It's not though. The most bizarre facet behind this glyph to me was that the number of ticks for both Moonfire and Sunfire were either exactly equal or they were within 1 tick of each other. This was consistent with every single test I ran, except in cases where I had cast 1 more Moonfire/Sunfire than the other.

If I were always casting the DoT then 3 Starfires immediately, I could understand this behavior. However, in practice there is a large gap between Sunfires and Starfires, which you would think would throw off the entire tick-rate. In practice however, that doesn't appear to be the case. Therefore, as long as your haste remains constant I believe the number of additional ticks gained through Moonfire and Sunfire is also constant. As long as you have NG up every time you cast a DoT and every time you extend it (which we do), then the number of ticks gained from the 3 extensions should be the same.

I have no way to back this up yet, but that is how it appears to be working based on the tests I did on a training dummy. It's either that or this is just simply a massive coincidence.

Now that I think about it, I'm not totally sure why I expected it to depend on exactly when the refresh occurred, so long as the tick rate is constant. After 1 refresh, you'll wind up with however many ticks you would have bad on a base 21-second DoT, regardless of the precise timing. The only weird issue is if tick rates change.

Did you ever upload a TreeCalcs with updated item list somewhere?

I'll get one uploaded with the recent changes shortly (next couple of days). Wanted to make sure OO was working properly before I did all of the stuff for it again.

Did you enable OpenOffice mode before testing?

Now that I think about this more--what precisely does happen when you extend a DoT?

Say I have a Moonfire with a 1.8s tick time, 18s duration. On cast I get an 18s debuff with 10 scheduled ticks. Somewhere in there I cast SF to extend. Now 3s are supposed to be tacked onto the end of the debuff. Since that's not integral, I think it rounds to 3.6 sec. So I get a 21.6s, 12-tick DoT with one refresh (best I can remember from what I observed on beta).

But what happens on the second refresh? I doubt that it records that the length of the DoT "should" be only 21s and extends to 24. I imagine it tried to add 3s again, which will again be rounded to 3.6. Is this what you were getting at above, ace?

In other words, if your MF tick rate is between 1.2s and 2s, you should always get exactly two ticks from a refresh?

I'll see if I can check this in-game, before I worry about changing haste buffs.

More of a 'why does this happen' question than anything else.

When I toggle Bloodlust 'on' my current stats go massively into the negative.

eg
Without BL

With BL

Now, I'm assuming that popping Lust doesn't immediately cause all my gear to become worthless, so I was just wondering if anyone knew what was going on here?

This is with the 110113 PTR version of the sheets.

edit: Thanks Hamlet - I don't think I'd ever hit F9 on WrathCalcs before. Made quite a lot of difference to the numbers I'm seeing!

Yes I enabled OO mode on the charsheetdata page.