No, not every spec. Though the ones that don't have one aren't normally considered offensive casters.
As for the source, it was in the big TC thread during the 5.2 PTR, though i erred on their being additional clarification, it seems. The numbers were simply given as the proc rates, not coefficients.
Bolded + underlined the relevant bits.Sinister Primal Diamond – 1.18 base RealPPM on damage/absorb of harmful or periodic spell. No ICD.
- That base proc rate is multiplied by an additional coefficient:
0.302 Fire Mage
1.387 Frost Mage
1.000 Anyone Else
Use the melee meta as an example, if you want (their "proc rates" were also included in the post you're referencing):
Now, the post before says the capacitive meta has a 21.00 base RPPM rate (analogous to the 1.18 for the sinister primal diamond). Do you really think all of the melee specs just have 5-10% of the base proc rate? Who uses 21.00? Or is it more logical to assume that these are coefficients? (hint: yes)Originally Posted by Blizzard Entertainment
Fortunately, we don't have to make assumptions. It's very easy to test.
1195 applications of capacitance in 43.65 minutes of sustained combat against a dummy = 27.38 procs per minute. Unless it's your contention that this enhancement shaman is rocking 3385% haste (27.38/0.809), I think it's far more likely that the 0.809 "proc rate" is, in fact, a coefficient being multiplied by the base RPPM rate of 21.00 - just as 1.872 is the coefficient for balance druids for the sinister primal diamond, with 1.18 being the base RPPM rate.
(note: WoL says 956 applications of the buff, but that's because the buff only stacks to 4 and is immediately consumed on the 5th stack. If you multiply the number of lightning strikes by 5, you'll arrive at the correct number of buffs (1195))
* EDIT: Taking the enhancement shaman example a step further...
13983 base haste rating, with 82% uptime on flurry = 19716.03 effective haste rating (46.39% haste from gear)
1.1 (ancestral swiftness) * 1.4639 * 0.809 * 21 = 27.36 predicted (observed: 27.38)
Last edited by Nitwit; 2013-04-19 at 10:59 PM.
Seems like it was stealth fixed after a couple of tweets to gcer about the topic on US forums
not sure if its been fixed on EU though
Last edited by Fleuria; 2013-04-20 at 11:58 AM.
shitty thing about the higher proc chance is the fact i've found alot of the time the meta has just been overwriting itself with like 6-7s left thus greatly reducing the uptime while testing on dummies.
I'm pretty sure Blizz accounted for that effect when setting the proc rate. So even if they did something to prevent that from happening, they'd just reduce the proc rate to keep the net effect the same.
Was the mage specced fire? Uptime sounds about right for that.
Last edited by huth; 2013-04-20 at 04:38 PM.
Bug != forgot to implement.
Also, pure overwrite protection would actually lower the uptime further, as you'd lose those 3-4s extra from procs at 6-7s left as well.
Tempus Repit 22 185.5 39.9 % #
From a 7min council fight, it does indeed seem fixed.
These logs pretty much speak for themselves:
10 fights, boomkin vs. fire mage with the Legendary meta. 142 procs for me, 25 procs for the mage. Boomkin modifier is 1.872, and the Fire mage modifier is 0.302. As a crude comparison, 142/25=5.68, and 1.872/0.302=6.19, which are roughly the same so the change is definitely in.
Since the meta has been fixed, I'm closing this thread.