wow Blue Posts Round-up: Apr 3

[Stan 5,240]

Today's blue posts talk about the new Artifact Solo Challenge, changes to Brewmaster / Mistweaver Monks and Outlaw Rogues coming in Patch 7.2.5.

Artifact Solo Challenge

Mage Tower is now active in NA and players are already whining about the challenge being too hard, crying out for nerfs. It's supposed to be challenging and there are currently no plans to tune down the difficulty. The scenario will get easier with better gear.

Blizzard (Source)

I get that these appearances are the new hotness and everyone is after them, which causes frustration. However, it's worth noting that the solo challenges to unlock the new appearances are intended to be just that; a challenge. We don't expect the majority of players to obtain them within the first cycle of the Mage Tower being constructed.

Our aim for these challenges is for them to be comparable to that of the green fire questline for Warlocks in Mists of Pandaria. In that case, only a few Warlocks were able to defeat Kanrethad immediately, but more and more were able to overcome the challenge as the expansion progressed.

As we progress through the course of Legion, your character will become stronger (through Artifact progression, gear upgrades, etc), which will naturally ease the difficulty of these challenges. Likewise, as more and more players complete these challenges, more community generated content will appear giving advice for those who are struggling.

Ultimately, each artifact appearance has a different source. Some reflect dedication to a particularly gameplay style, such as raiding or PvP, others for reaching milestones like completing the 7.0 Order Hall line. In the case of these challenge appearances, they are meant to show that you've truly mastered the nuances of your spec.

Brewmaster Monks in 7.2.5

A huge post with plans to address issues with Brewmasters in a forthcoming content patch.

Blizzard (Source)

Hail! First round of Brews is on me, Monks. Shall we talk a bit about Brewmasters?

As Seph talked about in a recent Rogue thread, 7.2.5 will include much more significant class change than 7.2 did, and one of the specs that we're focusing on is Brewmaster. Brewmasters are currently quite strong, performance-wise, but have a few notable issues that we'd like to work out.

Offensive Abilities

Rotationally, Brewmasters are using a mixture of offensive and defensive buttons. Some parts of this worked well, such as Keg Smash and Tiger Palm granting partial charges of your Brews. One part that hasn't worked out well is in Blackout Strike and Breath of Fire. Having no direct defensive value, or interaction with other abilities in your rotation, they end up feeling disconnected, and leave you wondering why you're hitting them. There are a couple minor artifact traits that give them some defensive value, but that's ultimately negligible as far as rotation design goes. One saving grace here is the Blackout Combo talent, which gives a strong reason to care about Blackout Strike, and add a lot of depth (and complexity) to your rotation.

Another problem is that Blackout Strike has a 3.0s/Haste cooldown, which is actually rather bizarre on a class with a 1.0s GCDs. Experienced players have learned that you should get a significant enough amount of Haste to bring that down to something in the 2.2-2.5sec range, and alternate Blackout Strikes with other abilities, with awkward 0.2-0.5sec gaps in between your abilities. This also means that with the forced gaps, you become GCD-capped, and Energy stops functioning. Finally, one last problem we're looking at is that there are rather limited options for customizing the rotation through talents (pretty much just Blackout Combo), and no baseline variability, leading to some people finding it repetitive and predictable.

We'd like to clean this up, and here are our current thoughts on how (not set in stone, very interested in discussion and PTR testing). 

• First, Blackout Strike and Breath of Fire will have a direct defensive value: they'll grant a stack of Elusive Brawler (per target hit, in Breath of Fire's case).
• Second, Blackout Strike will more smoothly fit into the rotation. We're going to try it having a cooldown, but Tiger Palm significantly reducing that cooldown, such that you can Blackout Strike every few GCDs, and not have any forced partial-second pauses. We want to make sure that Energy (and thus Haste) controls the speed of your rotation, so that that's in your control. If you want a more full, button-spammy rotation, you can favor Haste. If you prefer being more tactical with your GCDs, optimizing the timing of each one, you can favor other stats.
• And finally, to let you customize the rotation with both higher GCD utilization and some variance, we're planning to add a talent that gives Tiger Palm a high chance to reset the cooldown of Breath of Fire. (Where exactly to put that talent is unclear; replacing Chi Burst is the current idea, but we're not super thrilled with that.)

