Blood Death Knight Tank Rotation For M+ (shadowlands)

Core Ability Priority Overview

Normal Priorities

  1. [Death Strike] if you are below 70%* health.
  2. [Abomination Limb]
  3. [Marrowrend] if [Bone Shield] is not active or has a duration less than 5 seconds or if you have less than 3 stacks of [Bone Shield].
  4. [Blood Boil] if a target does not have [Blood Plague] or it is about to expire.
  5. [Death Strike] when (RP is above 105 or above 85 when [Dancing Rune Weapon] is active) and (priority damage is desired or your [Coagulopathy] buff does not have greater than 3 seconds of remaining duration while at 5 stacks)).
  6. [Soul Reaper] on (1 target or if priority damage is desired) when a limiting target is below 35% health.
  7. [Marrowrend] if below 8 stacks of [Bone Shield] (below 6 stacks when [Dancing Rune Weapon] (with [Insatiable Blade]) has less than 60 seconds on its cooldown) and [Abomination Limb]) is not active.
  8. [Tombstone] with more than 6 stacks of [Bone Shield] and when [Death and Decay] is active and when [Dancing Rune Weapon] has more than 15 seconds on its cooldown.
  9. [Death and Decay] if [Death and Decay] is not already active.
  10. [Heart Strike] with, or when 1.5 second away from, having more than 3 Runes.
  11. [Blood Boil] with 2 charges and less than 5 stacks of [Hemostasis].
  12. [Heart Strike] with 3 runes or (with 6+ stacks of [Bone Shield] and 4.5+ seconds left of [Bone Shield] duration).
  13. [Blood Boil] with less than 5 stacks of [Hemostasis] or with 2 charges of [Blood Boil].
  14. [Death Strike] when (RP is above 105 or above 85 when [Dancing Rune Weapon] is active).
  15. [Death’s Caress] with less than 9 stacks of [Bone Shield].

Non-Global Cooldown Abilities

  1. [Empower Rune Weapon] when you have less than 3 runes and less than 121 RP.
  2. [Blood Tap] if you have 2 charges, or are less than 5 seconds away from 2 charges of [Blood Tap], and you have less than 3 Runes.
  3. [Blood Tap] if you have less than 3 Runes and less than 55 RP.
  4. Use [Raise Dead].

Core Ability Priority Details

[1] [Death Strike] if you are below 70%* health.

Basis: [Death Strike] is our primary mitigation ability and using it effectively is the key to staying alive; this priority is meant to use [Death Strike] when it’s efficient. Using [Death Strike] under the right circumstances is our top priority, since you will either die or require an excessive amount of healing from your healer if you only passively use [Death Strike].

So, under what circumstances do we want to use [Death Strike]?

[Death Strike] healing is proportional to the damage we’ve taken in the last 5 seconds, though any overhealing will be lost (with the exception of the resulting [Blood Shield]). For a simple and effective method, it is recommended to use a fixed health %, alone, as a trigger for when to use [Death Strike] specifically for healing, since situations where you drop below any given health % are almost always going to be when you have been taking significant amounts of damage in the last 5 seconds.

What health exact % should be used as a setpoint?

There are a few things we need to take into consideration: 

  1. If the threshold is too low, it becomes more likely that we’ll overshoot our threshold and die before we can reactively use [Death Strike].
  2. If the threshold is too low, too many of our [Death Strike]‘s may be used inefficiently to avoid capping RP, for minimal healing, when they could have been used more efficiently during a damage spike that didn’t push us below our overly-low threshold.
  3. If the threshold is too high, [Death Strike] might be wasted during low damage periods that still manage to push us below our overly-high threshold, when they could have been used more efficiently on higher damage periods.
  4. If the threshold is too high, our RP levels will be chronically low, since we’re using [Death Strike] too aggressively. This means we won’t have as much RP (our second health bar) saved up for when situations become dangerous.

As such, we want to get as close to that theoretical sweet spot as possible to maximize our overall [Death Strike] healing, which also has us pooling sufficient RP for truly dangerous situations and keeps our health pool high enough that we’re unlikely to instantaneously die before we have the chance to use [Death Strike].

In reality, the ideal threshold may change from situation to situation, but, for the purposes of this guide, a trigger point of 70% health is recommended and has been found to be effective in all content up to and including cutting edge BDK M+ key levels. Feel free to adjust this value as you see fit.

[2] [Abomination Limb]

Basis: [Bone Shield] provides a significant amount of armor and a respectable amount of haste. Generally, this buff reduces physical damage intake by over 20%, which is a large increase to our mitigation and EHP.

