Question about Cata RE: Healing Debuffs

#0 - Feb. 11, 2010, 9:10 p.m.

Okay... so we've been talking about this for years now... but it SEEMS like we can use Cataclysm as a base-point for finally resolving this issue once and for all.

Originally, Arms was given MS because its damage was lackluster. This is a given.

Now, we're trying to get ALL dps specs to be viable top-tier dps in PvE content.

The problem that is run into is that if you let a class with an MS effect do the same damage as a class without one... you've ruined PvP for the ones WITHOUT one... because they can ONLY be valuable substitutions when there is already a dps WITH one on the team.

Case and point:

T1 comp TSG: Warrior, DK, Holy Pally... you can't replace the warrior with a Ret/Boomkin/Elemental/Enhance/Feral/etc because NO ONE would bring MS... and EVERYONE would bring the same damage (roughly).

Sooooooo... is Cataclysm going to be the point where:

1) Healing is reduced in PvP in some meaningful way (you've basically already stated THIS will happen)?
2) Can we finally remove the healing debuffs (or reduce the effect and spread them to more classes so that Ferals have more choices in teammates than Rogue/Warrior/Hunter)?

Ghostcrawler

#1 - Feb. 11, 2010, 9:44 p.m.

I agree it's an issue and we do have some plans.

However, we're going to back off of talking about Cataclysm for a little bit. We're excited about it, so we've been wanting to share our philosophy, plans and ideas as they relate to class design. However, it may be a little too soon. I think it's clear that some players are mistaking our excitement for Cataclysm as our giving up on Lich King. ("Cataclysm will fix it.") That's not our intent nor plan, but I can understand how you might draw that conclusion. We'll talk more about the upcoming expansion soon (tm).

Ghostcrawler

#37 - Feb. 11, 2010, 11:14 p.m.

Q u o t e:
Don't get excited. This does not mean they think it is a big issue or have any plans that they actually will implement into Cata. Prepare for WotLK 1.5 Cata will not fix it.

No, we do think it's a big issue. Just don't take that to mean we're definitely going to head towards a particular implementation. "Because they think it's an issue, clearly they are going to remove it or clearly they are going to give it to everyone." Too early to make those assumptions.

Q u o t e:
I hate how the bad ruin it for the rest of us.

We're not trying to slap anyone's wrist. We just want to focus on patch 3.3 for now.