Defensive Abilities

Overall, Stagger is working quite well in the general case. Ironskin vs Purify (and in particular when to Purify) is a good choice, though maybe a tad bit skewed toward Ironskin right now. However, it becomes problematic in the extreme case, where Stagger is used to cheese mechanics that aren't intended to be survivable. For example, a Brewmaster may use High Tolerance and Fortifying Brew in order to get 100% Stagger, soak several of some raid mechanic that is intended to be entirely unsurvivable (probably even piercing immunities), Purify twice quickly, and get healed through what little of the damage is remaining. The key source of this is when Stagger reaches 100% or near-100%, and our planned changes to solve this focus on that:

• We'll be reducing the Stagger gain of Fortifying Brew, and slightly reduce the Stagger gain of Ironskin Brew.
• We'll be raising Brewmaster's base armor to compensate.
• We're going to add a cap on how much damage can be Staggered (high enough that you won't hit it in normal gameplay, but enough to stop cheesing mechanics).
• There is also an artifact trait that increases the Stagger gain of Fortifying Brew that has been mostly-useless since 7.1.5, which we're going to redesign.

Again, the point of this is not at all to be a nerf in intended circumstances, but rather to shift around where the mitigation comes from, such that it can't be used to unintentionally bypass mechanics.

Relatedly, one mechanic that causes imbalance with tanks is that in a tank-swap situation in a raid, tanks can store up a large amount of active mitigation while not actively tanking, both in terms of ability charges, and buff durations. In general, this is fine, but it can be taken to extremes, and Brewmasters are a good example of that, frequently being able to go into their tanking with a 30+sec duration Ironskin Brew rolling. Some amount of this is fine, but to keep it within a reasonable range, we're going to put a cap on how long you can extend tank active mitigation buffs, to a maximum of twice their base duration. Thanks for reading! We look forward to your feedback.

What are you doing to address the fact that ISB has basically become the new shuffle and requires 100% uptime? That's literally brew gameplay right now -> 100% ISB uptime and anything left goes into purify.

I touched on that a bit, that the decision is skewed a tad bit towards Ironskin right now. There are 3 changes here that will help with that:

• The increase to base armor will help with the problem of Ironskin falling off feeling like a death sentence.
• The reduction to Ironskin effectiveness will slightly decrease the difference between Ironskin being up and not.
• Our current plan for the mentioned artifact trait replacement is Purify percentage, which will increase the value of Purifying.

How does a talent like Tiger Palm resetting Breath Fire work when you have the legendary chest? Clearly we wouldn't take it since Keg is resetting breath about every 5 seconds. With both it would be absurd.

Occasional legendaries that push you away from or toward a particular talent are generally OK. If you have the Breath of Fire chest, you likely will want to pick one of the other talents instead of Spitfire (the Tiger Palm resets Breath of Fire one), and that's OK.

Will there be exceptions added to this rule? For example, will this not just completely negate the use of the 'Bastion of Light' talent for Protection Paladins? Gaining the instant charges allows them to go much further beyond the "twice their base duration", essentially throwing away all that additional SotR uptime that comes from the talent during the activation window.

There may be, yes. We don't want to invalidate any existing gameplay, just prevent the "I've been offtanking for a bit and have a crazy long duration buff up when I take over, skewing my priorities."

Without hard numbers, it is difficult to see if this will be a blessing or a curse.

Numbers matter for performance, and I want to reemphasize the fact that the changes I'm talking about are intended to be net-neutral, performance-wise. Of course they will affect performance, but we'll offset them with number tweaks, in whichever direction is necessary.

The point of all of these is gameplay, mechanics, and particularly rotational flow.

My first concern on hearing that there is a stagger cap is what does that mean for damage intake: once you're at stagger cap, do you take full damage from hits? How do you anticipate this working on mobs like The Demon Within, which is already hitting for approximately 5 million white damage per auto set? Extrapolating further to future mythic tiers, it's not necessarily unreasonable to anticipate mobs that will be hitting a monk in excess of 7+ million white damage (for example) every 1-1.5s. Given brew generation in your most favorable circumstances, it seems there is a real possibility of brewmasters essentially hitting some upper limit of mob they're able to tank before they're essentially as squishy as a dps, save dodging, due to having capped stagger.