[Abomination Limb] provides up to 9 [Bone Shield] charges, though, because we generally don’t want to spend time below 5 charges and outside of [Ossuary] range, getting all of these charges is not always possible. Later priorities will adjust [Bone Shield] charges to maximize this gain within reason while [Abomination Limb] is coming off of cooldown, but it is currently not worth delaying [Abomination Limb] for the sole purpose of increasing its [Bone Shield] generation. In any case, even using a low estimate of 6 [Bone Shield] charges generated per cast, those charges will result in a minimum of 20 additional RP through 4 additional casts of [Heart Strike] over 2 casts of [Marrowrend].

Why is this not ranked higher? Recovering from a low health % is going to do more for your immediate survivability than an armor buff or threat generation.

[3] [Marrowrend] if [Bone Shield] is not active or has a duration less than 5 seconds or if you have less than 3 stacks of [Bone Shield].

Basis: [Bone Shield] provides a significant amount of armor and a respectable amount of haste. Generally, this buff reduces physical damage intake by over 20%, which is a large increase to our mitigation and EHP.

Ideally, if [Marrowrend] is going to be used specifically to refresh the duration of [Bone Shield], you want to try and prevent a situation where the 20 generated RP is wasted due to having too much RP (in priority damage situations). It is suggested to track when [Bone Shield] is within 5 seconds of expiring (or with 2 or less stacks) so you have some time to efficiently sequence abilities without the immediate need of having to use [Marrowrend] on your next global and potentially overcap RP.

Why is this not ranked higher? Recovering from a low health % is going to do more for your immediate survivability than an armor buff and [Abomination Limb] provides a more efficient way of generating initial [Bone Shield] stacks.

[4] [Blood Boil] if a target does not have [Blood Plague] or it is about to expire.

Basis: The main basis for this priority is that [Blood Boil] is how we establish threat on multiple targets. If we waited 2-4 globals before using some AoE threat generation, then your targets might decide to kill a dps/healer in the meantime. In fact, if initial AoE threat continues to be an issue, using two casts of [Blood Boil] near the start of a pull may be a consideration, but this situation isn’t common enough to account for it in the core priority list. In any case, even if this priority is suboptimal in one or two target situations, there is very little being lost using this same priority in all situations, since you will generally only be using this ability at this priority once per encounter and it only slows you down from putting Runes on cooldown by one global cooldown.

[Blood Plague] provides low enough damage and healing that it is NOT justifying why we are going out of our way to apply it; we’ll be casting [Blood Boil] often enough, anyway, that using [Blood Plague] at this priority is only giving us an extra few seconds of [Blood Plague] uptime, which is only healing us for a very small fraction of our overall health, per target, over that duration. However, the 5% damage increase from [Coagulopathy] due to [Blood Plague] is a nice perk, in any case.

The primary defensive benefit to using [Blood Boil] is actually to generate [Hemostasis] stacks, if that talent has been selected. Let’s assume that, at most, 15% of our [Death Strike] healing overheals (not including [Blood Shield]) and that our Mastery is, at max, 28% (remember, [Blood Shield] is not affected by [Hemostasis] stacks); real overhealing values rarely get lower than 15% and 28% Mastery is a relatively low value. With these assumptions, each stack of [Hemostasis] increases the effectiveness of our next [Death Strike] by ~6% per stack gained. If we further assume that it will take 35 RP to use [Death Strike], then we can say that a cast of [Blood Boil] is equivalent to 2.1 RP per stack of [Hemostasis] gained; a value that gets worse if our assumed values of over-healing and Mastery get higher. These numbers *also* aren’t being used to justify this priority, though they may be referenced in other priorities.

Why is this not ranked higher? We want to ensure that [Bone Shield] is active to reduce damage from incoming hits and to provide additional Haste before worrying about establishing AoE threat and applying [Blood Plague].

[5] [Death Strike] when (RP is above 105 or above 85 when [Dancing Rune Weapon] is active) and (priority damage is desired or your [Coagulopathy] buff does not have greater than 3 seconds of remaining duration while at 5 stacks)).

Basis: While we want to maintain reserve RP (so we can use [Death Strike] in situations where it is needed), if our RP levels get too high, then we won’t be getting full benefit out of our RP generating abilities. And so, this priority tries to responsibly gain the mitigation and damage benefits of otherwise lost [Death Strike] casts, while still maintaining a reasonably strong RP pool. 

However, players have the option to overcap and waste RP to increase [Blood Boil] throughput in non-challenging AoE encounters for more overall AoE damage in AoE situations where there is not a priority target. That being said, this is only a potential damage gain if you are not sabotaging your [Coagulopathy] ramp speed or uptime as a result. So, you want to make sure you are at max stacks and with sufficient duration before you consider skipping this priority for more overall AoE damage. While this strategy obviously reduces [Death Strike] throughput and could cause loss of damage specifically when using the [Bloodshot] talent due to a loss of [Blood Shield] uptime, this should usually be acceptable since you will have a full RP pool to fall back on and [Bloodshot] is not a general-use talent in M+.

