Diablo 4 Season 12 has no shortage of bug complaints already, but some of the more frustrating reports are coming from players who are doing exactly what Blizzard would probably like them to do more of: playing together.
A growing chunk of the Season 12 frustration is not just about solo progression or dungeon tuning. It is about co-op and party play, with players reporting that some seasonal systems and class interactions feel unreliable once another person is on screen. The result is a specific kind of annoyance that hits harder in a multiplayer ARPG, because it does not just slow one player down. It can make the whole group feel out of sync.
The Auradin group-play complaint is getting attention
One of the clearest examples comes straight from Blizzard’s own Season 12 known bugs thread. In replies to that post, a player reports that “Auradin seems to stop working in group play when the party is on the same screen.” That does not read like a tiny edge-case visual bug. If accurate, it points to a build interaction losing effectiveness specifically in party conditions.
That matters because class and build bugs always feel worse when they are conditional. If something is broken all the time, players at least know where they stand. If it seems to break only when grouped up, it creates a messier kind of confusion. Suddenly the question is not just “is my build bad?” but “is my build only bad when I try to play with friends?”
Killstreak complaints suggest the seasonal mechanic may feel uneven in groups
The other co-op issue getting traction is tied to kill streaks in party play. A Blizzard forum thread posted on March 12 describes two players leveling together from character creation, only to find that one party member was regularly building kill streaks above 100 while the other struggled to get above 20, despite running the same content together. The poster argued that the seasonal mechanic was creating a visible disparity inside the same party.
That thread alone does not prove a confirmed system-wide bug, but it lines up with reactions inside the known-bugs discussion, where one player called the group killstreak issue a “huge bummer” and said half the reason they play is to co-op with friends. That is a useful detail because it shows this is not just a theorycrafted numbers complaint. Players are framing it as something that actively hurts the social side of the season.
Why co-op bugs tend to feel bigger than they look on paper
A lot of seasonal issues can be brushed off as temporary irritation. Co-op problems are harder to shrug away.
When party play works badly, players do not just lose efficiency. They lose momentum. One person gets progress, another does not. One build performs correctly solo, then behaves strangely in a group. One player gets the satisfying seasonal mechanic, while another feels like they are tagging along in their own session. Even if Blizzard eventually fixes the underlying problem, the immediate impression is that grouping up feels less rewarding than it should.
That is especially awkward in a live seasonal environment where the game is supposed to encourage repeated runs, experimentation, and shared grinding. If party play introduces inconsistent seasonal behavior, players are naturally going to ask whether they are better off splitting up rather than sticking together. That is not a great look for a multiplayer ARPG. This last point is an inference based on the player reports and the type of mechanics involved.
Blizzard has public reports, but not a clean public resolution yet
The most important line to hold here is the difference between player reports and officially confirmed fixes.
The Auradin complaint appears in Blizzard’s known-bugs discussion, which means Blizzard has a visible public thread where the report exists. The killstreak disparity also has its own forum thread. But based on the sources reviewed here, there is not yet a clean public post saying these exact co-op issues have been fully fixed or precisely explained. So the safest framing is that these are active player-reported Season 12 co-op issues, not fully resolved problems with a confirmed public timeline.
That distinction matters because Season 12 discourse is already crowded with complaints. The last thing worth doing is flattening all of them into “Blizzard confirmed everything is broken.” What the evidence supports is more specific: players are reporting co-op-specific problems, those reports are visible on Blizzard’s forums, and frustration around party play is clearly part of the broader Season 12 mood.
This is the kind of bug story that can grow fast
The reason this angle matters is not that every Diablo 4 player suddenly became a co-op specialist overnight. It is that multiplayer bugs tend to spread through perception quickly.
A solo player can sometimes work around a broken interaction and move on. A group of friends tends to notice immediately when the season mechanic feels unfair, inconsistent, or weaker in party play. That creates the kind of complaint that travels fast because it is easy to explain: we were playing together, and the game did not treat us the same. That is not hard for other players to understand. This is an inference based on the kinds of complaints visible in the forum threads.
If Blizzard addresses these party-play issues quickly, this probably stays as a short-lived launch-week frustration. If not, it risks becoming part of a larger Season 12 narrative where players start to feel that grouping up is more trouble than it is worth. And for Diablo, that is a much bigger problem than one bugged screen effect or one weird tooltip.