To be clear, the stagger cap is not on the amount you can stagger per-hit, but on the total amount you can have delayed in your "stagger bar" at once. As stated, it's mainly a limit to avoid abusive cases, similar to how spells like Guardian Spirit have a point where they stop working. If you're about to try to soak something that will do a few times your maximum health in damage (even after cooldowns), you should expect to die immediately. This should come into play only in relatively extreme cases.

What exactly do you mean by a cap on how much damage can be staggered? Is there a maximum amount of damage that is allowed to be in the stagger dot? Or does each attack have a maximum amount that can be absorbed from it and added to the stagger dot? This is hugely important to know.

There will be a maximum amount of total damage that you can have banked in your Stagger DoT. Any overflow beyond that will continue through to your health.

I personally love the way Blackout Strike fits into the rotation, especially with Blackout Combo.

And you're not alone; we recognize that there are many Brewmasters who love Blackout Combo, and have Haste in the right thresholds to make it flow reasonably well. One of the things of utmost importance to us with this rotation change is that it doesn't feel worse to those like you. We have several experienced Brewmasters internally who voiced this apprehension when first hearing about these changes, and after playtesting it they all agreed that it felt the same to them. In our books, that's a win, since it's an improvement for the rest of the Brewmasters who aren't in that sweet spot. We hope that sentiment is common externally as well, so please test it out when the PTR goes up, and let us know how it feels. Your feedback on this really matters.

The ability to be GCD capped, or very close to it, is something that I have always loved about brewmasters and on a personal level of feedback it is really important to me that that type of gameplay is still available and viable. Brewmaster has always been a very high APM spec (even if not all of the GCDs directly translate to defensive benefits) so please be careful to maintain that as you tinker with the rotation.

We absolutely hear you, and are targeting Spitfire, Rushing Jade Wind, and Haste at players like you. It'll probably take us some iteration on the energy and proc rate numbers to get the feel just right, so we'll need your help with PTR testing feedback.

Please Increase the IsB duration cap, at least 30-40s. 16s is too short.
And when will you address that bears have been OP for too long and EASIER to play without any significant nerf?

We're starting with a cap of "double the base duration," but that may feel too restrictive, and we'll iterate. This is still early in the process (PTR hasn't even started yet), and none of this is set in stone.

Cheers to everyone that has provided valuable feedback here so far. We'll keep reading and iterating.

First, Blackout Strike and Breath of Fire will have a direct defensive value: they'll grant a stack of Elusive Brawler (per target hit, in Breath of Fire's case)." -- I am sure you are well aware this will push Mastery's value through the roof.

That's certainly possible, and we'll adjust stat tuning if needed. Again, this is intended to be performance-neutral, so we're not trying to buff OR nerf overall performance here.

On the AM max duration discussion, there's been a ton of great feedback on that so far. I'd like to go into why we're considering this change a little more. Forgive me for the verbosity (hah):

This effects Brewmasters more than other tanks, but not exclusively. The main reason that this affects Brewmasters more is that they are meant to split their resource between two brews: Ironskin and Purifying.

Consider a simple situation of two bosses, each beating on a tank. The Brewmaster is using a mixture of their Brews, maintaining ISB while using excess on PB (or maybe even letting ISB fall off when the boss stops to cast something, or is otherwise unthreatening for a moment). She gets more Brew charges than she needs to keep ISB up, but she's using those excess charges on PB, so ISB duration is remaining low.

The co-tank, let's say a Warrior for example, is built a little differently, having two separate defensive resources (Shield Block charges and Rage for Ignore Pain). Both are being generated and consumed at a similar rate, also not gaining increasing Shield Block duration.

Things are good here, and let's suppose for the sake of argument the two tanks are 'balanced' in this context.

---

OK, now let's change the design of the fight, to one where there's one huge boss, and the two tanks take turns tanking for 30sec at a time. Arguments of this being a less-engaging fight aside, let's look at how that affects the tank balance.