What RP threshold should we use to decide when we use [Death Strike] to avoid capping excessive amounts of RP?

In general, the higher the RP threshold on this priority, the more RP we will have pooled to use when we start taking significant amounts of incoming damage. However, once this threshold gets above 95, we begin making a tradeoff between a larger average RP pool (which can increase our overall survivability) and some level of lost RP. In 9.2, the tier set bonuses greatly increase the potential to generate large amounts of RP in a single global cooldown, but we are generally only concerned about excess RP waste on single targets in 9.2 due to excessive resource generation. In such a situation, the highest amount of RP that can be generated is 15 RP (25 RP during [Dancing Rune Weapon]) when using [Tombstone], with some chance of a tier set proc to generate an additional 15 RP (25 RP during [Dancing Rune Weapon]). The use of the (Night Fae) legendary increases RP generation potential by 20%, but it also increases resource bloat in a way that allows for similar thresholds to be used regardless of covenant.

This guide recommends using [Death Strike] whenever we are above 105 RP (or 85 RP with [Dancing Rune Weapon] active), where the only way RP is wasted in some capacity is when bonus RP generating effects occur with unfortunate timings. This small loss in RP efficiency is thought to be worth the tradeoff for the extra RP pooling it provides. But, feel free to adjust these numbers as you please.

Why is this not ranked higher? If anything, the global spent on [Blood Boil] buys you some time to potentially take more damage and make this non-essential [Death Strike] more valuable, which can improve your RP efficiency. Even if it doesn’t result in a stronger [Death Strike], [Blood Boil] generates no RP, so it isn’t causing you to overcap RP. In any case, establishing threat takes priority over a non-essential [Death Strike] (at least when it comes to [Blood Boil]).

[6] [Soul Reaper] on (1 target or if priority damage is desired) when a limiting target is below 35% health.

Basis: If the player has chosen to talent [Soul Reaper], it is assumed they are interested in the priority damage increase despite the mitigation costs associated with using this ability (within reason). As such, this priority placement results in the highest [Soul Reaper] damage throughput without overly adverse consequences in other areas. This ability provides single target damage and is generally displacing casts of [Heart Strike] (which has some target scaling) and, to some extent, [Death Strike] (which helps with [Coagulopathy] consistency). As such, when more than 1 priority target is present, this ability is generally not worth using

Because of the low cooldown on [Soul Reaper], it is especially important that the player is using it whenever it is available assuming a higher priority does not exist. As such, it is suggested to use heightened tracking of its cooldown to make sure you are maximizing its utilization.

The effect that is triggered if an enemy dies before the execute damage is dealt is not seen as particularly desirable at this time due to the current state of our resources.

Why is this not ranked higher? The immediate priorities above this point are either needed to support important proactive benefits or abilities that are more immediately impactful than [Soul Reaper].

[7] [Marrowrend] if below 8 stacks of [Bone Shield] (below 6 stacks when [Dancing Rune Weapon] (with [Insatiable Blade]) has less than 60 seconds on its cooldown) and [Abomination Limb]) is not active.

Basis: With a high [Bone Shield] stack count, you will never be in any immediate need to [Marrowrend] to maintain 5+ stacks for the 5 RP cost reduction on [Death Strike] with [Ossuary]. However, it’s important that [Bone Shield] stacks aren’t wasted when you [Marrowrend], which would occur when we have more than 7 stacks. High [Bone Shield] stacks also give you more flexibility to use your runes without losing [Ossuary] and it maximizes the benefits of [Foul Bulwark], so keeping stacks high is the default recommendation. Granted, if [Abomination Limb] is active, we may as well let it finish generating [Bone Shield] stacks before we worry about generating more.

With [Insatiable Blade], it is recommended to swap to a lower [Bone Shield] band when [Dancing Rune Weapon] is coming off of cooldown in the near future, so we can maximize the bone shield generation of these abilities while avoiding a significant loss of [Ossuary] uptime, which improves resource efficiency at the cost of marginally lower [Foul Bulwark] benefits. Ideally, we want our [Bone Shield] stacks as low as they can possibly be when the corresponding abilities are coming off of cooldown *without* losing any [Ossuary] uptime in the process. This same logic is applied to [Abomination Limb].

With current tuning, [Everlasting Bond] does not change the math enough to consider ignoring [Ossuary] during our [Dancing Rune Weapon] windows, which had previously been justified with the patch 9.2 tier set bonus.

