As many of you know, there's been another Hunters vs Blizzard fight going on recently over a bug surfacing in the 1.5.0 patch. Certain skills had timers affected by their weapon speed when they shouldn't have.
The Hunters screamed and clawed, claiming DPS nerfs as if the Fires of Hell had come down on them. Then Blizzard released that the bug was not intended to be fixed when 1.5.0 went live. Oops. Hell hath no fury like the Hunters scorned, apparantly.
In the midst of the flames, Blizzard then released this information: it had always been bugged this way. The difference between now and the test patch was that the Client side used to show the "right" cooldown, but the Server side enforced the wrong, longer one. The test patch had the "wrong" - but accurate - cooldown displayed. So all the Hunters giving numbers about how they suffered sounded like they were lying.
Of course, now Blizzard says it'll try to fix the cooldown bug completely before 1.5.0 goes life (but, hey, Rogues getting hurt by their own skill - Ghostly Strike - isn't important). Why does any of this matter to me? Because it gives the backstory to a revelation Blizzard posted here.
People have claimed 1.0 second global cooldowns. Others have claimed 1.5 second global cooldowns. I had tried timing it in my head before, and came closer to 1.0 but somewhat off. What's the discrepency? There is a 500 ms grace period given in cooldown calculations server side, to allow for latency problems. So if you hit the button at, say, 1.1 seconds, the server would still allow even though you're 0.4 seconds early. The reason some Hunters experienced reduced DPS in the test patch was that they were no longer using up thier grace period.
Just some interesting information, and it shows that neither relying on a 1.0 cooldown nor a 1.5 is completely accurate, as you are fluctuating between them to account for latency.
The Hunters screamed and clawed, claiming DPS nerfs as if the Fires of Hell had come down on them. Then Blizzard released that the bug was not intended to be fixed when 1.5.0 went live. Oops. Hell hath no fury like the Hunters scorned, apparantly.
In the midst of the flames, Blizzard then released this information: it had always been bugged this way. The difference between now and the test patch was that the Client side used to show the "right" cooldown, but the Server side enforced the wrong, longer one. The test patch had the "wrong" - but accurate - cooldown displayed. So all the Hunters giving numbers about how they suffered sounded like they were lying.
Of course, now Blizzard says it'll try to fix the cooldown bug completely before 1.5.0 goes life (but, hey, Rogues getting hurt by their own skill - Ghostly Strike - isn't important). Why does any of this matter to me? Because it gives the backstory to a revelation Blizzard posted here.
People have claimed 1.0 second global cooldowns. Others have claimed 1.5 second global cooldowns. I had tried timing it in my head before, and came closer to 1.0 but somewhat off. What's the discrepency? There is a 500 ms grace period given in cooldown calculations server side, to allow for latency problems. So if you hit the button at, say, 1.1 seconds, the server would still allow even though you're 0.4 seconds early. The reason some Hunters experienced reduced DPS in the test patch was that they were no longer using up thier grace period.
Just some interesting information, and it shows that neither relying on a 1.0 cooldown nor a 1.5 is completely accurate, as you are fluctuating between them to account for latency.
Trade yourself in for the perfect one. No one needs to know that you feel you've been ruined!