While the Warrior is OTing, he's building up Shield Block charges, but once he hits max charges, they're being wasted. He can use one at a time as they're generated, but they don't last longer than it takes to generate, so his Shield Block buff duration doesn't grow over time. Similar deal with Rage and Ignore Pain. He builds up Rage, and when that caps out, he builds up an Ignore Pain stack, but that caps out pretty quickly too. Excess Rage is wasted (at least defensively anyway; they can put it into damage). When the Warrior taunts, he goes into it with some buffer of his max Shield Block charges, maybe a single partial Shield Block buff, and max Rage and Ignore Pain. Overall, he could carry over some value from that time not tanking, but not all of it.

Meanwhile, when the Brewmaster is not tanking, they're building up charges of their single defensive resource, Brew charges. Once at max Brew charges, she starts using Ironskin Brews, as they're generated. Since there's nothing to Purify, she never does so, and all of her charges go into Ironskin Brew, creating a surplus of Ironskin duration that just grows over time. When she taunts, she goes into it with max Brew charges, and a 1min long Ironskin buff. She never has to Ironskin the whole time she's tanking, and can send all of her Brew charges into Purifying, over tripling (if not more) how often she can Purify, providing a sizable gain over her Warrior counterpart. All that time she spent not tanking goes into storing up defensive value for when she is tanking, with no limit.

If the two tanks were 'balanced' in the first fight, then the Brewmaster is overpowered in the second. Alternatively, if you argue that they're balanced in the second fight, that means they're underpowered in the first. The goal of this change is to place a reasonable limit on how much value you can carry over from time spent not tanking, so that we can tune the tanks to be balanced in both of these situations, not just one of them.

I totally get that right now you can always get benefit out of hitting Ironskin Brew, never being fully wasted, and so the prospect of going to a system where there may be a time where you're just sitting on full charges, wasting them sounds like a negative. Please understand that for most other tanks, that's just normal; a Warrior that's not tanking is just wasting the defensive value of their Shield Block charges once at max charges, and that's just an accepted norm. By bringing Brewmasters into parity in this regard, we can then tune them to be more consistently balanced with other tanks, which is the core goal of the change.

One of the most common responses so far has been "I understand wanting a cap, but 2x*duration is too short". Totally reasonable argument, and we'll need your help finding what the right cap is. We chose that to start with because that's consistent with things like Ignore Pain, Mark of Ursol, Blood Shield, Soul Fragments, etc. Given the more liberal use of Brew charges, it may be more appropriate to be higher for Brewmasters.

I'd love to keep hearing your thoughts on this, and I hope that this massively-over-verbose post helped better explain our thought process here. Thanks to those of you that stuck with it, reading it all the way through. :)

This is probably the most extreme example I can pull from in game currently and it results in 21.5 million staggered, which is certainly a lot but I know on Mythic Gul'dan, there have been moments where I've had between 10 million and 18 million staggered and subsequently purified. How will this design idea allow those two different situations to co-exist? How does the game react to me being sent to stagger cap because of a single huge ability that should've killed me rather than the fact that the boss encounter just hits extremely hard? And if your retort is "well, brewmasters shouldn't be able to solo fel scythes and still continue to tank the boss" my counter is "what about guardians doing the same thing with roughly the same amount of externals?

That is exactly my retort, and Guardians shouldn't be able to either. Soloing every 100-Energy Fel Scythe is perfect example of the cheese this is intended to prevent, and we'll be preventing it on Guardians as well.

How much of a threshold are we talking? One stagger bar? Two? Five? Ten? 

When we reach this threshold, what happens? Do we begin to take unmitigated hits? Will stagger simply stop working? If so, what's the plan for taking an unmitigated raid boss hit, as a few bosses are capable of 100-0% a 910 brewmaster in a single swing?

The current idea is that the Stagger bar that the UI shows is the cap, which matches up with your health bar, since that'll be the most understandable and intuitive. Then, however much of a buff to max health is needed to make that balanced.

Example, with 80% Stagger, 33% Armor for convenient numbers:

HP: 100/100 ~ Stagger: 0/100

Take a hit for 30, armor reduces that to 20, then stagger takes 16, and 4 goes through to HP.
HP: 96/100 ~ Stagger: 16/100

Time passes and 8 of the Stagger damage goes over into HP.
HP: 88/100 ~ Stagger: 8/100