Why is this not ranked higher? There is no immediate urgency to top off [Bone Shield] stacks, especially so if we are normally maintaining higher levels of bone shield. While this priority does enable the 5 RP cost reduction on [Death Strike] in some situations, that RP efficiency isn’t going to make up for the fact that we’re overcapping on RP generated by this [Marrowrend] if we’re above 105 RP in single target situations. An argument could be made to make a [Marrowrend] priority higher on this list for when 4 or less RP would be lost to overcapping and where the [Marrowrend] would enable the 5 RP reduction to become active, but there aren’t a lot of gains to be had for the added rotation complexity. We should almost never have such high levels of RP in combination with such low stacks of [Bone Shield].

If [Soul Reaper] is being used, [Bone Shield] management is not adversely impacted by giving [Soul Reaper] a higher priority, especially given the low rates of [Bone Shield] consumption on single targets.

[8] [Tombstone] with more than 6 stacks of [Bone Shield] and when [Death and Decay] is active and when [Dancing Rune Weapon] has more than 15 seconds on its cooldown.

Basis: Our main three considerations with [Tombstone] usage is, first, making sure we do not lose [Bone Shield] while doing it, second, we would like to be standing in [Death and Decay] to triple the effectiveness of [Shattering Bone], and, third, we would like to gain a reasonable amount of effective [Dancing Rune Weapon] cooldown reduction.

The main things even making [Tombstone] a core rotational ability, at all, is its synergy with [Insatiable Blade] to reduce the cooldown of [Dancing Rune Weapon] and [Shattering Bone] to generate increased AoE damage, which is why both of these synergies add additional conditions for the usage for this ability. 

Still, the initial absorb can sometimes be useful as a situational defensive cooldown against certain mechanics and, in these situations, you can consider using this cooldown defensively instead of as a core rotational ability.

Why is this not ranked higher? All of the perks associated with [Tombstone] usage are not more important than maintaining proactive mitigation, especially since bone shield charges are needed to use this ability in the first place without significant downsides.

[9] [Death and Decay] if [Death and Decay] is not already active.

Basis:

With [Crimson Scourge] active, [Death and Decay] costs nothing and generates no RP on cast. This tradeoff is sometimes preferable since the saved rune can now be used on [Heart Strike] to generate even more RP, though using [Death and Decay] in this way results in less total [Death and Decay] casts. However, in the current patch, it is not worth waiting for [Crimson Scourge], since any bonus [Heart Strike] is displacing a [Blood Boil] and [Death and Decay] has enhanced value from the [Unholy Ground], [Sanguine Ground], and [Shattering Bone] talents. This usage technically results in marginal losses to our mitigation and, indirectly, our EHP, but the damage gains are significant in comparison.

With the [Death’s Echo] talent, we want to avoid a situation where we use [Death and Decay] while one is already active, since their effects do not stack.

Why is this not ranked higher? [Tombstone] is currently only used under the condition that [Death and Decay] is already active, so these priorities do not compete with each other. Furthermore, [Bone Shield] maintenance takes priority before runes are potentially spent on other abilities in order to maintain the associated benefits.

[10] [Heart Strike] with, or when 1.5 second away from, having more than 3 runes.

Basis: We can regenerate up to 3 runes at any given time, so we are missing out on rune regeneration if we have more than 3 Runes. This priority is making sure we are using all of our rune regeneration and, with [Bone Shield] topped off, [Heart Strike] is going to generate the most RP per rune.

Why is this not ranked higher? [Death and Decay] is prioritized since its combined perks (with talents) are superior in all situations to what is gained with [Heart Strike], assuming the player is able to stay in their [Death and Decay]. Beyond that, it is generally better to efficiently top off [Bone Shield] stacks than to frontload RP generation, unless you are in immediate danger of dying and desperately need to build RP to [Death Strike]. It can be argued that a higher priority of [Heart Strike] should be added to capture this situation, but this is not included because “panic” [Heart Strike]‘s are a very short-term band-aid that will quickly cause more problems than they solve with the loss of RP efficiency from dropping below 5 stacks of [Bone Shield].

[11] [Blood Boil] with 2 [Blood Boil] charges and less than 5 stacks of [Hemostasis].

Basis: With 2 charges of [Blood Boil], we are missing out on potential [Blood Boil] casts (and potential [Hemostasis] stack generation) by not using this ability. As long as we are not already capped on [Hemostasis] stacks, we want to generate more to increase the effectiveness of our next [Death Strike]. And, even without [Hemostasis] talented, we are not flooded with other resources to the extent where it is worth further neglecting the long-term throughput of our [Blood Boil] casts, even if they are only providing increased damage.

