Five Interviews from Diablo 4’s First Post-launch BlizzCon
These November 2023 interviews explain how Blizzard approached Season of Blood, Abattoir of Zir and the newly announced Vessel of Hatred. They are a record of the developers’ thinking at that time, rather than announcements of upcoming content today.
The most useful distinction is between a development goal, a feature preview and a released rule. Each answers a different question: why a change was being made, what was planned, or how players could actually use it.
Game Informer: Why Seasons Needed Separate Teams
In Matt Miller’s November 10 interview, franchise manager Rod Fergusson and game director Joe Shely described separate groups working on live support, seasons and expansions. Parallel development meant a later team could keep building its release while another shipped its own.
Fergusson also described challenge coins awarded for the base game and season launches. These recognized staff milestones; they were not in-game rewards.
Shely explained an important feedback constraint: Season 1 was largely complete when Diablo 4 launched, so Season 2 could reflect more post-launch learning. He also clarified the leveling headline: reaching level 100 roughly 40% faster came from combined progression changes, especially later in the journey. It did not mean every experience reward simply received a flat 40% increase.
Screen Rant: Which Rewards Would Survive the Season?
Carrie Lambertsen’s November 13 interview with Joe Piepiora and Tiffany Wat separated temporary progression from lasting cosmetic unlocks:
| 2023 interview subject | What the developers described |
|---|---|
| Abattoir of Zir and Tears of Blood | Both were tied to Season of Blood and would leave at its end. |
| Midwinter Blight participation | Seasonal Realm access, rather than Eternal Realm participation. |
| Midwinter cosmetic rewards | Wat announced 18 earnable cosmetics that players would keep after the event. |
Piepiora described AoZ as a place to test powerful endgame builds, with 25 escalating tiers and a run ending on death. For the published event window and later rules, use the original AoZ event reference.
He described a different challenge for The Gauntlet: accumulating score in an open dungeon whose layout stayed fixed for a week. Repeated attempts could improve route knowledge. That weekly competition was separate from AoZ’s escalating tiers; these were previews, not interchangeable dungeon rules.
But Why Tho?: Making Player Goals Enjoyable to Pursue
In Mick Abrahamson’s November 4 interview, Piepiora named concrete goals: reaching level 100, defeating Uber Lilith and finding an Uber Unique. The issue was whether progressing toward them stayed enjoyable.
He pointed to feedback about leveling slowing around levels 58–63 as a reason for Season 2 progression changes. That explains a design problem more precisely than a general promise to make the game “more fun.”
Wat also outlined plans for players to enter Vessel of Hatred’s campaign with story context, including a base-campaign recap. Piepiora said a new class needed a distinct playstyle and fantasy while existing classes continued receiving support. Those were 2023 expansion plans.
Press Start: Why the Story Returned to Nahantu
Cami Wolfe’s November 8 interview connected the setting to Mephisto. Wat explained that the soulstone carried by Neyrelle was the vessel holding the Lord of Hatred.
Returning to Nahantu linked that story to Diablo 2’s Act III locations, including Kurast and Travincal. The aim was to revisit places changed over time, not merely repeat the earlier campaign. Piepiora discussed expanding explorable Sanctuary without promising that every corner of its map would eventually become playable.
The A.V. Club: Expansion Scope and Spectators
William Hughes’s A.V. Club interview connected expansion scope with campaigns, regions and classes, and discussed The Butcher’s streaming appeal.
Developer ambitions explain the direction of a project. They do not establish a price, guarantee a purchase’s value or replace the requirements published when a feature launches.
