Don't remove rolling corruptions

#0 - Dec. 11, 2009, 4:04 a.m.
Blizzard Post
This is probably pointless because it seems to have been decided to "fix" corruption/swp keeping the original haste/crit/sp values from when it was applied, however I'd much rather it stay. the damage from eradicated corruptions is high, naturally, but it's something extra you have to do as the player to get more damage out, and a good way for affliction to set up kills. how well you keep your hasted corruptions up is just another skill gap that i don't think should be removed.

only had a couple days playing since the patch ofc, but from what i've seen the damage from rolling corruptions isn't too high in pve or pvp, and if it was i'd rather see a coefficient nerf than dumbing it down and having the game adjust your damage without you having to think.


on a related note, tongues/slow/mn increases haste-enabled dot durations, if anything should be on the quick fix list it's that imo
#23 - Dec. 11, 2009, 6:31 a.m.
Blizzard Post
Q u o t e:
yea see we're opposites, you don't like it because it's "gamey" aka you have to think and it's hard to maximize it's effect, and you'd rather just have things easier and then get buffed without you having to actually get better. i'd rather get more damage by doing more things well.

also what exactly is counterintuitive about having a dot keep the values it had when it was casted? that doesn't really seem any less logical than having it update and change mid-duration..


If it had been a matter of skilled warlocks able to focus all of their haste cooldowns at once for a small or medium dps increase, then yeah, maybe that would have been cool. The problem was it was a very serious increase, especially in a world with Bloodlust. The damage was just out of line. We considered somehow nerfing the benefit haste gave, but that would defeat the whole point of the glyph in the first place. Other options would have been to nerf Everlasting Affliction or change the haste glyph to affect Unstable Affliction instead. Both of those seemed like bad choices compared to just letting the refresh not keep rewarding you for the initial burst of haste.

I agree with the person who said the direction was to make haste a more attractive stat, not to develop a new play style about blowing a ton of haste cooldowns at once and then [trivially] refreshing the dot forever.
#50 - Dec. 11, 2009, 7:32 a.m.
Blizzard Post
Q u o t e:
Have Warlocks using it been doing excessive damage though? From what i've seen even in the fights where it has been used it mainly serves just to bump us up to the same level of DKs and Rogues. I'm not saying that the dps gap is significant, but that the dps gap was needed.


Who you may have noticed also got nerfed today. Yes, rolling locks have been doing excessive damage. Not all of them, mind you.
#53 - Dec. 11, 2009, 7:39 a.m.
Blizzard Post
Q u o t e:
The only question i have is how exactly do we get ourselves heard during the ptr testing? Im asking because this scaling issue was brought up several times on the ptr forums and was ignored, this is not the first time we've presented an issue with an ability during the ptr, and been told it was fine, only to have it nerfed shortly after the patch goes live.


I'm going to answer this once, because it's all over the forums, and it's all over the forums every time we do a patch.

Players say a lot of things on the PTR. We have a smart community. They are right a lot of the time. They are wrong sometimes too. It's easy for players to focus on the things they said, or that the thought leaders in their community said, and forget about all the ridiculous and occasionally insane things that get said on the forums all the time. This is where you say: but you should listen to us, not to those guys. See the problem?

We read the concerns and discussed them and decided which concerns were probably not an issue, which things we needed to keep an eye on ,and which things we needed to change right away. We have a pretty good track record overall, but sometimes we get things wrong. The right thing to do in those situations is to fix them, not try and be stubborn and save face.

We were wrong about Corruption. However, that doesn't mean we are now or ever going to follow a design model where if the community suggests something that we immediately go and implement that change. We don't think we'd end up with a very good game that way. I promise we'll listen to you though. There's a perhaps subtle but important distinction there.