[Hemostasis] is the primary defensive benefit of using [Blood Boil] and, beyond that, the only other benefit is the uncapped AoE damage of the [Blood Boil] cast itself, since [Blood Plague] application is already assumed due to the previous [Blood Boil] priority. [Hemostasis] discussion can be seen in the previous [Blood Boil] priority, as well.

Why is this not ranked higher? Rune usage through [Heart Strike] is generally preferable to [Blood Boil] in all situations where [Blood Plague] is already active due to mitigation benefits. Situations where loss of [Blood Boil] charges actually has an effect on overall [Blood Boil] throughput are also rare given current resource conditions.

[12] [Heart Strike] with 3 runes or (with 6+ stacks of [Bone Shield] and 4.5+ seconds left of [Bone Shield] duration).

Basis: We want to lower our active rune count as much as possible to create some margin for our rune regeneration as our runes come off of cooldown. But, we usually want to preserve 2 runes so we can [Marrowrend], when needed.

In general, we can only go below 2 runes (without missing a crucial [Marrowrend]) If our [Bone Shield] is at sufficient stacks and has sufficient remaining duration.

Why the [Bone Shield] thresholds?

For duration, the longest amount of time you would be unable to use [Marrowrend] if you just spent your runes on [Heart Strike] is ~4 seconds in a worst-case scenario, so the duration of [Bone Shield] needs to be sufficient to cover this window beyond the buff duration. This number is being increased to 4.5 to account for player reaction time and some amount of player haste.

For the number of stacks, the largest amount of stacks we can lose in 4.5 seconds is 4 stacks of [Bone Shield]. So, we have little to no risk of falling below 5 stacks of [Bone Shield] if we have 6 or more stacks before using our reserve runes.

Why is this not ranked higher? At this point, we are not in immediate danger of losing out on long-term Rune generation, since 3 runes are already on cooldown.

[13] [Blood Boil] with less than 5 stacks of [Hemostasis] or with 2 charges of [Blood Boil].

Basis: This will reduce the likelihood that we’ll miss out on [Blood Boil] casts (and long-term [Hemostasis] stack generation when talented). There is no particular reason to save 1 charge.

Against multiple targets, we risk underutilizing [Blood Boil] against multiple targets if we are attempting to maximize [Hemostasis] value too much when the situation is not sufficiently dangerous. So it is better to use [Blood Boil] at this priority with no additional restrictions if we are sitting on 2 charges.

Why is this not ranked higher? Runes are more valuable than [Blood Boil] charges based on previous discussion, so preventing lost rune regeneration time takes priority.

[14] [Death Strike] when (RP is above 105 or above 85 when [Dancing Rune Weapon] is active).

Basis: Given that we are not in a priority damage situation and our [Coagulopathy] stacks are being properly maintained, it is still worth using [Death Strike] at this lower priority to reduce RP waste, since, at this placement, our other resources are already being fully utilized.

[15] [Death’s Caress] with less than 9 stacks of [Bone Shield].

Basis: [Death’s Caress] is a very resource efficient ability, but its weakness is that it does not accomplish enough during a single GCD to make it worth casting over another ability. So, even though it generates 2 [Bone Shield] stacks per rune compared to 1.5 [Bone Shield] stacks per rune with [Marrowrend], the fact that it only generates 2 [Bone Shield] stacks per GCD instead of 3 [Bone Shield] stacks per GCD (in addition to lower marginal damage) is ultimately what limits its usage. That being said, if conditions are such that we don’t wish to use any of our other abilities, and we are making productive use of the generated [Bone Shield] charges, it is a gain to use [Death’s Caress]. This will still occur at some frequency in melee range, but you should be especially conscious about the potential to use [Death’s Caress] when you are outside of melee range.

Why is this not ranked higher? More frequent usage of [Death’s Caress] will lower the amount of long-term casts we are able to perform for [Blood Boil]. There is no demonstrated upside to using [Death’s Caress] more often in melee range and potential downsides when we consider real-world conditions.

Non-Global Cooldown Abilities

[1] [Empower Rune Weapon] when you have less than 3 runes and less than 121 RP.

Basis: [Empower Rune Weapon] is a strong source of resource regeneration and a strong haste buff effect. While we generally wish to maximize the value of this ability by using it as soon as possible, much of its value is lost if your rune levels are too high when it is used. Additionally, small gains were noted if you do not waste the initial 5 RP generation.

At this time, it does not appear worthwhile to make a particular effort to sync [Empower Rune Weapon] with [Dancing Rune Weapon]. The potential damage gains were extremely small, while it would also have the negative effect of increasing overlap of cooldowns with defensive benefits.

[2] [Blood Tap] if you have 2 charges, or are less than 5 seconds away from 2 charges of [Blood Tap], and you have less than 3 runes.

