Some classes still target capped destroying the class for M+

Community General Discussion
1

Example: Priory of the sacred flame dungeon damage profiles.

For the extreme example picking one of the highest and lowest damaging profiles.

Highest profile (Deathknights) (Roughly 4m overall) (Burst profile 20-30m):

One of the lowest profiles (Fury Warrior) (Roughly 3m overall) (Burst profile 10m):

I’m sorry but isn’t the target capping of certain classes a bit outdated. It really feels like it doesn’t belong on certain classes.

Either cap all classes again like in shadowlands, or uncap all of them. Please fix your game Blizzard.

10 Likes
2

I would never invite a warrior. Garbage class until blizzard fixes it. zugzuggers

2 Likes
3

I am surprised that Fury did peak 10 million, in my experience that doesn’t even happen during Bladestorm with Reap procs. The burst potential was stronger in season 1, than now in S2. And the burst potential just got worse off as S1 progressed.

Now that tirade aside, I am just salty about the burst fun being gone from the spec.

Fury does bring a stable and consistent damage profile. While a DK might peak at 15 million DPS in the pack with a Bloodbeast blowing up, they also got periods where they do 2-3million DPS. A Fury Warrior might peak at 6 million DPS, but they kinda go through the whole dungeon at a stable 3-4 million.

Now it is a question of the value of the DPS profiles.

  • If DK does more overall, but a majority of that is done to clear out trash-fodder-mobs. Is that valuable?
  • If the warrior kills the priority targets in that pack, and carry boss DPS through the run. Is that valuable?

It is a trick question. Both are valuable. Trash, all of it, got to die. Bosses got to die. Mythic+ shouldn’t be seen as this or that, but as one long boss-fight.

As such, you got to ask the question, in the team does the warrior carry its weight and DPS role, even if it does less total overall damage. As its damage and DK does not overlap on the same targets.

As long Warrior and DK is balanced to the point where you wouldn’t bring two DKs instead of a warrior. Or two warriors instead of a DK. Then balance between the damage profiles are acceptable.

Currently, Fury is in a weird place, as how it now works is so extremely tightly knit to its singletarget rotational abilities. This is a problem because on affecting the numbers there really affects the raid. The tuning knob of using CDs for Fury to address AoE has been gutted. So they kinda can only adjust either the RNG AoE damage procs or meatcleaver functionality.

Neither is very fun. But that is my opinion.

If Fury Warrior really starts to fall behind in the value it brings (prio damage), then it is a problem. Yet, Fury being behind DK on overall damage is not a problem. A DK would need the Fury Warrior (or other) to carry his slack on Single Target.

If the fact of the matter is that Fury Warrior does not carry Single Target. Then there is an issue.
https://www.warcraftlogs.com/reports/vamYJWKpbgy3kCP9?fight=2&type=damage-done&target=42&start=1410318&end=1588585

Just as an example. If Fury warrior was equal to DK on trash, this would not be balanced from the other perspective. But clearly you can see the value the Warrior bring in this comp and on this fight.

So while I dont disagree Fury could get a bump on AoE for fun factor, it isn’t exactly needed per se. As Fury is currently designed to be more about priority damage than anything. It should as such be balanced around that. The PuG and community trap of only to care about the overall is a big one. Let us just hope this pitfall doesn’t have the community stumbling and dragging Fury down with it.

5 Likes
4

I think target cap is lame in general for all classes.

Just let people enjoying going nust in aoe

3 Likes
5

------------Very true

6

Why did they add target cap in the first place anyway?

1 Like
7

rogues in bfa were broken going in to shadowlands/dragonflight blizzard started the 4/5/8 target cap.

their bleed spread in pve and pvp were annoying.

Back in classic blizzard used the chance on missing hit and expertise etc in mop that went away and they gave us capping spells.

1 Like
8

I never really understood how blizzard works.

Its reasonable to expect that when they do 1 spec rework, or tune a spec for a tier set, and if things get out of hand they drop the nerf bat. Which is what they did with Rogue.

But then, they forgot to put a post-it next to the change. Because today we ALL have some spell like the Rogue AoE. Plus we got PvP specific tuning, which we did not have in the past. So they should revert the changes, but they dont !

I have seen things like this many times. Two examples pop into my mind:

  • RShaman got Resurgence and Ancestral Awakening nerfed because in DF we had a tier set that practically gave us 100% crit chance.

So to prevent infinite mana, they nerfed those 2 things. Which makes sense. But AFTER that season they should have reverted the changes. BUT THEY DID NOT ! WHY?

  • VDH with double sygil in DF S4 was making CCing mobs trivial. So instead of nerfing the double sygil early on they waited for like… 8 months to do it. And instead changed the spell quew of mobs. Making M+ so much harder today than it used to be. All because of 1 class.

Well VDH is nerfed. It dosent have double sygil anymore. Revert the spell quew changes FFS !

9

i must say for the normal +10 keys i would value single tarhet damage more thane aoe dmg.
I am pretty sure i have never failed a dungeon because we didnt kill trash fast enough or didnt pull enough trash.
I had plenty of dungeons that failed because wipes on bossed because the boss didnt die fast enough in combination with failed mechanics.

in higher keys both, st and aoe is required of course, but thats why also only meta specs get an invite

10

True i agree

11

Well packs living for 1 minute roughly in very high keys with full uncap aoe. With full capped it’s about 2-3 minutes. It really does break a key

12

Target capped aoe is a stupid design. It is neither fun, nor helpful to achieve its goal.

If Blizzard really worries about some specs doing too much damage in aoe, it should introduce dps cap according to item level, instead of making aoe abilities with target number cap.

1 Like
13

Crashing storm 6 target, chain lightning 5 target, primo storm 6 target.

Only doom winds not target capped, yet…

14

Very true. It’s really annoying as Fully capped class (on every ability) to do any sort of damage on big pulls like in first pull of Cinderbrew etc

15

That’s cause in your eyes bosses are the fail checks for weaker groups. But i’m reality if you psy attention to youvspwnd much more time on trash then on Boss fights

16

maybe u only have played with garbage warriors haha

17

True that you spent most of time on the trash and aoe tbh

18

yes but since a dungeon has about 15 mins spare time with a decent group, wiping on a trash pack costs you 2 mins while wiping on a tyrannical boss bear the end easily can cost you 6 mins.
its not like i never wiped on trash but it rarely ever had cost me a key.
if the timer ends up being tight it is mostly because the dps is slacking.

fail checks are generally what breaks low keys not low dps or wipes on trash. thats at least my opinion

20

That is true but still its an outdated concept to leave some uncapped and have some capped

21

Their reworks are just set to fit the 1% player base not the whole playerbase the fact they are still trying after 12 years

to make stressform work… … …

The halo thing is better than the dark wing priest you just spam as much devouring as you can to make your void form 1min last.

Just saying blizzards reworks are terrible.
i’m disappointed in the class designs for season 2