Hey everybody, Wyatt Cheng here. Communication is key to a great community, and we’re aiming to improve the ways in which we deliver important information to our players. What you’re reading now is our next communication experiment: a semi-regular blog where we tackle the most commonly discussed questions and feedback from the community. Welcome to Developer Chronicles!
Today's Topic: Wrath of the WastesFor our first topic, we wanted to address a common question from the Barbarian community. For the last few patches, we’ve seen a lot of requests to buff up or redesign the Wrath of the Wastes set. Whirlwind is a very iconic Diablo ability, steeped in the history of the series, so it’s natural for it to be a fan favorite. There’s a lot going on here. Before we get started, the most important takeaway is that we want to make sure a Whirlwind-based playstyle has a place in Diablo III. Therefore, providing ways to make Wrath of the Wastes a reasonable choice as compared to other Barbarian sets is definitely on our list. The last few patch cycles haven’t seen a lot of changes for Wrath of the Wastes for two reasons:
- We are trying to cut down on the number of changes we make to live items. It’s been a longstanding policy that we avoid making changes to Legendary items. Set items tend to be the exception. Our typical approach would be to buff Wrath of the Wastes and Whirlwind by adding new Legendary effects to the game. However, there are a lot of interactions that happen between Wrath of the Wastes and the other Barbarian class sets, particularly Raekor and Immortal King’s. Many of these sets get combined, so in order to prop up Wastes specifically, we have to do so in a way that doesn’t necessarily further buff the other class sets. Otherwise, the gap doesn’t really change. We have some other ideas on this front that we are also exploring.
- Straight talk: Whirlwind causes performance issues. Many of you may remember performance issues during Patch 2.1.0 and 2.2.0. We have been (and will continue to be) making performance optimizations with each patch. However, our initial investigations identified Whirlwind as one of the skills that caused heavy strain on our servers. The more people using Whirlwind, the more it exacerbates the issue. This means we don’t necessarily want everyone using Whirlwind—at least, not until more server optimizations have been made.