Thursday, December 10, 2009

TGZ #8: WoW 3.3 Damage Nerfs

This is from a Blizzard Poster:


After evaluating damage dealt in instances and PvP over the last two days, we are going to deploy three changes. There could always be more along the way. These hotfixes should hit sometime today (Dec 10).

Hunger for Blood now increases damage by 10% instead of 15%. We wanted to increase Assassination rogue damage, and we were succesful, but we overshot the mark. We buffed Hunger for Blood back when Assassination needed a damage boost, so we're more than happy that this talent won't account for such a huge dps increase. Because of the nature of hotfixes, it is unlikely the tooltip will change to 10% right away.

Scourge Strike can now crit only once. The Shadow portion of the damage cannot separately crit. We wanted to keep the double crit mechanic as a way of making Scourge Strike do more than just being an attack that hits for equal part physical and Shadow damage. The change just proved to be too bursty in PvP and provide too much sustained damage in raids. The Shadow portion Scourge Strike will continue to be increased by effects that currently boost Shadow damage.

Rolling Corruptions no longer use the initial haste value indefinitely. This is really more of a bug fix than a nerf. The problem here was that players could inflate the initial cast of Corruption and have the spell tick for that damage indefinitely as long as it was refreshed. This resulted in some "jaw dropping" damage. Technically this was a tricky one to fix but we wanted to keep the Glyph of Quick Decay and were able to ultimately find a solution. When this fix goes live, the hasted Corruption should correct itself to your current haste within a tick or two of the spell being refreshed.

Ideally, we'd rather make changes while we're still in PTR before a patch goes live, but in the end we'd rather make changes than allow something imbalanced to continue just because we didn't change it pre-patch. To the community's credit, some players predicted these issues might become a problem. We appreciate the feedback as always, even if we don't always immediately make changes suggested by the community.

I'm going to go ahead and lock this thread, but only because it covers three different topics and not because we're trying to limit any response or feedback to this announcement.


Support us!

0 comments:

Post a Comment

Twitter Delicious Facebook Digg Stumbleupon Favorites More