You’ve never needed four piece to hit 20 stacks of wind gust. I promise you, it’s not 0.75 sec. CL and LB can go lower and their associated GCD, with 20 stacks. The largely agreed upon number is 0.6 sec. Some claim to have seen 0.57 between casts, however. Either way, your 0.75 is absolutely incorrect.
I never said you couldn’t. You could hit 20 stacks regularly in 9.1. We aren’t talking about that though so why even bring it up.
We’re talking about the nerf which was related to the 4 Piece and the Machine Gun Build which used Unlimited Power and required 800 Mastery to really work.
Blizzard’s issue was those 20 stacks were going to be permanent because of that build. 0.75 seconds is the GCD cap btw broseph. I wasn’t talking cast times with that number. It was in reference to where Blizz’s issues came from. They don’t want perma casts sub the GCD limit. That’s it.
Blizzard didn’t care that you could hit 20 stacks a few times each fight.
LOL. I never said you couldn’t hit 0.6 sec cast times. You’re the one who doesn’t seem to get the difference between Cast Times and the GCD.
Cast Time is separate from the GCD. The lowest the GCD can go is 0.75 seconds. With 20 stacks you could get the cast time of Lightning Bolt lower than that and with the 4PC and Unlimited Power that became permanent.
Blizzard didn’t like the feeling of cast times going permanently LOWER than the GCD because of how it feels. Your casts may be 0.6 second but the GCD prevents you from casting again for a fraction of a second since that’s capped at 0.75 seconds.
You do realize that the head dude is a lawyer and says a lot of things that arent truth. Its his training to do so.
The council is a PR move and nothing more.
I understand the difference between GCD and Cast time.
What I’m saying is that the CAST time and the GCD of (LB and CL) both decrease to 0.6 seconds when at 20 stacks of wind gust…this allows the spell to be cast every 0.6 seconds.
Here is a quick exerpt from the top parse from KT (with the name of the caster removed)…showing casts (and subsequently the associated GCD) much quicker than 0.75 sec.
You can agree that you cannot take actions faster than the GCD right?
So if you’re casting a new spell every 0.6 seconds, the associated GCD must be lower than your claimed 0.75 sec.
I’ll state this one more time clearly…
The GCD for LB and CL were lowered to 0.6 seconds (as were their cast times) while at 20 stacks of Wind Gust.
The GCD for LB and CL absolutely (at 20 stacks of Wind Gust) was much lower than your claimed 0.75 sec.
I can’t figure out if you’re trolling or you don’t understand what you’re talking about.
The caster in the log exerpt that i just showed performs an action every 0.6 seconds.
You literally CANNOT take an action during a GCD.
The GCD of LB and CL was 0.6 seconds at 20 stacks. The information is there publicly for you to look at. I’m done explaining this to you.
The GCD cap was changed from 1 sec down to 0.75. If it was changed again I’d love to see documentation and I’ll take my lumps but here’s info from WOWpedia…
Haste reduces the [global cooldown](https://wowpedia.fandom.com/wiki/Global_cooldown) (GCD) triggered by spells and certain physical abilities exactly as it reduces the cast time of those effects, but cannot reduce it below 0.75 seconds. The length of the global cooldown can therefore be calculated using the same formula given above.
Like I said…who cares? You’re getting caught up in minutia for some odd reason. The build a lot of us liked got nerfed no matter the GCD cap.
That quote does not take into account the special effects that Wind Gust applied to the GCD of LB and CL.
And, this started by me pointing out the inaccuracy in your statement. I didn’t expect it to completely derail the way it has, especially since the proof is, and has been, publicly accessible since Wind Gust’s existence.
The difference between 0.75 and 0.6 is nearly the same percentage difference between 1 sec and 0.75 sec. It’s a pretty drastic difference.
I am simply against your spreading of misinformation.
I mean thats nice and all but what does that have to do with ele losing a large chunk off of one of their most prolific talents with a justification that has nothing to do with ele’s damage. This is a massive nerf that gives nothing back and the reason given wasn’t ele’s damage, it stands to reason that ele should get something back, especially since this nerf came out the day mythic released with 3 days notice.
People are seeing upwards of a 34% loss in M+ so far, Regardless of how it came about there are so many ways this could of been handled better without absolutely destroying a spec.
And yet no one has stepped forward now to contest it with actual evidence, combine this as tarona has said with the fact that nothing was shifted elsewhere to compensate for the absolutely insane performance loss, this was nothing more than an actual nerf but they his it behind a lie so people wouldn’t get as mad.
Except they have. Even in the thread you linked, in replies to me, people pointed out at least one person asked for the change for an accessibility reason.
Complaining that they changed something for accessibility is selfish.
As I said in the thread you linked, the change is fine for accessibility reasons, however, what is NOT fine, is the fact they didn’t buff elemental in other ways to make up for the massive amount of DPS that will be lost due to it.
“We listen to community feedback” - that doesn’t just mean you. That means everyone in the community, including those who have accessibility issues with the “machine gun” spec.
Again, asking for buffs in other areas (such as asking that the wind elemental stacks also grant a damage buff to make up for the loss of 10 stacks) is great, and I think it’s good to get the thought process rolling.
But insulting people who have accessibility issues by saying it’s a non issue is just not okay.
Also, no one, and I mean NO ONE owes you public acknowledgment that they have accessibility concerns. The only one that needs to know that info is Blizzard.