Consecration "incorrectly" counts as a debuff

yay it only gets better…

PrideToday at 10:07 AM

So we did some tests with @Smeet last night and it appears that Consecration ticks are definitely subject to a spell miss check per tick, as vs lvl 53 mobs he missed ~1.5% of his ticks inexplicably, which looks like statistical margin of error on the built in minimum 1% spell miss
There also appears to be some spell batching bs going on if you cast Consecrate on CD, as sometimes the last tick of your previous cast be batched AFTER you have cast your new Consecrate, and you essentially lose a tick from the previous or current cast

ThelorasToday at 10:11 AM

oh lovely

PrideToday at 10:11 AM

We still need to do some research on that, but even THAT does not explain why we’re saying so many missed ticks in raids. Casting Cons on CD resulted in ~3.3% tick loss, so 1.8% more than the 1.5% he was losing due to the base spell miss

PrideToday at 10:13 AM

If the spell miss per tick thing is true, we should be getting 6.64 ticks per cast vs bosses, but a lot of logs seemed to be closer to 5.4-6 ticks per cast
If you guys could go over your own logs, click yourself as source, Summary -> Events, filter to only encounters and hitting the boss, then use this filter expression - ability.name = “Consecration”
You can count “X casts Consecration” events and “Consecration [Target] Tick [Damage / Resist]” events (Ctrl F works too :p) and just remove the last instance of casts and the subsequent ticks since you probably lost ticks due to the boss dying
Then divide ticks / casts, we can get a better picture of real world performance
Batch clipping should not be able to account for 1-1.5 ticks per cast loss, that’s 12.5% to 18.75%, it was only an extra 1.8% on the level 53 mob