http://worldoflogs.com/reports/rt-5d...9/?s=711&e=963 32.9% uptime Durumu
http://worldoflogs.com/reports/rt-5d...?s=1299&e=1570 30.3% uptime Primordius
http://worldoflogs.com/reports/rt-5d...?s=2088&e=2268 22.6% uptime Dark Animus(No Bloodlust tho)
http://worldoflogs.com/reports/rt-5d...s=9970&e=10424 23.8% uptime Iron Qon
http://worldoflogs.com/reports/rt-5d...=10692&e=11115 34.7% uptime Twin Consorts
Definitely better than the old 3% crit damage gem.
Guess I should say this here as well, instead of just my little thread up top. I've been told spec modifiers should be in place as of restarts. Just a heads up.
Last edited by Proakryt; 2013-04-19 at 06:51 PM.
A vast simplification but valid comparison: 6% uptime averages out to ~2% haste rating. 25% up time averages to about 8%. I am crying.
Last edited by Proakryt; 2013-04-19 at 09:40 PM.
For this post I'll assume the 13.07% more procs from bad luck protection will translate into 1.1307x more uptime (not entirely accurate since there's a chance for overlap, but that should be minimal in this case, since the proc rate is so low). Assume an 8 minute fight, so the extra proc at the start of the fight is worth ~2.08% (10/480) uptime on its own.
In total, you'd expect to see some 9.81-10.14% uptime for the meta gem on average. No idea why Blizzard thinks the meta gem needs this low of an uptime for fire, but I'd think that should still be an upgrade over the burning meta. If it's not, we can always provide feedback to Blizzard, as I imagine those coefficients aren't set in stone.
The main reason I dont like the change comes from the already high RNG aspect of fire. If we are to expect this meta to be up ~10% of the time, i like your math, then it can easily proc during non-dps moments. You become even more reliant on good rolls to do good dps because a lowered proc rate increases the marginal value of each moment of the buff. Each second of a 10 second buff is more valuable than each second of a 30 second buff. I've seen myself lose 1.5 seconds of the buff because it proced in the middle of an evocate. Instances like this lower the realized uptime below 10%. Even if it procs as we expect the time we spend actually casting with the buff wont be the buff's full duration.
The 3% crit damage is fully realized because number of casts is more or less independent of the meta's effects (you will cast roughly the same number of spell with a burning meta as with none equipped). You do more damage per spell at all times with a burning.
Last edited by Proakryt; 2013-04-19 at 10:26 PM.
I can't imagine they'd have it be so low in worth for any given spec that you'd take the normal gem over it.
But it shouldn't. The legendary should be MILES ahead of a gem that's available to everyone from the get-go.
---------- Post added 2013-04-19 at 07:51 PM ----------
PS: I'm coming up with a log right now on the dummy.
Edit: Results below
A huge, terrible, nerf.
3 proccs in about 6-7m. This meta is next to worthless now.
Second test: http://www.worldoflogs.com/reports/o...ocr/details/0/
4 proccs in ~6m. Ffs, it doesn't help us when it doesn't line up with Combustion... I'm tempted to just use Burning now.
Last edited by Polarthief; 2013-04-20 at 02:18 AM.
Wow, it's up already? I didn't even know there was a restart.
Anyway, attempt it in a raid setting. It does scale with haste, and temporary haste at that. Heroism, raid haste, and its own proc will influence rates in a real setting.
Hell, it was crap before when it didn't line up with Combustion, now it's just even worse and useless.
---------- Post added 2013-04-19 at 10:29 PM ----------
http://www.worldoflogs.com/reports/l...yw0/details/2/ As Frost... 14 proccs in ~6m.
Yeah, this is a fucking joke. Someone please upload these on the DD forums (I would but I'm banned...) and ask them wtf is up with Frost, a specc that benefits more from Haste, is getting MASSIVE amounts of proccs compared to Fire, which doesn't scale as well (especially when it HAS to line up with Combustion to be useful).
Last edited by Polarthief; 2013-04-20 at 02:29 AM.
It's also used as a tuning function between specs. It's the same reason elemental has such a huge uptime. We need it up more to make it worthwhile since we're basically hard capping nukes now. Fire was ahead by default, it didn't need as large a benefit in relation to some of the other specs out there.
Edit: Seriously though, someone please make a thread on Official or contact a Dev. I threw the logs to GC on Twitter, but he probably won't respond to them.
Last edited by Polarthief; 2013-04-20 at 02:38 AM.
mage is still fine dps wise. its just so stupid to balance it through the legendary metagem.
The best part is when you have to seriously think about if you actually even want to use a "Legendary" meta gem over its normal counterpart when it's released. I mean... why even give it to fire mages at that point? Seems like a terrible way to balance a spec if that's what they're after. I'd much rather be toned down if needed and actually benefit and have fun with my legendary things rather than just have them be slightly better or worse than normal things if that's how it turns out. I mean really all of those quests up to this point etc and that's sort of a huge let down isn't it? Oh well I suppose we can look forward to future parts of the quest.
Last edited by Turkey One; 2013-04-20 at 02:57 AM.