Maintenance for the week of April 6:
• PC/Mac: No maintenance – April 6

Standardization needs to be all or nothing

casparian
casparian
✭✭✭✭✭
✭✭✭✭
As is well known by now, ZOS is aiming to standardize abilities in order to make balance decisions easier and more objective. To my mind, this can be fine. I'm not in principle opposed to this aim, and at any rate it's ZOS' decision.

What concerns me is that the standardization efforts seem to be piecemeal. For a very long time, classes have had unique unique weaknesses that were justified precisely by the fact that they exceeded certain standards -- it was fine for them to be rule-breakingly strong in possessing a particular strength other classes didn't have because they were rule-breakingly weak in lacking a particular tool other classes didn't have. Unfortunately, it seems that the standardization effort has removed some classes' rule-breaking strengths without addressing their rule-breaking weaknesses.

A prime example of what I'm talking about is the case of the Dragonknight, particularly magDK. MagDK has for a very long time relied on having unusually strong DOTs, as a way of compensating for the fact that they lacked certain other important tools (mobility and and execute, for example) that other classes have. ZOS has (rightly, to my mind) determined that DOTs are currently too strong, and has standardized all DOTs to approximately the same level across classes. By my calculations (someone please correct me if I'm wrong), Burning Embers will about 1k per tick weaker than the Destructive Reach DOT, for example -- throw in the free Burning status from Embers and you get in-class DOT damage that is roughly equal to out-of-class DOT damage, which comparably strong utility (healing vs. CC). Again, to my mind this is not necessarily a bad thing -- except that the class as a whole hasn't been standardized along with its DOTs. Again -- in the past, DK's stronger DOTs made sense because it lacked other tools (execute etc.). Now, it no longer has stronger DOTs but it still lacks those tools.

ZOS, I can't tell you whether standardization is or is not the direction to go for combat balance. But if you're going to pursue standardization, player morale and class balance depend on doing it consistently. It makes little sense to remove strengths which have for years existed to compensate for particular weaknesses while leaving those weaknesses intact.
7-day PVP campaign regular 2016-2019, Flawless Conqueror. MagDK/stamplar/stamwarden/mageblade. Requiem, Legend, Knights of Daggerfall. Currently retired from the wars; waiting on performance improvements.
  • NBrookus
    NBrookus
    ✭✭✭✭✭
    ✭✭✭✭
    You can't have every spec good at healing, tanking and damage without homogenization, which is now what we have with different colors. Restoring class identity after systematically destroying it over the past two years is going to take a lot more work than this patch shows.

    Bound Armaments doesn't make we want to try stamsorc -- one of the few specs I haven't tried.
    Stonefist definitely doesn't make me want to dust of stam DK
    And magwarden... Arkay bless the folks still trying magwarden.

    P.S. RIP Shor, too. It was fun for a while. If you are masochistic enough to play Kaal, I'm in a DC guild that might suit you well.
  • starkerealm
    starkerealm
    ✭✭✭✭✭
    ✭✭✭✭✭
    Didn't I just write a response to this post?
  • Olupajmibanan
    Olupajmibanan
    ✭✭✭✭✭
    ✭✭
    At least, some of the very obvious cases should be corrected. My best example of standardization fail is range of ranged CC spells. Magnum Shot range has been reduced to 22m and Flame Clench has been reduced to 15m while range of Piercing Javelin was left at 28m. Now, in Dragonhold they also changed the range of Javelin to 22m. 22m seems to be Zos's new standard for ranged CCs (Magnum Shot, Piercing Javelin, Unrelenting Grip) however Rune Cage range has been left at 28m and Flame Clench range at 15m.

    IF STANDARDIZE CONCRETE CASES (E.G. RANGED CCs), THAN EVERYTHING OR NOTHING, JUST AS OP SAID.
Sign In or Register to comment.