Somewhat tucked away in the Patch 1.0.5 notes was this tidbit about a change to a popular Barbarian skill.
That might not sound like a lot, but the proc coefficient is what causes all those other tasty effects to trigger, such as Critcs and Life on Hit, which is why Barbarians using this skill, almost always paired with Whirlwind, were basically unkillable. That was okay with the devs in v1.0.4, but with the Monster Power system coming up in v1.0.5 it was too OP, since Barbs could just run in circles indefinitely and eventually whittle down even the fiercest enemies on Monster Power 10, at little risk to themselves as their Sprint tornadoes kept hitting, procing, and healing.
So the proc chances were dropped from 20% to 8%, which means the build will still work fine for dealing damage, but the Life on Hit and Critical hits will be procing much less frequently.
Wheres the diversity in killing a build? i didnt paid for this D3 1.05, at least give my money back!
Lylirra: Run the Like Wind makes WW/double tornado barb a very strong build by combining multiple benefits into one neat little package: life regeneration, Fury gain, damage, in-combat mobility, and run speed. It’s all there. Ask just about anyone (or take a look at the posts in these forums) and they’ll tell you WW barbs are incredibly powerful, and it’s also one of the first builds people point to when the word “nerf” is mentioned.
I think most players — whether they’d admit it publicly or not — probably agree that the tornadoes left by sprinting (a skill that provides utility, huge mobility, and proc effects including Life On Hit and Into The Fray) shouldn’t be so powerful in comparison to other skills that have restrictions on them. Like Hammer of the Ancients, which requires you to stand still, swing, and who’s sole purpose is to deal damage. We’d like to bring the skill more in-line with other build options, and we think that from a pure design standpoint the problem is tornadoes triggering procs, most specifically Life on Hit.
The survivability you get from WW with LoH is definitely an outlier compared to other available builds. This wasn’t a huge issue previously, but once we introduced Monster Power it became clear that we needed to make some adjustments. Basically, when we were doing our initial testing for 1.0.5, anything that didn’t kill WW barbs in the first second of combat failed to be any sort of real threat, and that applied even after scaling Monster Power up to its higher settings. The amount of damage enemies do at higher Monster Power levels is pretty insane, and while the WW barb was still doing fine, it felt punishingly unfair to every other class and barbarian build.
This introduced another problem: if a WW barb could heal from empty to full health in half a second, then for any monster to pose a threat it would need to take you from full to dead in less than half a second. We could certainly make damage more spikey, but most players don’t enjoy being insta-gibbed, and we tend to agree that going from full health to DEAD without ever seeing your health hit those intermediate values can make combat feel a little shallow. Having times when you want to play more conservatively vs. more aggressively can add depth to combat and make it more interesting, so (in general) we try to avoid creating situations where spikey damage is the norm.
So, even though we really liked the build, in the end all the data was telling us that WW needed to be changed.
That was just the start of Lylirra’s very lengthy explanation; click through to read the full statement.
Lylirra: Just to give you some history, when we started to troubleshoot how we could better balance Run Like Wind, we didn’t want to remove the ability for tornadoes to trigger procs completely. Rather than break the build, we wanted to find ways to reduce the sheer efficiency of it without removing the fundamental mechanics that make it work. We also discussed options outside of adjusting its proc coefficient, too:
After a lot of internal testing and heated debates, we ultimately decided to address the core of the issue and reduce Run Like Wind’s proc coefficient, and we brought it down by a significant amount (from 0.2 to 0.08). We want to make sure whirlwinding is still viable, though, so to compensate, we also dropped down Whirlwind’s Fury cost from 16 to 9. This should make it possible for players to still whirlwind continuously, but it lessens the need to have Sprint in order to use Whirlwind at all.
Of course, we’re really looking forward to players jumping on the PTR, testing out the changes first-hand, and sharing their feedback. We’re still working out a few kinks with the PTR client, but hopefully we can start getting that feedback pretty soon now. 🙂
This isn’t a huge surprise; the build was pretty obviously overpowered and furthermore, it seemed unintended. We debated this on the podcast a few times, and generally agreed that Blizzard had almost certainly meant the Sprint > Run Like The Wind rune effect as a cool bonus feature, kind of like the Vault > Trail of Cinders rune effect or Spirit Walk > Severance, where the character adds a bit of damage to their escape skill.
It seemed highly unlikely that the devs had meant Barbs to be able to Sprint indefinitely, while maintaining full health and dealing big damage, without any real personal risk. And given this patch nerf, it would appear that we were correct.
So, all the people not playing Barbs are indifferent or feel this is a good change to take down an OP build, and all the Barb players are outraged and threatening to boycott? Or do you think the build will still work okay; you’ll just need to up your critical hit chance to like 70%?Related to this article