Basis: If we are under these conditions, long term rune regeneration is, or is about to be, lost by not using [Blood Tap].

[3] [Blood Tap] if you have less than 3 runes and less than 55 RP.

Basis: [Blood Tap] gives us the ability to pool an additional rune without losing long-term rune regeneration. So, the question is, under what circumstances do we want to use this additional rune?

  1. The lower this limit is, the higher likelihood it is that it will be used in a situation where it is needed.
  2. If the limit is too low, the time needed to convert the rune into RP and into a [Death Strike] may be too long to avoid a player death.

So, how low is too low? For the purposes of this guide, that is when the extra rune is not enough to enable an extra [Death Strike] on its own. Given that the minimum RP generated from a [Heart Strike] is 15 RP with [Heartbreaker], we don’t want to be below 20 RP while we are still holding onto a charge of [Blood Tap]. We get into this situation by using [Death Strike] when we are below 55 RP, so being below that is our trigger for using our last charge of [Blood Tap].

[4] Use [Raise Dead].

Basis: [Raise Dead] is a minor 1 minute duration single target damage cooldown. Either use it on cooldown or attempt to strategically use it when single target damage is more valuable, but, like all damage cooldowns, sitting on the cooldown can quickly become a net loss in most situations.

Potential Deviations from the Core Priorities

Does anything change in the opener?

In most ways not a whole lot changes during the opener, but, if you are beginning a pull with full or near-full runes available, one of two actions can become efficient to do if you specifically perform them on pull. Both of these actions speed up your immediate rune consumption, so you can start your rune regeneration faster. As such, the cost of these actions specifically on-pull are much lower than normal, making them worth doing under these circumstances.

  1. If you [Death and Decay] *at range* at the start of an encounter for increased damage and mitigation at any target count. (If you are in melee range during this GCD, it is not worth doing using outside normal priority)
  2. [Death’s Caress] is another rotational ability that can be used at range, so, if nothing else is usable as you are setting up a pull, it is important to keep it in mind.
  3. Use [Rune Tap] immediately on pull for a usage that is likely a mitigation increase instead of the usual mitigation loss. (This becomes less useful if other defensive cooldowns are available or if enemies are initially scattered.)

Especially in M+, the on-pull [Death and Decay], in particular, is especially useful and also aids in improving on-pull threat.

What if I’m outside melee range for an extended period of time?

At range, our only offensive ability options are [Death and Decay], [Death’s Caress], [Chains of Ice], and, when talented, [Blooddrinker] (also [Death Coil], but [Death Coil] is almost always not worth using). [Death’s Caress] already has usage conditions in the core ability priority which still apply when outside of melee range. Without a [Crimson Scourge] proc, all of these abilities cost 1 rune and generate 10 RP compared to the 15-30 RP that we could get from a [Heart Strike]. So, if you think you’ll be out of melee range for more than ~4 seconds with more than 3 runes, it can be beneficial to use any of these ranged abilities to generate RP without negatively impacting your long-term rune regeneration.

Still, if you are in a situation where you are forced to kite, it is still often preferable to stay in melee range with at least one enemy unit if at all possible. [Death Grip] can help make this possible.

What if I’m at low health and I don’t have enough RP for a [Death Strike]?

We have a few options as follows:

  1. Kite (more details on this below)
  2. Use one of the following consumables as a substitute for [Death Strike]:
  3. Use remaining runes to [Heart Strike] for enough RP to [Death Strike]

The best options are going to depend on the exact situation you are in. Using [Heart Strike] desperately for [Death Strike] should only be used as a last resort; it’s going to quickly put you into an unrecoverable situation and there’s a time delay before it can help save you. 

When is kiting appropriate?

Kiting should ideally only be done when needed for immediate survivability or if a specific pull has an excessively high potential to kill the tank when they are not kiting, otherwise it is a large negative impact to your personal capability (since most of your personal mitigation and damage throughput relies on melee abilities) and can lower the effectiveness of your group’s damage through excess enemy movement.

As such, kiting is mainly used as a last resort method to mitigate damage or to drop stacks of a stacking debuff. Knockbacks, snares, personal speed buffs, and other forms of CC are usually used to support kiting. Additionally, [Death Strike] healing is based on the damage we have taken in the last 5 seconds, so any attempt to *stop* kiting will mean we initially have a weaker [Death Strike] for the initial 5 seconds of re-engagement. If enemies have melee abilities that can only target the tank, these abilities will likely be off cooldown should you attempt to re-engage these enemies. Also, enemies with ranged methods of dealing damage may still be able to damage you while you may have no nearby [Death Strike] target and your normal RP generation may be impaired.

