What's the logic behind Priests being the only healer without an interrupt?

The same reasoning that paladins got brez before priests did …
— Because Blizzard don’t like priests :triumph:


Honestly even though it was a trivial spell, I feel SO lost on my holy priest without circle of healing now :sob: Bring it back Blizz </3

Well, they didn’t give priests Brez, they gave everyone brez. Every single player has it now and it doesn’t require a tradeskill or anything special. Go to the AH, buy convincingly realistic jumper cables. Jobs done. If your class doesn’t have a brez spell and you aren’t carrying those in your bags, you’re doing it wrong.

1 Like

Resto druid has an interrupt. You’re confusing resto with balance.

Balance druid also has an interrupt. It just does other stuff too.

2 Likes

For example… ?

paladins are gods, we should always come first, maybe priest should get a dualcast raise or something.
:cherries:

I think you’re underestimating how powerful the shielding is, as well as passive damage while healing.

Having silence even on a 1min CD for those emergency moments would be nice, but whatever, much of the time we can run in and fear. If an interrupt is missed on a boss you’ve prolly got bigger issues going on than your healer not interrupting.

I mean that’s essentially how Blizzard feels …
If you have but any doubts, simply look to the story questline of the Legion Orderhalls for priests, lol

We’re on talent rework 4(?) of Shadow priest since Dragonflight’s release and the spec is still tied for the most two point nodes, most total nodes in a tree, and is the only dps spec in the entire game that has to give up damage points in order to take utility / defensive talents in its spec tree.

It took blizzard one look at balance druid’s tree in early DF to realise giving up solarbeam for damage was a bad design choice. It took them one look at paladin’s class tree to see making spec specific changes to the class tree was a reasonable solution to a lot of the same problems priest have with their class tree, it took them one iteration to reduce the point bloat on almost every single spec tree they’ve touched since Dragonflight.

The rules are simply different for priest. And sure tuning can mask that, or make players not care, but they are.

3 Likes

Aren’t we talking about heal priests though?

What do other specs give up in order to get such a basic ability? Oh, nothing? Yeah that is what I thought. :dracthyr_hehe_animated:

Every class should have an interrupt baseline at this point. Or remove everyone’s and massively cut back on the number of abilities that we need to interrupt. Either would be fine really.

2 Likes

I mean, what other healer can save someone from a 1shot by shielding them for their entire HP bar?

That’s an absurd amount of power for a healer to have.

Arguably, most total nodes in a tree should be better because it gives people more options, in theory.

(But generally, there’s only one right way to play, so.) Trading dps for utility is a minus though.

I can give some more examples.

Shining force was removed from holy and disc citing “there are too many knockbacks in the game” at the same time thunderstorm was added to resto and enhance shaman, and blast wave was added for frost and arcane mage, as well the dracthyr / evoker introduction. So we added knockback to 4 more specs, added a new class with 2 knockbacks, and then removed it from priest citing there were too many? This lead to enhance and resto shaman being meta in M+ with Cap totem, landslide, and thunderstorm as AoE stops in Season 1.

There is a huge blue post floating around from during dragonflight’s development in which priest feels like it’s being defined by what it is not allowed to have. Not allowed mobility, not allowed an interrupt, not allowed many of the cool things it used to have expansions ago (Spectral guise anyone?). Meanwhile every other class in the game feels fuller and like it’s breaking more rules that had previously been set for it (DK Mobility).

2 Likes

Most total nodes would be good if it wasn’t that it was caused by point bloat in two pointers and the utility at the top of the tree. MW is a great example of a high point count tree that leads to a lot of theoretically interesitng options.

As a rule of thumb, healers have more point totals than DPS, and DPS that received reworks trend downwards heavily in total points. Except for Shadow.

Thanks for your explanation.

Wanted to chime in here on MW, as a MW. All those nodes, but most of them are trash. The options that get taken in the “optimal” build are there because they are head and shoulders better than the others. The capstone talents on both monk and MW trees are awful. But at least there’s been some improvement there in the last year.

This is true, which is why I cited potential. The way the tree is structured is good, and it’s a good way to make a high point node tree work with tonnes of varied single point nodes and a lot of connections, there are just a lot of tuning issues.

You either have one or the other, you can’t have both, and even if you could have both, the points I mentioned earlier remain irrefutable.

Then trade off dominate mind and all the cheese that allows.

Or nerf the shields into the ground.

Both are very powerful strengths that are unique to priest.

No CR and no BL are not a blocker to complete meta domination, see disc and VDH since mid-DF.

Let’s not pretend that Fortitude isn’t top 2 for best raid buffs in the game for high M+ (with MOTW).