Diablo 4’s Season 12 has already built a nice little side career as a bug anthology, and now it has produced one of its weirder entries yet. This time the complaint is not just “something feels off.” It is much nastier than that: one player says Butcher’s Brutality can be active on the quest log while the actual seasonal systems fail in their own world, then suddenly work properly when they jump into a friend’s. That is not a balance issue. That is your season acting like it has commitment problems.
The bug report is oddly specific, which usually makes it worse
In a fresh post on Blizzard’s PC Bug Report forum, the player says their Seasonal Necromancer appears stuck in a desynced seasonal progression state. According to the report, activating a Slaughterhouse key in their own world triggers the message that the Slaughterhouse is active, but the entrance at the Butcher’s location becomes an open doorway that does not actually lead anywhere. The same post says killstreak/brutality progression does not work correctly in that world, related seasonal interactions in Gea Kul do not appear properly, and the entire setup works normally when the player joins a friend’s storyline instead.
That matters because this is not some side feature nobody uses
Blizzard’s official Season of Slaughter overview makes clear that the Butcher systems are a major part of Season 12. The seasonal questline A Taste of Power starts in Gea Kul, the season revolves around the Killstreak system, and Slaughterhouses are one of the main ways to play as the Butcher throughout a run. In other words, if your world state is bugged here, this is not a cosmetic inconvenience. It is the season’s central gimmick falling through the trapdoor.
Blizzard has already been patching Killstreak-related issues, which makes this extra annoying
What makes this uglier is that Blizzard has already touched Season 12’s killstreak systems in post-launch updates. The current official patch notes say Killstreak multipliers are now highlighted in the UI and Killstreaks no longer reset when going between floors in dungeons, which shows Blizzard has already been tuning and fixing this part of the season. So when a fresh report shows up saying the entire Butcher progression loop can desync in one world while functioning in another, it starts to feel less like one random freak bug and more like the season still has unstable wiring under the floorboards.
A co-op season should not punish you for playing co-op
The player who filed the report says the issue appears to have started after co-op seasonal quest progression in another player’s world. That is still only one report, and Blizzard has not publicly confirmed a broader issue here. But it is the kind of bug that immediately gets attention because it cuts straight into trust. If a season built around shared demon murder starts scrambling your own world state because you played with a friend, that is not “quirky live-service behavior.” That is Sanctuary eating its own save file with a knife and fork.