Then you take a big hit for 60, armor reduces that to 40, then stagger takes 32, and 8 goes through to HP.
HP: 80/100 ~ Stagger: 40/100

You quickly Purify 50% of that.
HP: 80/100 ~ Stagger: 20/100

Then you take a *massive* hit for 210 (something cheesy), armor reduces that to 140. Stagger would take 112, but there's only room for 80 in your Stagger bar. So Stagger takes 80, and 60 goes through to HP.
HP: 20/100 ~ Stagger: 100/100

TL;DR: The Stagger bar on your UI is now representative of your maximum stagger pool, and any overflow damage continues on into your HP bar. Max HP is increased as needed, such that these two bars combined are a big enough pool for normal gameplay.

Alright, second round is on me as well, Brewmasters. Now that the weekend is over, we've had a chance to discuss all the great feedback you all have provided so far. Here's what we're thinking:

(Note that the below changes likely won't make it into the first PTR build.)

Stagger Cap

As I said, the goal of this was cheese-prevention, not intended to impact normal gameplay. A Stagger cap of 100%*HP has a lot of value to us due to it functioning intuitively within the UI. We had hoped that the amount we need to buff HP/Armor would be reasonable in order to make that work, but looking at the numbers and your feedback, we don't think there's enough room there. Therefore, we're now leaning toward a 200%*HP cap, and that just won't be visible in the UI (but then, neither is the cap of Guardian Spirit and the like).

Active Mitigation Duration Cap

There has been a ton of useful feedback about this topic. Being able to carry over a ton of banked Active Mitigation (and Ironskin Brew absolutely is AM in context) from tank swaps and low damage phases is extremely powerful, and contributes to imbalance between tanks. But we're also sympathetic to how it adds an additional complication that you need to keep in your mental space. We think that just loosening the restriction up a bit so that the window you can safely press Ironskin Brew in is much wider will satisfy that, so we're going to try a cap of 3x Duration instead of 2x. And to clarify, calling this "base duration" was inaccurate; I meant the duration of a single cast of Ironskin Brew, including traits (so 3x Duration would be 24sec with 4/4 of that trait).

Magic DR

We've talked about having armor and potentially HP as tuning knobs to use. We also have the % of Stagger that applies to Magic to use. All of the changes we're discussing in this thread are for mechanical and playstyle reasons, and then tuning is a separate (but big and important) issue. Just to set expectations, Brewmasters with Mystic Vitality are currently seen as extremely strong against Magic damage, sometimes overpowered. Guardian Druids are also overpowered against Magic damage, and that will be adjusted as well.

Thanks, and keep the feedback coming!

Mistwaver Monks - Essence Font With CD

Blizzard (Source)

What are we supposed to do when Essence Font is on cooldown, Uplifting Trance isn't available, Whispers of Shaohao has been used, and the the group still needs to be healed?

The initial version going out has a small buff to baseline Vivify. Also, the changes greatly increase the practical value of mastery, which is a hidden buff to the Vivify, Enveloping Mist, and Effuse casts you'll be making in between Essence Fonts.

Part of it, though, is you should have more of cadence between the high-priority heals that somewhat solve problems on their own, and the spells that don't always do that. You asked what to do when the "best" 3 or 4 things are on cooldown or not available, and that's similar to a Druid falling back to laying down Rejuvenations when she can't use Wild Growth or Swiftmend, or a Paladin using Flash of Light between Light of Dawn and Holy Shock cooldowns. Making use of the no-cooldown spells that are more limited is meant to be a moment when you look forward to the next heavy hitter coming back (even if it's just a few seconds for an Essence Font).

The concerns in feedback seem to mostly reflect tuning--that the "filler" kit of Vivify, Enveloping Mist, Effuse, and Soothing Mist isn't strong enough. Possibly that's true and the problem has been papered over on live by the ability to focus everything on Essence Font. Overall tuning will be something to watch on PTR, as with any spec getting any degree of shakeup. Tuning debates usually aren't too productive in early feedback, but maybe a helpful thing to say is: "if we hadn't been making any changes to Mistweaver, it would probably have gotten a small flat throughput buff before the next raid."

