"Shield spam" has become a term of ill-repute in the discipline priest community. It's spoken of either in whispers about the "bad old days" or else in the sharp, mocking tones of what not to do. Only the most degenerate discipline priests would encourage shield spam. It speaks to loose healing morals and, yes, even a bit of healing perversion. Shields are to be enjoyed in small quantities, not to gluttonous excess.
That is why I'm here to tell you to reject those stereotypes. Even good-hearted people can blast out bubbles. It's not the evil that you've all heard it is. It can--nay, should--be done. Don't listen to your neighborhood priest telling you that it's sinful.
That said, we should probably define what we mean by "shield spam" because multiple behaviors have been lumped into that one term and they are not all the same.
Let's start by examining where the term really sprang into prominence and trace our story from there. This, it turns out, may run a bit long but I promise there's a point at the end. And a pizza party. Pertinent point and pizza. And cold beer.
Come with me, then, back to those heady days of Wrath...
Spammy Shield Spam
Welcome to Dalaran! Do you have any emblems of frost to turn in? And how about those vrykul, eh?
I hope I've adequately set the mood. Back in this era of World of Warcraft, discipline priests were slowly but surely rising in the world of healing. In prior eras, discipline was really more of the PvP spec and holy was the healing spec for priests. However, the tree was revamped in Wrath and PvE discipline priests were becoming more and more populous.
Oh, sure, there was still residual persecution that they faced. They were regarded with suspicion, not being holy. Absorbs were a bit of a new mechanic to much of the playerbase and no one really paid attention to absorb values, which made discipline priests appear to be rather ineffectual, what with Power Word: Shield and Divine Aegis being completely ignored by almost all healing meters.
However, as raiders were graduating from Trial of the Crusader to the final raiding tier of the expansion, Icecrown Citadel, people were understanding the power of the absorb. High-level players had understood it long before, but it gained popular acceptance. Now, discipline priests were not just being accepted but often actively recruited as they carved out their own niche. Discipline priests weren't healers, they were shielders! You could almost think of them as a huge damage debuff on each and every boss.
This was a double-edged sword. It made discipline priests a rather necessary part of any raiding team capable of picking and choosing their raid compositions, as much so as getting a shaman in for Bloodlust or having a druid who could Rebirth. Having such a valuable niche in raid teams is obviously a nice thing...damned are the poor souls who play class-specs marginalized by current raid design.
On the other hand, it was a terribly boring playstyle, especially in 25 man raids. In 25 man raids, very literally a discipline priest's job during an encounter was to do nothing but blanket the raid in shields. And then do it again. And again. Until the boss was dead. Other healers were there to do the actual healing, after all. In 10 man raids, it was a little better, purely because there weren't enough people to shield before the Weakened Soul debuff prevented you from casting more shields. At that point, it was reasonable to cast an actual healing spell.
So discipline priests were in a bit of a bind...the niche that gave them ready access to raid spots also trapped them into a rather unenjoyable style of playing. (This wasn't purely confined to discipline priests, as I know there are restoration druids out there who have nightmare stories of being Rejuvenation bots. But I think it was most pronounced for discipline priests.)
Our Story Runs Into A Twist
Blizzard agreed that it was a trap. Their design philosophy had been slowly attempting to weed out repetitive, or One-Button, play. Discipline priests sometimes using nothing but one spell in raids didn't escape their notice. So they changed it. So mighty was their change to the discipline priest spec that they named an entire expansion for it: The Cataclysm.
Perhaps you heard about it? The change resulted in many fires around the world.
What they did was make Power Word: Shield really weak. It was brilliant. Why would you spam a spell that wasn't very strong? You wouldn't. That Blizzard, always thinking.
Well, as it happened, trying to reduce a spec's dependence upon their best and most iconic spell by making it terrible didn't do wonders for balance, that nasty issue that boils down to "Do you get to raid or not?" Discipline priests were pariahs again. Go holy or go home. The chants were hurtful.
So Blizzard did what any wise design team would do. Turn the dial the other direction as far as it would go. Suddenly, Power Word: Shield was really strong. Discipline priests were great again...in fact, they were recording by far the best parses overnight. No other class could compete.
"Hmm," said Blizzard. "That was unexpected." Also, there was this issue of discipline priests spamming their newly god-mode spell on everyone again. Also unexpected.
So now Blizzard needed a solution that did not involve turning that dial at all. Turning the dial on Power Word: Shield, you see, revealed a problem inherent in WoW balance. A spell you can use whenever you want will either be strong enough that you will use it first, last and always or else so weak that you will never use it. For if it is the strongest spell right now, it will probably be your strongest spell a moment from now. And if it is not your strongest spell right now, it probably won't be your strongest spell a moment from now.
The answer resided in the other dial that Blizzard had ignored in Wrath (which caused that previous logic about "strongest spell now->strongest spell always" to be binding in nearly every case) but used with abandon in Cataclysm...the mana cost dial. True to the Cataclysm healing model, which held that you don't simply min/max based on power of spell but min/max such that you don't go out of mana in the first minute, they increased the mana cost of Power Word: Shield greatly.
That changed the game significantly for discipline priests. The shield was still really strong, and it gave mana back every 12 seconds, so it was still useable...but "shield spam was dead for good" (I place that in quotation marks because it was probably the most common quote of the past year, it even featured on the cover of a Time magazine).
This was driven home with a peculiar sternness on forums and guides for discipline priests. Perhaps the people saying it felt it was necessary to say it with passion to break the dirty habits people had built up, but a great deal of scorn and derision was heaped upon the concept of shield spam (in my experience, at least). Not that it really required stern insistence...any discipline priest that tried to spam shields during a raid encounter, Wrath-style, would find themselves as merely a decorative prop pretty quickly, completely out of mana (OOM) and therefore unable to help much. This was a lesson as subtle as a jackhammer to the head.
And lo...it is still impossible. Unlike the latter stages of Wrath, where no spell could really run you out of mana, casting shields non-stop on a raid group, even in 10 man, will solidly OOM you.
So What's All This Talk Of Shield Spam, Then?
The problem is, "shield spam," which was originally applied to casting shields on each raid member robotically, over and over, is now being applied to any behavior involving using lots of shields.
The fact of the matter is that absorption is still the healing space of discipline priests. That is where you can add the most value while still allowing all other healers to do what they do best. While holy paladins have entered the space to some extent (to say nothing of the abominations known as blood death knights), it's still an important niche that discipline priests largely dominate. Damage prevented or mitigated is more valuable than damage taken and then healed up (the easiest way to see this is to compare the value of absorbing a 30k hit to a player with 24k health remaining, versus attempting to heal it up after).
While Divine Aegis does yeoman's work in terms of absorption, there's no faster way to get on-demand absorption out on the raid than what you might call "spamming" shields.
The key here, of course, is that you must choose when it makes sense to spam those shields. Your mana won't support doing it all the time. And the mechanics of bosses (along with a duration lowering change that I neglected to mention earlier) are such that ill-timed shield spam will come at great mana cost for no benefit as the shields mostly drop off due to expired duration without absorbing any damage at all.
So you absolutely have to pick your spots intelligently. However, if you do, there's a world of benefit to be mined from strategic shield spamming. Getting ten shields out ahead of a big raid-wide damage spike can effectively increase your raid team's "clutch heals per second (HPS)" by which I mean that if you're using GCDs during a low-stress period to put up shields that will be eaten by a high-stress period, it frees you up to cast other spells during that high-stress period. You're borrowing time from a low-stress period to lessen the difficulty of a high-stress period, in a way other healers largely can't. Absorption shields are about the only "preventative healing" (though HoTs can be used in a somewhat similar way, though less efficiently for the same purpose).
You won't be able to shield to the exclusion of all else, even if you pick your spots. There are times, especially in 10 man raiding environments, where helping your fellow healers move life bars will be necessary. However, the more you bias your casting patterns in favor of Power Word: Shield, the more you can help your raid team even out the spikiness of the overall incoming damage of the encounter. It also has the benefit of clarifying your stat choices for gemming, enchanting and reforging. If you know you will be using as much of your mana as possible (over the entire encounter) on Power Word: Shield, then you know mastery is your best bet.
This is Smart Shield Spam(tm). This is good. This is a perfectly responsible way to play discipline priest. There are other perfectly responsible ways to play a discipline priest, but don't let others lazily say "Shield spam is bad, mmmkay?" Make sure they define what they mean by shield spam...if they're talking about Wrath-style bubble botting, nod at the obviousness of their observation. Yes, you can't do something that you don't have the mana for. However, if they're advocating shielding as little as possible (some even claim you should largely only be shielding the tanks or only shielding to proc Rapture) then reject that supposed truism. Intelligently spamming shields at the right times can be an extremely powerful way to play (I would argue the most powerful way to play)...you should experiment and see how far you can stretch Power Word: Shield, especially as you push into progression fights that stretch you to your very limits.
Showing posts with label power word: shield. Show all posts
Showing posts with label power word: shield. Show all posts
Monday, January 16, 2012
Friday, August 12, 2011
Priest Shield Slam
Protection warriors have long been familiar with shield slamming. It's a key weapon in their arsenal when bugbears are trying to chew their faces off from the inside. However, it's also a key weapon in the arsenals of discipline priests who are healing tanks that have bugbears trying to chew the tank's face off from the inside.
One small difference: protection warriors target enemies with their shield slam, while discipline priests target tanks (possibly DPS, but DPS is really only there to shorten the fight so you can go watch TV).
It's really not a new technique (in fact, it might be a stretch to call it a technique) but I'm likely the first person to give it a name. And I'm without doubt the first person to apply for copyright on that name...the law offices I contacted about it confirmed that (or so I interpreted their "You want to do what? Who would be silly enough to do something like that?").
Shield Slam
Priests have a somewhat obscure ability known as Power Word: Shield. Discipline priests tend to use it quite a bit, though. In the latter stages of the previous expansion, they often tried to put it on as many targets as possible. It was the measure of first resort. Escalating mana costs (relative to mana pool) and a lowering of its duration effectively killed that strategy, but it's still something most discipline priests endeavor to cast on their target of main focus (like a tank) as often as they can (while, talented, it doesn't have a cooldown, it has an effective cooldown on a particular target due to Weakened Soul).
However, there are times when it's a better idea not to use it whenever you can on your main target. This has costs:
So when and why should you bypass these benefits? When you can expect a moment in time when any other spells (even Flash Heal) might be too slow or even impossible to cast and you can't count on other healers, you need to have Power Word: Shield in your back pocket, to slam the door on damage for a short time until you can restore stability.
Before I provide some examples, let me point out what I am definitely not saying: You should not normally treat Power Word: Shield as an emergency cooldown. Most of the time, you want to be using it as much as you can if you're tank healing. The improved throughput and mana efficiency (due to Rapture) usually make it an important ability to use as much as possible on your primary focus. Usually.
But This Is Not "Usually"
The first example I'll offer is being one of the two healers in the Alysrazor fight. I won't go through the entire encounter, as many, many...many guides exist for that. I'll briefly explain, though, the task of tank healing in phase one such that the reason to "shield slam" becomes evident.
In phase one, each of the two tanks is holding a Voracious Hatchling. Healing through the hatchling's normal melee is largely uneventful. However, they have two mechanics that can quickly make matters tricky. The first mechanic is Tantrum. The second mechanic is Gushing Wound. These two mechanics occur independently, which means they can (and often do) overlap. Or they can follow one another with no gap between them.
So you often have a case where you're letting your tank's health drop under 50% and then dealing with an enrage, essentially. The hatchlings hit rather hard and rather fast at that point, so if the tank's health is under 50%, there is the risk of losing the tank.
This is a good time to shield slam. Let the tank's health drop below 50%, causing the debuff to drop off, and then instantly drop a shield on the tank, shutting off the Tantrum damage for a precious few seconds. Your tank's buffer is not really his/her health. It's the time left before the tank dies. The sub-50% health is part of it and time provided by stopping the damage is the other part, which is why mitigation and absorption are so valuable. You're essentially increasing his/her effective health, which is crucial in a dicey situation like that.
Shutting off the damage gives you time to catch up, after artificially being forced to fall behind. There are other ways you could handle this (for example, not letting the tank drop below 50% and healing through both Gushing Wound and Tantrum until Tantrum ends) but that's less mana efficient and waiting for Gushing Wound to drop allows you to quickly throw a heal on someone else if necessary. And if the Tantrum follows directly after a Gushing Wound, even that is not an option.
Moving on to another example, let's examine how my guild does Baleroc. What I've heard is that the Shards of Torment are supposed to spawn in melee, but that's not what we were seeing. They appeared to spawn on random players, whether they were in melee or at range. Ultimately, we dealt with that by having two stack-up spots...we all--tanks excepted--started on one on those spots, when a new shard of torment had been announced and was soon to spawn, we all moved en masse to the other stack-up spot except the next DPS in rotation to soak the shard. Each subsequent shard, we repeated the maneuver, moving back and forth between stack-up spots.
We may have missed something crucial, but this is the behavior we were seeing for shard spawns, so we adapted that strategy to deal with it and it's worked for us. It did, however, have one important consequence: healer movement.
On every shard spawn, every healer was in motion. This was a problem when the tank taking the Decimation Blade strikes had just been...struck. Suddenly the tank is around 10% health and has to be pushed back up to about 100% health before the next strike arrives, and all the healers are moving.
This is an ideal time to use what I've dubbed "shield slam." You may have noticed that the tooltip for Decimation Blade said that it ignores mitigation effects. Mitigation refers to effects like "take 10% less damage." It doesn't apply to good old absorption, and Power Word: Shields will absorb Decimation Blade damage. With a large Vital Flame buff, those shields can absorb a great deal of the Decimation Blade. Therefore, dropping it on the tank just before you move, ahead of the strike, means that you (and your fellow healers) arrive at the destination with significantly less damage to heal up (which is good, since the movement also means you have less time).
Slamming The Door (On This Article)
I've gone through a couple of examples of when you want to limit using Power Word: Shield so that you can use it at crucial moments. The specific examples may not apply to you, depending on how you do those fights or whether you're doing those fights at all, but the concept is still worthwhile.
Often times, maximizing the uptime of powerful abilities is most valuable. They have cooldowns (of one type or another) for a reason: the more often you can use them, the more powerful you are and therefore Blizzard doesn't want you using them too often. However, maximizing uptime is not always ideal. Sometimes, you want to maximize the leverage of something...that is, maximize the value by using them at the specific times when they'll count the most.
To use a baseball analogy (skip down to the next paragraph if baseball, analogies or baseball analogies bore you), it's the difference between maximizing a pitcher by getting the greatest number of innings out of him or by maximizing the leverage of the innings he does pitch. Starting pitchers are an example of the first...they throw as many quality innings as they're capable of and maximize their value that way. Relief aces are an example of the second; they throw many fewer innings but they come into the situations that you know have a major bearing on who will win the game (close game, near the end) which reduces the frequency of "wasted good innings" like a shutout third inning of a 13-2 game.
Most of the time, you want to maximize uptime of Power Word: Shield. But be alert for those times when you'd rather maximize the leverage of it. Shield slam to victory, the priest way.
One small difference: protection warriors target enemies with their shield slam, while discipline priests target tanks (possibly DPS, but DPS is really only there to shorten the fight so you can go watch TV).
It's really not a new technique (in fact, it might be a stretch to call it a technique) but I'm likely the first person to give it a name. And I'm without doubt the first person to apply for copyright on that name...the law offices I contacted about it confirmed that (or so I interpreted their "You want to do what? Who would be silly enough to do something like that?").
Shield Slam
Priests have a somewhat obscure ability known as Power Word: Shield. Discipline priests tend to use it quite a bit, though. In the latter stages of the previous expansion, they often tried to put it on as many targets as possible. It was the measure of first resort. Escalating mana costs (relative to mana pool) and a lowering of its duration effectively killed that strategy, but it's still something most discipline priests endeavor to cast on their target of main focus (like a tank) as often as they can (while, talented, it doesn't have a cooldown, it has an effective cooldown on a particular target due to Weakened Soul).
However, there are times when it's a better idea not to use it whenever you can on your main target. This has costs:
- Power Word: Shield is a pretty strong throughput spell (30-40k effective HPS on a target taking continuous damage with an instant cast, and up to 60k with the glyph)
- The Weakened Soul debuff it applies boosts healing from the priest due to talent
- A further talent, Rapture, provides major mana returns when the shield is broken (subject to an internal cooldown on the talent)
So when and why should you bypass these benefits? When you can expect a moment in time when any other spells (even Flash Heal) might be too slow or even impossible to cast and you can't count on other healers, you need to have Power Word: Shield in your back pocket, to slam the door on damage for a short time until you can restore stability.
Before I provide some examples, let me point out what I am definitely not saying: You should not normally treat Power Word: Shield as an emergency cooldown. Most of the time, you want to be using it as much as you can if you're tank healing. The improved throughput and mana efficiency (due to Rapture) usually make it an important ability to use as much as possible on your primary focus. Usually.
But This Is Not "Usually"
The first example I'll offer is being one of the two healers in the Alysrazor fight. I won't go through the entire encounter, as many, many...many guides exist for that. I'll briefly explain, though, the task of tank healing in phase one such that the reason to "shield slam" becomes evident.
In phase one, each of the two tanks is holding a Voracious Hatchling. Healing through the hatchling's normal melee is largely uneventful. However, they have two mechanics that can quickly make matters tricky. The first mechanic is Tantrum. The second mechanic is Gushing Wound. These two mechanics occur independently, which means they can (and often do) overlap. Or they can follow one another with no gap between them.
So you often have a case where you're letting your tank's health drop under 50% and then dealing with an enrage, essentially. The hatchlings hit rather hard and rather fast at that point, so if the tank's health is under 50%, there is the risk of losing the tank.
This is a good time to shield slam. Let the tank's health drop below 50%, causing the debuff to drop off, and then instantly drop a shield on the tank, shutting off the Tantrum damage for a precious few seconds. Your tank's buffer is not really his/her health. It's the time left before the tank dies. The sub-50% health is part of it and time provided by stopping the damage is the other part, which is why mitigation and absorption are so valuable. You're essentially increasing his/her effective health, which is crucial in a dicey situation like that.
Shutting off the damage gives you time to catch up, after artificially being forced to fall behind. There are other ways you could handle this (for example, not letting the tank drop below 50% and healing through both Gushing Wound and Tantrum until Tantrum ends) but that's less mana efficient and waiting for Gushing Wound to drop allows you to quickly throw a heal on someone else if necessary. And if the Tantrum follows directly after a Gushing Wound, even that is not an option.
Moving on to another example, let's examine how my guild does Baleroc. What I've heard is that the Shards of Torment are supposed to spawn in melee, but that's not what we were seeing. They appeared to spawn on random players, whether they were in melee or at range. Ultimately, we dealt with that by having two stack-up spots...we all--tanks excepted--started on one on those spots, when a new shard of torment had been announced and was soon to spawn, we all moved en masse to the other stack-up spot except the next DPS in rotation to soak the shard. Each subsequent shard, we repeated the maneuver, moving back and forth between stack-up spots.
We may have missed something crucial, but this is the behavior we were seeing for shard spawns, so we adapted that strategy to deal with it and it's worked for us. It did, however, have one important consequence: healer movement.
On every shard spawn, every healer was in motion. This was a problem when the tank taking the Decimation Blade strikes had just been...struck. Suddenly the tank is around 10% health and has to be pushed back up to about 100% health before the next strike arrives, and all the healers are moving.
This is an ideal time to use what I've dubbed "shield slam." You may have noticed that the tooltip for Decimation Blade said that it ignores mitigation effects. Mitigation refers to effects like "take 10% less damage." It doesn't apply to good old absorption, and Power Word: Shields will absorb Decimation Blade damage. With a large Vital Flame buff, those shields can absorb a great deal of the Decimation Blade. Therefore, dropping it on the tank just before you move, ahead of the strike, means that you (and your fellow healers) arrive at the destination with significantly less damage to heal up (which is good, since the movement also means you have less time).
Slamming The Door (On This Article)
I've gone through a couple of examples of when you want to limit using Power Word: Shield so that you can use it at crucial moments. The specific examples may not apply to you, depending on how you do those fights or whether you're doing those fights at all, but the concept is still worthwhile.
Often times, maximizing the uptime of powerful abilities is most valuable. They have cooldowns (of one type or another) for a reason: the more often you can use them, the more powerful you are and therefore Blizzard doesn't want you using them too often. However, maximizing uptime is not always ideal. Sometimes, you want to maximize the leverage of something...that is, maximize the value by using them at the specific times when they'll count the most.
To use a baseball analogy (skip down to the next paragraph if baseball, analogies or baseball analogies bore you), it's the difference between maximizing a pitcher by getting the greatest number of innings out of him or by maximizing the leverage of the innings he does pitch. Starting pitchers are an example of the first...they throw as many quality innings as they're capable of and maximize their value that way. Relief aces are an example of the second; they throw many fewer innings but they come into the situations that you know have a major bearing on who will win the game (close game, near the end) which reduces the frequency of "wasted good innings" like a shutout third inning of a 13-2 game.
Most of the time, you want to maximize uptime of Power Word: Shield. But be alert for those times when you'd rather maximize the leverage of it. Shield slam to victory, the priest way.
Subscribe to:
Posts (Atom)