If you are in a situation where you are forced to kite, it is still often preferable to stay in melee range with at least one or more enemy units if at all possible, since our resource generation is heavily penalized without the use of melee attacks. As far as immediate incoming damage is concerned, you are still drastically lowering incoming damage by staying out of melee range of the majority of the enemies. [Death Grip] is particularly useful in moving an enemy slightly in front of a cluster of enemies so they can be targeted by melee abilities while you remain out of range of other enemies, while [Blood Boil] is still capable of hitting enemies just outside of melee range if you wish to toe that line. Kiting in a tight circle maximizes the time enemies remain in AoE effects and helps to keep them grouped, though this has the side effect of making it more difficult to keep only a few enemies within melee range. For the purposes of keeping only some enemies in melee range while the remaining enemies stay outside of melee range, a straight line can be better (though you will lose group damage potential).

What tools do we have to support kiting?

BDKs have a few kiting tools available:

  • [Death and Decay] with [Grip of the Dead] provides a powerful AoE snare on cast that quickly gets weaker. It has a short cooldown and can make it easy to get out of melee range of enemies. [Death and Decay] should be placed that enemies need to move through the entire area when it’s used for this purpose.
  • [Chains of Ice] provides a powerful single target snare on cast that has no cooldown. Its main drawbacks are that Runes are limited and that it won’t work too well against large groups of enemies.
  • [Gorefiend’s Grasp]  can be used defensively by grouping mobs onto a target that is outside of melee range from you; grouping targets also makes group damage more efficient while kiting.
  • [Death’s Advance] can help counter any snare effects we have and/or help to create a gap between us and what we are kiting. It’s not a strong effect on its own, but it has its uses.
  • [Potion of Gusts], [Wraith Walk], or [Nitro Boosts] can get us out of range quickly by giving us a strong movement speed buff. This tool is more limited, but it can be useful at times.
  • [Death Grip] can separate an enemy so we can still efficiently use our abilities while kiting the bulk of an enemy trash pack (as previously explained).

Are there any tweaks we can make to improve our survivability in especially dangerous situations?

There are two methods that can be used to improve your survivability under the right conditions:

  1. If the high damage you are taking is consistent and predictable, you can wait until your health drops much lower than 70% before using [Death Strike] as long as you are confident the next attack will not outright kill you, which can increase the overall efficiency of your [Death Strike].
  2. If you are worried that you could potentially run out of resources in a drawn-out encounter, you could potentially stop using [Death Strike] to avoid overcapping RP and, in an extreme case, stop using runes when your RP is full. This is a VERY conservative strategy that loses long-term resource generation and damage, but it is something that can situationally improve survivability. Realistically, you generally only need to use this tactic for short periods of time to respond to multi-hit tank-buster mechanics that may require multiple [Death Strike]‘s in succession to survive. Even then, such actions should only be necessary in high-end content and situations for rune throttling haven’t really occurred since the Shadow of Zul from BfA at high key levels

What if generating threat is the immediate priority?

The following options should be considered:

  • [Dark Command] or [Death Grip] can be used to instantly have the top threat on single targets and to increase threat generation by 400% over the 3 seconds after cast. The best way to capitalize on this short duration threat amplification is with [Blood Boil], [Death Strike], and (when appropriate) [Marrowrend], our hardest-hitting abilities on individual targets.
  • If we have no immediate solution to the problem, stunning a target we have lost threat on with [Asphyxiate] or snaring them with [Death and Decay] can buy some time for our taunts to come off of cooldown or to sufficiently damage the enemies to naturally retake threat.

Defensive Cooldown Priorities

While there is not a hard and fast priority list for defensive cooldowns, there are a few things we want to take into consideration:

  • We generally don’t want to stack defensive cooldowns unless we are trying to mitigate extremely large amounts of damage for very specific purposes, since most defensive cooldowns stack in a way that they mitigate less overall damage when used together. For example, if you use two 50% damage reduction cooldowns at the same time, the second cooldown is only effectively mitigating 25% of the original damage. Even for cooldowns that don’t stack in this way (such as [Anti-Magic Shell]), it is usually more beneficial to spread them out to even out the incoming damage profile.
  • If we have no other considerations, we generally want to prioritize the defensive cooldowns that mitigate the most damage, per second, while they are active; this maximizes overall mitigation. The effectiveness of all defensive cooldowns (while active) are as follows:
  1. [Anti-Magic Shell] – 100% of damage taken (if magic)
  2. [Vampiric Blood]* – ~50%+ of damage taken
  3. [Dancing Rune Weapon] – ~50% of damage taken (if it can be parried)
  4. [Icebound Fortitude] – 30% of damage taken
  5. [Rune Tap]** – 20% of damage taken
  6. [Anti-Magic Zone] – 20% of damage taken (if magic)
  7. [Lichborne] – 15% of damage taken (with [Unholy Endurance])

