By late May 2026, Diablo IV looked less like a game waiting for its next big moment and more like a live service trying to prove it can keep its footing. Lord of Hatred had just arrived, and the game's footprint was still broad: PC through Steam, Xbox One, Xbox Series X|S, PS4, and PS5. That matters because a wide player base notices everything. A broken item, a fast balance change, a slow fix, even the way people talk about D4 Gold in the economy around the game can become part of the daily conversation. What's missing from the available reporting is also worth saying plainly. There aren't reliable details here on season names, patch numbers, loot tables, or exact balance values. So the current picture isn't about a build guide or a tier list. It's about trust. Players are asking whether Blizzard can launch a major expansion, support new systems, and still keep the game feeling fair, responsive, and worth logging into night after night.

The argument around Diablo IV isn't only about whether bugs happen. Everyone who's played a live-service game for more than a week knows they do. The sharper complaint is about what gets fixed first. A May 2026 forum thread showed that pretty clearly. One long-time player said they were losing faith after seeing some issues handled quickly while other problems, especially around new expansion content, seemed to drag on. They pointed to cases such as a Barbarian aspect being disabled and brought back within days, Ball Lightning getting attention quickly, and a new class item, Dirge of Odium, allegedly being too broken to use. Those are player claims from a forum discussion, not a clean patch history. Still, they show the mood. When something powerful gets corrected fast but something unusable lingers, players start reading that as a priority call. Maybe that's unfair. Maybe older systems are just easier to diagnose. But from the player side, it can feel like loud problems get fixed while quiet ones sit there.

That tension lands differently when you put it beside Marcin Undak's comments from Digital Dragons. His point was simple, and a bit uncomfortable: crunch means different things depending on studio size. In a small team, overtime may come from panic. Miss the launch and the studio might not survive. In a large AAA company, the same pressure doesn't always carry that survival excuse. The money, staffing, and structure are usually there. So if people are still pushed into heavy overtime, it starts looking like culture rather than emergency. For Diablo IV, that's a useful lens. Players want fast fixes. Developers need room to work without burning out. Both things can be true, which is why this debate keeps circling back. A service game trains its audience to expect movement every week, but human teams can't live in permanent crisis mode just because a build is broken or a forum thread is angry.

The older Diablo design philosophy makes the issue even more pointed. Max Schaefer once described the original idea as cutting through the old RPG clutter: get into the game, hit monsters, get loot, feel rewarded. Not spreadsheets first. Not punishment systems first. That's still the emotional contract players bring into Diablo IV. They want action to feel immediate and rewards to feel good in the hand, even when the game has become much bigger and messier than that first vision. Lord of Hatred adds to that pressure because every new class item or system has to fit a loop people already understand by instinct. If it doesn't work, players don't treat it like a footnote. They treat it like friction in the thing Diablo is supposed to do best. Whether someone is chasing drops, testing builds, or deciding where to buy D4 Gold before another long session, the expectation is the same: the game should respect their time and keep the hunt feeling alive.