With the changes to Mistweaver during the transition to Legion, there was already a degree of homogenization from what was previously a fairly unique gameplay experience to something more similar to what already existed in other healing classes. As you consider further changes to Mistweaver, is further samey-ness something that's "on the radar"?

It is, although possibly in the opposite way. If anything, thinking that Essence Font had to be forced into an off-cooldown design from the start "just to be different" probably didn't help anybody. The spec flowing better for everyone using it matters more than symmetries or antisymmetries between specs and how they look on paper. Nobody actually playing either spec is going to forget whether they're on a Mistweaver or a Resto Druid just because Essence Font follows a successful design like Wild Growth. The spells around them, the different interactions they have, and the whole pile of talents, traits, and item bonuses all doing different things ensures that.

There's always a balance between lessons and good designs that are generally true throughout the game, and variance between specs. And powerful AoE heals usually having some cooldown (for a number of reasons) is a factor that's more likely to improve Mistweaver gameplay than worrying about being a carbon copy of other specs (which it's pretty far from, all things considered).

Outlaw Rogue: RTB & True Bearing

Changes coming in Patch 7.2.5.

Blizzard (Source)

Two things I think many of us can agree on right now: 

• 1. True Bearing's cooldown reduction per combo point spent mechanic is fun to play with. The mechanic has been on the spec for a long time as a passive with a different name (Restless Blades), and largely drove the pacing and feel of the spec.
• 2. True Bearing is much stronger than any of the other single Roll the Bones buffs, on average.

That said, we're going to make two changes to Outlaw Rogues in 7.2.5:

• 1. The True Bearing mechanic is being added to Outlaw as a baseline passive (called Restless Blades), tuned to an appropriate pacing and power level for how many combo points the spec currently generates. Restless Blades, currently in 7.2.5 is tuned at 0.5 sec of cooldown reduction per combo point because realistically, the spec now generates easily 2-3x more combo points compared to a couple expansions ago, and the pacing impact and tuning of Restless Blades should reflect that.
• 2. True Bearing will remain as one of the 6 Roll the Bones buffs, but will be tuned down from 2.0 to 1.0 sec of cooldown reduction per combo point. We're serious about balancing each of the 6 individual buffs against each other, and True Bearing at 2.0 sec is clearly out of line.

We'll be keeping a close eye on Roll the Bones during 7.2.5 development, and as usual will make further tuning/adjustments as necessary.

[Realmouse 5]

the mage tower quests are not a skill check, they are not  even very much of a gear check, they ARE however a massive hardware check, IF you have less than perfect internet connection...they are impossible to complete due to the zero tolerance timing, one tiny lag spike and its failed.  

[Unicurn 1]

So Due working i have not been able to try it yet , but is it possible for tanks to solo it ?

[Eukray 5]

13 hours ago, Realmouse said:

the mage tower quests are not a skill check, they are not  even very much of a gear check, they ARE however a massive hardware check, IF you have less than perfect internet connection...they are impossible to complete due to the zero tolerance timing, one tiny lag spike and its failed.  

Those are mean to be raid Mythic difficulty level wised and I think they are tuned just like it should (WW monk here). I tried and failed 21 times before beating it and it felt awesome. I had to use everything I can to beat it and I'm only 895 ilvl. Sometimes in mythic you die of bad luck or because you failed to predict what will happen soon enough and I can guarantee that lag will kill you. It's not mean to be easy so yeah, hardware and a good internet connection is mandatory.  

[RoseZ12 6]

people rushed mage tower though they knew it would be a challenge like the green fire questline from pandaria.. and now cry for nerfs? pathetic.. ofc they wont stand a chance at actual gear levels. maybe after tomb opens they can try.. but crying for nerfs right now is just the usual shitstorm.. do people really think they walk in get the appearance first try? blizzard told them it wouldnt be the case. its a CHALLENGE for a new appearance. but if wow players have to work for something they get cringy..

[Realmouse 5]

my only beef with the mage tower is that blizzard flat out lied to us.  they said it would be a skill based scenario, it is not. they said it would need expert levels of class knowledge, it does not (basic understanding of a class is all that is needed, anything else has no use in there),  they said it would be like the warlocks green fire quest, this is so far from the truth its aggravating..the mage tower is proving grounds 2.0.