* – [Vampiric Blood] is a bit unique, while it functions as a ~23%-28.5% damage reduction cooldown when we are *just* looking at the increase in healing coming from our healer, it actually does a lot more than that since it increases our own healing by 30%-40%, which is a large portion of our mitigation. The exact strength of this defensive depends on both our character setup and the incoming damage profile, but it is generally much more powerful after accounting for the increase in personal healing.

** – [Rune Tap] details are below

  • It can be worth prioritizing situational defensive cooldowns if you aren’t always going to be able to make use of them. (This mostly just applies to [Anti-Magic Shell] and [Dancing Rune Weapon].)
  • One alternative perspective to take with your defensive cooldowns is to use them to refill your RP pool when it’s getting low, since defensive cooldowns should reduce the frequency that you need to [Death Strike]. This reactive style can be useful in very difficult content, but can potentially result in unnecessarily low defensive uptime if you aren’t being mindful of when you should proactively use your cooldowns.
  • Because of how [Vampiric Blood] works (it affects our healing received and it increases our health pool by a flat 30%), it’s our only defensive cooldown that can be used *reactively* to high damage taken at no penalty. As long as a situation won’t instantly kill us, it can be useful to save this cooldown for moments where you aren’t sure whether or not you’re *actually* going to take a lot of damage.
  • Also because of how [Vampiric Blood] works, your current health % will go down by up to 23% when the buff expires (So, if you have 23% health or lower when the buff goes away your health will be reduced to 1). It can be useful to be mindful of this.
  • [Dancing Rune Weapon] has extra value when our RP is low, since it increases the generation of resources. It also increases our threat generation, making it more useful at the start of pulls. Since it is such a powerful cooldown when talented both offensively and defensively, [Dancing Rune Weapon] should generally be used aggressively when it is getting full value unless you have a specific reason to hold onto it.
  • [Icebound Fortitude] is a stun break and gives stun immunity, which can be an *extremely* useful trait when it can be utilized.
  • [Anti-Magic Shell] can prevent the application of many debuffs, which can greatly increase its value.
  • [Rune Tap] is not used like our other defensive cooldowns, since the RP generation lost by using it would generally mitigate more than [Rune Tap], itself. However, with the current state of BDK resources, the mitigation and potential damage losses are trivial enough that they are not really a concern as long as you are getting value out of the added EHP. Just be cognizant about the rune cost so you can actually have runes on hand if you plan on using this ability and be aware that using this ability could, likewise, conflict with your plans to use other rune-spending abilities.
  • [Anti-Magic Zone] can be used as a personal defensive cooldown, its obvious usage is as a group magic damage reduction cooldown.
  • [Lichborne] is a sleep/fear/charm break and immunity, which is extremely useful in some circumstances.
  • [Blood Shield] provides a shield effect that is applied on top of our health, sometimes the [Blood Shield] from a pre-emptive [Death Strike] can be used strategically for a (very) short-term EHP increase as a pseudo-defensive cooldown, particularly in response to predictable hard-hitting mechanics are about to hit you that can potentially kill you instantly. That being said, you should never be using [Death Strike] solely for the [Blood Shield] unless it is necessary for the situation, since a lot of the healing potential for [Death Strike] is wasted when you specifically use it in this way.

When is [Rune Tap] worth using?

The 5-35 RP lost from using [Rune Tap] over [Heart Strike] generally results in less overall mitigation due to a loss of [Death Strike] healing that outweighs the damage reduction effect of [Rune Tap]. However, the freed up cast time means that we are often able to cast an extra [Blood Boil] as a result, which is further offset if you are using [Hemostasis]. With or without [Hemostasis], the mitigation loss appears to be minor relative to the EHP gains of using [Rune Tap], while damage effect is near-negligible in all scenarios. As such, [Rune Tap] can mostly be used as a normal defensive in the current patch, which wasn’t the case in Shadowlands. In any case, some alternative uses are listed as follows that can potentially give you some extra value:

  1. When you have excess runes, you don’t have an attackable melee target, and you are taking damage.
  2. When you are starting an encounter with full runes and an early usage of [Rune Tap] will allow you to maximize your full rune regeneration at least two global cooldowns faster than you would be able to without using [Rune Tap].
  3. When you have an extended period of time out of combat, the RP you generate with [Rune Tap] will carry over into the next encounter, and the rune regeneration has no other productive use ([Death and Decay] can also be used in this manner).

 

About the Author

Kyrasis

Blood Death Knight Theorycrafter and High Mythic+ Player
Subscribe
Notify of
guest

0 Comments
Inline Feedbacks
View all comments
Scroll to Top