Diablo 4 Bloodied Provisions Bug Still Blocking Progress

 

Diablo 4 has another Season 12 problem on the table, and this one is the kind that turns a normal checklist objective into a brick wall. A fresh Xbox bug report says the Bloodied Provisions seasonal quest still will not complete even after every gear slot is filled with blue Bloodied Magic items. That would already be annoying on its own. The uglier part is that this does not look like some fresh one-off freak accident. It looks like an old wound that never really closed.

The quest sounds simple, which makes this worse

According to the new official Xbox forum report, the player says every slot is filled correctly, the objective still refuses to trigger, and none of the suggested fixes floating around Reddit, Steam, Xbox, or Blizzard’s own forums solved it. That is exactly the kind of bug that makes players start second-guessing reality. Not because the system is complicated, but because it is supposed to be dead simple. Wear the gear. Get the credit. Move on. Sanctuary, naturally, has chosen chaos instead.

This is not a brand-new complaint

That is the key detail here. Blizzard’s own Season 12 known bugs list already acknowledged in March that the Bloodied Provisions objective was not working correctly and pointed players toward a workaround: equip all Bloodied Legendary items, then swap in one magic or rare piece. Separate March threads from players on Paladin, Barbarian, and other characters show the same basic frustration, with some saying the objective still would not clear even after trying multiple item combinations. So when a fresh April 21 report says the quest is still busted, it lands less like a surprise and more like another miserable checkpoint in a bug that apparently refuses to die.

Why this one actually matters

Diablo 4 can survive a weird animation bug. It can survive a cosmetic menu acting possessed for a day. A seasonal progression objective is different. These are the tasks players are supposed to clear on the way through the season, and when one of them stops tracking properly, the whole seasonal rhythm starts to feel rotten. It also fits a broader Season 12 pattern we have already seen on Diabloz, from reward issues tied to Bloodied boss loot to earlier progression friction around Season 12 quest blockers Blizzard had to hotfix. At some point, “just one more bug” stops sounding small.

Still alive, still ugly

At the time of writing, the new Xbox thread is live, public, and not showing a visible Blizzard reply yet. That does not prove the problem is widespread again, but it does prove something more than rumor: players are still running into Bloodied Provisions trouble weeks after Blizzard publicly said the objective was bugged. For a seasonal checklist objective, that is a pretty bad look. Diablo 4 does not need every menu and reward track to feel haunted. Right now, though, it keeps volunteering for the role.

Read More

Diablo 4 Players Say Some Monsters Are Literally Not Killable

 

Diablo 4 has had its share of annoying bugs lately, but this one cuts right past irritation and into full gameplay paralysis. A fresh player report on Blizzard’s PC bug board used the bluntest possible headline: “I cannot commence because Monsters are actually not killable.” That is not a balance complaint. That is not a loot gripe. That is the game allegedly putting enemies on the field and then forgetting to let players finish the job.

The original thread on the official Diablo IV PC bug report forum was posted on April 19, 2026, but it was also quickly marked as deleted by author. That means the public evidence is thin, and nobody should pretend Blizzard has confirmed a broad new unkillable-monster plague. But the topic title is still visible in Blizzard’s latest PC bug listings, which is enough to make it a live story worth watching rather than some made-up ghost report.

Even one report like this gets attention fast

There is a reason a thread title like that hits harder than a lot of other bug posts. Diablo can survive ugly UI. It can survive busted wardrobe menus. It can even survive the occasional loot container deciding to become decorative. Combat is different. The second players start feeling like enemies cannot be killed properly, everything else in the game becomes secondary because the basic contract stops working.

That is also why this story still has value even with the deleted thread caveat. The public details are limited, yes. But “monsters are actually not killable” is not some fuzzy theorycrafting argument over damage math. It is a direct, ugly gameplay failure if true, and those are the kinds of reports players instantly understand.

Diablo 4 has already trained players to expect friction

The timing does not help. We recently covered how players said Ashava’s world boss cache gave no loot, how Season 12 reward complaints were still hitting Bloodied boss loot, and how Flay was reportedly double-casting with WASD input. Different bug families, same overall problem: Diablo 4 keeps producing little moments where players stop trusting whether the game will behave normally from one system to the next.

That broader mood matters because it changes how people read fresh reports. In a cleaner week, a deleted one-post thread might just vanish into the forum swamp. In Diablo 4 right now, even a half-glimpsed combat bug can catch attention because players are already primed to believe the game is capable of something this dumb.

Right now, this one is real but still thin

To be fair, this is not a slam-dunk “major issue confirmed” story. The thread is gone, the author pulled it, and there are no public replies expanding on what zone, quest, or enemy type triggered the complaint. That uncertainty should stay in the article because it matters. But the topic is real, fresh, and visible in Blizzard’s current bug index, which makes it fair game as a watchlist story rather than a fully proven outbreak.

At this point, Diablo 4 does not just need fewer bugs. It needs fewer moments where even the basic act of killing monsters starts sounding negotiable.

Read More

Diablo 4 Players Say Season 12 Rewards Are Still Going Missing, and the Latest Complaint Hits Bloodied Boss Loot

 

Another fresh reward complaint has hit the forums, which is not exactly the kind of sentence Diablo 4 wants attached to Season 12 at this point. This time the issue is simple, ugly, and very easy to understand: a player says they killed a Bloodied Greater Lair Boss on Torment IV and did not get the reward they were supposed to get. No confusing tooltip. No weird edge-case interaction. Just kill boss, receive disappointment. ([us.forums.blizzard.com](https://us.forums.blizzard.com/en/d4/t/season-12-reward-bug/245250?utm_source=chatgpt.com))

The fresh report comes from a new thread on the official Diablo IV PC bug report forum, posted on April 17, 2026. The player says they defeated a Bloodied Greater Lair Boss in Season 12 on Torment IV and simply did not receive the rewards. That thread is now sitting alongside another live topic in Blizzard’s latest PC bug listings called “Season Journey Rewards Bugged”, which is not new by itself but does help show that reward friction is still hanging around the seasonal experience like a bad smell. ([us.forums.blizzard.com](https://us.forums.blizzard.com/en/d4/c/bug-report/7?utm_source=chatgpt.com))

This is not the same bug, but it rhymes with all the others

That distinction matters. The older Season Journey Rewards Bugged thread is more about a fake “reward available” prompt that will not go away. The new Season 12 reward bug complaint is more direct: the player did the activity, killed the boss, and says the rewards never showed up. Different bug, same family, same growing suspicion that Season 12 is still a little too comfortable messing with player rewards. ([us.forums.blizzard.com](https://us.forums.blizzard.com/en/d4/t/season-journey-rewards-bugged/241982?utm_source=chatgpt.com))

And that is what makes this story useful even if the thread is still small. Diablo players can live with stingy drops. They can live with long grinds. What they do not love is uncertainty over whether a boss reward is actually going to pay out at all. That turns the whole progression loop from harsh-but-fair into “maybe the machine just eats this one.”

Season 12 has already trained players to be suspicious

The bigger problem is that Diablo 4 has already burned through a lot of reward trust this season. We recently covered how players were still getting fake “Season Rank Rewards Available” notices, and how Band of First Breath was reportedly dropping like a cursed object. Those are not the same issue. But they absolutely help set the mood around a fresh report like this. When rewards disappear in Diablo 4 right now, players are not shocked. They are annoyed in a very practiced way.

Fresh report, familiar anxiety

To be fair, this is still one fresh public report, not proof of a giant widespread meltdown. Nobody should oversell that. But it is live, current, and attached to one of the most sensitive parts of any ARPG: the moment when a boss dies and the game is supposed to hand something back. If players start feeling unsure about that exchange, everything else gets uglier fast.

At this point, Diablo 4 does not just need rewards to exist. It needs players to believe the rewards will still be there after they do the work.

Read More

Diablo 4 Console Players Say Bloodied Magic Gear Is Not Counting

 

Diablo 4 has another one of those seasonal bugs that somehow manages to be both specific and incredibly annoying. This time the complaint is coming from console players, who say the game is failing to recognize a full set of Bloodied Magic gear for a Season Journey objective. In plain English: players are putting on the right blue gear, checking every slot, stripping transmogs, re-equipping everything like maniacs, and the game still acts like they showed up half-dressed. 

The current report comes from a fresh thread on the official Diablo IV Console Bug Report forum, where one Xbox player says Rank 2 will not complete even after equipping all the required Bloodied Magic gear. According to the post, they had already completed later ranks, but could not claim the completion rewards because Rank 2 remained stuck. That is the sort of season-progression nonsense that turns a checklist into a hostage situation. 

Players are already poking at the possible cause

One reply in the same thread suggests the issue may be tied to Spiritborn, because the class does not use an off-hand in the same way other classes do. If that theory is right, then this may not be a random “gear not detected” bug at all. It may be a class-specific requirement check that was never built properly for one of the game’s weapon setups. That would be a very Diablo 4 way for a seasonal objective to break: not spectacularly, just stupidly. 

And that matters because Season Journey bugs hit differently from ordinary combat bugs. A weird skill interaction is annoying. A progression objective failing to count when you did the thing correctly is worse, because it makes players feel like they are arguing with a spreadsheet that hates them personally.

Season 12 keeps tripping over the basics

This also fits a broader Season 12 pattern that is starting to feel less like bad luck and more like a design curse. We recently covered how players were getting fake “Season Rank Rewards Available” notices, and how Nightmare Keys were sometimes activating without clearly pointing to the dungeon. Different systems, same result: players are doing what the game asks, and the game is still finding ways to make basic progression feel weirdly unreliable.

Fresh bug, small thread, very real frustration

To be clear, this is a fresh console-side report, not a massive confirmed meltdown. Blizzard’s latest Console Bug Report listings show the thread active on April 15, and the discussion is still small. That means nobody should oversell it. But the complaint is live, specific, and easy to understand, which is exactly why it has legs. Seasonal objectives are supposed to be clean little dopamine dispensers. When one gets stuck because the game apparently cannot identify a full outfit, it stops being cute very quickly. 

At this point, Diablo 4 does not just need fewer bugs. It needs fewer moments where players do the homework correctly and still get told they failed the class.

Read More

Diablo 4 Players Say Nightmare Keys Are Not Pointing to Dungeons

 

Diablo 4 has a new little quality-of-life gremlin on the loose, and this one is less dramatic than a crash but somehow still deeply annoying. Players are reporting that some Nightmare Keys activate normally, then fail to point them toward the dungeon at all. No useful map guidance. No obvious active marker. Just you, your key, and a brief moment of wondering whether the game has decided to become mysterious for no reason.

The complaint comes from a fresh post on the official Diablo IV PC bug report forum, where one player says this is happening with some keys “like every 5th key this season.” According to the report, the Nightmare Key activates, but the game does not point to the dungeon and does not clearly show which dungeon is currently active. That turns a basic loop into dumb guesswork, which is exactly the sort of friction Diablo 4 really does not need more of right now.

It is not a big disaster, but it is exactly the kind of bug people remember

This is the sort of issue that looks small in a patch note and feels bigger when it hits real play. Nightmare Dungeons are not some obscure side activity. They are a normal part of the grind, and that means players expect the whole process to be brain-dead simple: use key, get marker, go kill things. When one of those steps disappears, the game starts wasting time in the most pointless way possible.

And wasted time is the real villain here. Diablo players can tolerate cruel loot, long grinds, and the occasional humiliating death. What they do not love is having the game turn navigation into paperwork. It is the same reason smaller Season 12 issues keep sticking in people’s memory. We recently covered how Diablo 4 players were getting fake reward notifications and how Barbarian players found Flay acting strangely with WASD. Different bugs, same general feeling: the game keeps tripping over things that should just work.

A blinking icon should not feel like a luxury request

What makes this report a little more interesting is that the player is not only flagging the bug. They are also asking for a cleaner fallback, like a blinking icon on the active dungeon. And honestly, that sounds less like a fancy feature request and more like common sense. If the game is going to build so much endgame flow around repeated key usage, it should be crystal clear which dungeon you have actually opened.

That is especially true in a season where players are already watching for systems that feel unreliable. A missing dungeon pointer is not the end of Sanctuary. But it is one more little cut, and Diablo 4 has collected enough of those lately that even the small ones stop feeling small.

Right now, it looks live and unresolved

As of now, the original Nightmare Key bug thread is still live, and the topic is also visible in Blizzard’s latest Diablo IV PC bug listings. That does not automatically mean a huge wave of players is hitting it, and nobody should oversell it. But it is fresh, it is real, and it lands in exactly the kind of routine gameplay loop where even one broken step gets old fast.

Diablo 4 can survive a lot. It probably should not be making players play detective just to figure out which dungeon they opened five seconds ago.

Read More

Diablo 4 on macOS via CrossOver Still Looks Broken After Season 12, and That Is a Pretty Miserable Place to Be

 

Diablo 4 has plenty of problems this season, but Mac players using CrossOver are dealing with a much meaner one than bad loot luck or another annoying UI gremlin. For some of them, the game simply launches into nothing. Battle.net says it is running, Activity Monitor shows the process chewing on CPU, and the actual game window never appears. That is not a rough session. That is a digital séance.

The core complaint is laid out in a still-active post on the official Diablo IV bug report forum, where a player says the issue started right after the Season 12 update. According to that report, the exact same CrossOver version, macOS version, and bottle setup had worked before patch 2.6.0, then suddenly stopped producing a visible game window after the update.

When “Running” does not mean running

That detail matters, because this does not sound like a vague compatibility complaint from someone trying to make unsupported hardware do circus tricks. The whole point of the bug report is that the setup was working, then Season 12 landed, and Diablo 4 basically turned into a ghost process. You click play, Battle.net insists everything is fine, and your desktop sits there like it has never heard of Sanctuary.

The issue also does not look buried. Blizzard’s latest Diablo IV PC bug listings still show the CrossOver Mac thread active on April 14, which is usually a decent sign that the problem has not simply evaporated. Over on the CodeWeavers support forums, players have been describing the same basic behavior: Diablo 4 says it is starting, then fails to open properly after the new season update.

There is at least one ugly workaround, and it is not exactly elegant

One particularly telling sign that this is not just user error is that some CrossOver users are already experimenting with ugly workaround territory. On the CodeWeavers compatibility forum, one player says they only got Diablo 4 to launch again by moving to a newer macOS beta and using a preview CrossOver build. That is less “fix” and more “ritual sacrifice with extra steps.”

For Mac players, that matters because CrossOver is already the compromise solution. People using it know they are not in the golden path Blizzard supports first. But there is still a big difference between “unsupported edge case” and “the game worked yesterday and now it opens into the void.” Season updates are supposed to break builds in-game, not erase the game window from reality.

The unsupported crowd still notices when things get worse

This is also one of those stories Blizzard can easily ignore because it sits in a niche lane. Diablo 4 on macOS through CrossOver is not the main player base. Nobody is pretending otherwise. But niche problems still matter when they are directly tied to a major patch and show up across both the official bug forum and the CrossOver community.

And honestly, Diablo 4 does not need more stories where players press play and get some fresh new variation of nothing. It already has enough of those.

Read More

Diablo 4 Players Say the “Season Rank Rewards Available” Notice Is Back, and It Leads to Absolutely Nothing

Diablo 4 has found yet another way to irritate people without even doing the courtesy of crashing first. A fresh round of player complaints is centered on the game showing a “Season Rank Rewards Available” notice even when there is apparently nothing left to claim. It is a small bug on paper, but in practice it feels like the UI is trolling you.

The main complaint comes from an active thread on the official Diablo IV bug report forum, where a player says the notification keeps appearing despite the reward screen being empty. That may sound minor, but in a seasonal loot game, false reward prompts are the sort of thing that get under people’s skin fast. When the game tells you loot is waiting and then opens an empty cupboard, players tend to notice.

Same reward anxiety, slightly different costume

What makes this one worth watching is not just the message itself. It is the timing. Diablo 4 has already had a rough stretch with reward-related complaints, missing items, and systems that look shakier than they should. That is why even a UI-facing issue like this lands harder than it normally would.

We just covered how Diablo 4 players say missing loot cases are piling up again, and that broader atmosphere matters here. This new complaint is not the same bug, and it would be lazy to pretend it is. But it feeds the same ugly suspicion: that Diablo 4’s reward systems are still not communicating clearly, and maybe not behaving consistently either.

The problem is trust, not just annoyance

That is the real issue. Seasonal systems are supposed to be clean and satisfying. You level up, you unlock a reward, you claim it, and your monkey brain gets the good chemicals. Instead, some players are getting a phantom notification that leads nowhere. That may be “just UI,” but repeated fake prompts start to erode trust in the whole progression loop.

And that is where Diablo 4 keeps stepping on the same rake. Players can handle grind. They can handle stingy drops. What they do not love is uncertainty over whether the game actually understands its own reward state.

No visible fix yet

As of now, Blizzard does not appear to have posted a visible resolution in the original forum thread. That does not prove a widespread disaster, and nobody should oversell it. But it does make the issue fair game, because the report is live, recent, and sitting in a season where reward confidence already feels a little bruised.

At this point, Diablo 4 does not just need fewer bugs. It needs fewer moments where the game looks players in the eye and confidently announces a prize that does not exist.

Read More

Diablo 4 Players Say The Butcher Can Still One-Shot Torment 3 Runs Even When You Do the Mechanic Right

Diablo 4 has a lot of bugs that feel cheap. This one feels personal. A fresh April 12 report says the Torment 3 Butcher fight is still killing players during the spinning-laser phase even when they move to the safe spots correctly. That is not just a hard boss. That is the game teaching you the mechanic, then deciding the lesson was optional.

The main complaint comes from a new post on Blizzard’s Diablo IV bug report forum, where the player says The Butcher enters the laser phase, they handle the safe movement correctly, and still get one-shot anyway. On the same Diablo IV forum index, two more same-day topics — “Butcher torment 3” and “Butcher torment 3 third time” — suggest the frustration escalated fast, even if it is not yet proof of a full-blown widespread outbreak.

This hits harder because The Butcher is basically Season 12’s mascot

That is what gives the story real weight. Blizzard’s official Season of Slaughter overview makes it clear that Butcher powers, Butcher progression, and Butcher-themed seasonal content are central to Season 12. So when the season’s signature fight starts killing players through what looks like the correct mechanic, it stops being some side-content annoyance and becomes a problem at the heart of the season.

That also fits with the wider Diabloz coverage around this update cycle. We already looked at how Butcher’s Brutality can break in your own world and work in someone else’s,  which means this is not even the first time Season 12’s Butcher systems have felt unstable. Different bug, same general smell.

Blizzard already fixed one invisible Butcher issue, which makes this worse

The awkward bit is that Blizzard’s March 20 Diablo IV patch notes already mention a fix for an invisible Butcher attack on low graphics settings. That is why this new report is interesting. If players are still getting deleted during the laser phase while saying nothing visibly hit them, then one of two things is happening: either this is a new version of the same basic problem, or the original fix did not fully bury the corpse.

There is also older forum smoke around this exact type of fight. In the Blizzard thread “The Butcher in the Broiler Visual Bug”,  players described missing beam visuals, unavoidable damage, and Torment 3 turning into an instant-death mess. That does not prove the April 12 report is identical, but it does make the whole thing feel less like a random one-off.

A mechanic check only works if the game respects the mechanic

That is really the issue. Diablo players can live with bosses being brutal. They can live with wipe mechanics. What they do not take well is a fight that appears to ignore its own rules. If the safe phase is not actually safe, then the problem is not balance. It is trust.

And trust is already a little thin in Season 12. Diabloz has been covering a steady pile of reward, progression, and system issues lately, from boss loot falling out of bounds during Lord Zir runs to better Aspect imprints failing to update gear properly. Against that backdrop, another Butcher fight complaint does not feel isolated. It feels like one more board coming loose in the same rotten floor.

Read More

Diablo 4 Players Say a Mythic Unique Cache Can Just Disappear After Crafting, Which Is About as Evil as It Sounds

Diablo 4 has plenty of annoying bugs. Some waste time. Some waste materials. This one goes straight for the throat. A fresh player report says a Mythic Unique Cache simply vanished after crafting, with the player losing two Resplendent Sparks and getting no item in return. That is not a minor inventory hiccup. That is the kind of bug that makes a season feel personally hostile.

The report was posted on Blizzard’s Diablo IV PC Bug Report forum on April 10. According to the player, the cache disappeared after crafting in Gea Kul, near the new seasonal area by Kael Rills the Butcher. They say they could still see it on the map, but it was not in their inventory, not in the stash, and not on the ground. In other words, the game seemed fully aware that the reward existed. It just apparently had no interest in letting the player actually touch it.

This is the kind of bug players remember

That matters because Mythic crafting is not cheap throwaway content. If a basic legendary vanishes, people groan and move on. If a Mythic Unique Cache disappears after consuming high-value crafting resources, the mood changes instantly. Blizzard’s Diablo IV forum indexes show the report as one of the newest active bug topics right now, which gives it enough heat to stand as a real current story and not just one lonely complaint buried three pages deep.

The awkward part: this may not be totally new

There is also some uncomfortable history here. An older EU forum thread from late December 2025 describes a Mythic Unique Cache disappearing from inventory after it was created and the player changed difficulty. A recent Reddit thread from last week also describes a player opening a Mythic cache and getting nothing, with one reply claiming certain town geometry can make loot disappear instead of dropping cleanly. That does not prove the current April 10 report is the exact same bug. But it does suggest cache-related vanishing acts may not be a one-night horror show.

When the reward system feels cursed, that is a real story

That is really the whole hook here. Diablo players can handle stingy drop rates. They can handle bad RNG. What they do not handle well is spending top-end resources and watching the payoff evaporate into UI smoke. Blizzard has not posted a public fix or explanation attached to this specific report yet. Until that changes, this is the kind of bug that will make every Mythic craft feel just a little more like a dare.

Read More

Diablo 4 Players Say Imprinting Better Aspects Still Isn’t Updating Gear to the Higher Value

Diablo 4 has a nasty little habit of turning upgrade moments into trust exercises, and the latest complaint fits that pattern perfectly. This time the issue is not that an Aspect looks wrong in the Codex. It is worse in a more practical, wallet-draining way: players say they are imprinting a better Aspect, spending the materials, and watching the item not actually update to the higher value. That is not a loot problem. That is an “are we sure the blacksmith is sober” problem.

The fresh report comes from Blizzard’s Diablo IV PC Bug Report forum on April 10. The player says that when they imprint an Aspect with higher values than the one currently on the equipped item, the game does not apply the new values. They also say it appears to happen when adding the Aspect to a rare item, and that they saw the behavior across multiple Aspects on a Barbarian. Blizzard’s current bug-board index shows the thread as one of the newest active Diablo IV bug topics today.

The annoying part is that this does not look brand new

That is what gives this one extra stink. Recent Diablo IV forum history shows Aspect-imprinting complaints have already been floating around for weeks. On March 25, one player said they were trying to overwrite an existing Aspect with a higher-value version and the sword would not upgrade to the stronger number. On March 14, another report said the problem happened specifically when trying to overwrite the same Aspect on an item that already had a lower-value imprint. There are also separate reports from March and April claiming imprint upgrades were landing at minimum values or throttled on lower-power gear.

Blizzard already patched one Aspect-value problem, which makes this harder to shrug off

That is the part Blizzard will not love. In the current official Diablo IV patch notes, Blizzard says it fixed an issue where values for Aspects were different between the Codex of Power and when imprinted or found on items. That sounds reassuring until a fresh April 10 report shows players are still talking about higher-value imprints not sticking properly. To be fair, this may not be the exact same bug under the hood. But from the player side, the feeling is basically identical: you earned the upgrade, you paid the cost, and your item still acts like it did not get the memo.

When upgrades stop feeling reliable, the whole system starts to smell off

That is why this matters. Diablo players can tolerate bad luck. What they hate is fake progress. If imprinting a stronger Aspect is still unreliable, then one of the game’s core upgrade loops starts feeling less like character building and more like a cursed coin flip with extra crafting fees attached. In a season already carrying a full backpack of bug reports, that is not exactly great timing.

Read More

Diablo 4 Players Say Butcher’s Brutality Can Break in Your World and Work Fine in Someone Else’s

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. 

Read More

Diablo 4 Players Say Season 12 Is Quietly Turning Valuable Reserve Sigils Into Generic Junk

Diablo 4 has a real talent for making loot feel cursed in ways Blizzard probably did not intend. The latest example is not some giant flashy crash or a boss exploding into the void. It is smaller, meaner, and somehow more annoying: players say valuable reserve sigils in Season 12 are being quietly converted into plain old “Gem reserves” by the game itself.

The fresh report on Blizzard’s Diablo IV PC Bug Report forum comes from a player running both Paladin and Barbarian in Season 12. According to the post, stash items with specific reserve affixes like Ruby, Emerald, Diamond, Topaz, and Sapphire were gradually changed into regular Gem reserve affixes after switching between characters. The player says those color-specific sigils matter this season, that the converted ones had been favorited, and that the bug effectively wiped out around 5 to 7 of the sigils they actually wanted to keep.

The ugly part is how easy this is to miss

That is what makes this one nasty. If a dungeon crashes, you notice. If a teleport black-screens, you notice. But if your stash slowly mutates your good sigils into generic filler, that can sit there like a quiet little scam until you finally realize your best stockpile has been spiritually mugged. Blizzard’s current PC bug board shows the report as one of today’s newest Diablo IV issues, which at least confirms this is part of the live Season 12 bug churn and not some ancient forum ghost resurfacing for attention.

It may not even be completely new

Here is the less comforting part: this does not look entirely unprecedented. An older Diablo IV PC bug-board page from January 3, 2026 shows a thread called “Gem Sigils converted over night.” That does not prove today’s report is the exact same bug with the same trigger, but it does suggest this family of problem may have been lurking around Sanctuary for a while instead of being a one-off seasonal freak accident.

A stash bug is still a progression bug

And that is the story here. This is not just about one mislabeled item. If players are holding specific reserve sigils because they are more useful or more valuable this season, and the game is flattening them into generic versions, then Blizzard is not just messing with inventory labels. It is messing with player planning, stash management, and the basic trust that the loot you saved yesterday will still be the loot you log in to tomorrow. In a game this obsessed with grind value, that is not a cosmetic problem. That is rot.

Read More

Diablo 4 Players Say the Wardrobe Is Still Bugging Out, and Somehow Even Dressing Up Has Become a Season 12 Problem

 

You can slay demons just fine. Picking a mount trophy? Apparently that is where the real challenge starts.

Diablo 4 has a fresh wardrobe complaint on the board, and it is exactly the kind of bug that sounds small until it starts wasting your time. In a new Blizzard forum report posted on April 8, one player says the wardrobe will let them interact with armor, but not with pets, mounts, mount armor, weapons, backpieces, or headstones. They also say armor only selects as a whole set, pigments behave the same way, and even a full reinstall did not fix it. The report is live in Blizzard’s Not able to select in the Wardrobe thread and also shows up among the newest items on the current PC Bug Report board.

This does not look like one completely isolated wardrobe tantrum

That is what makes it more than a one-post curiosity. A separate Blizzard thread from March 20, Wardrobe Bugged, describes a very similar problem: players saying clicked wardrobe pieces will not equip properly, that the interface can force the entire set instead of a single item, and that weird workarounds like pressing number keys or spacebar while clicking can sometimes make it respond. Blizzard’s latest topics pages also show related wardrobe complaints still surfacing this week, including “Wardrobe bug unable to select cosmetics” and “Issue with Wardrobe – Cannot interact (no response) – Diablo 4.” That does not prove every report is the exact same bug under the hood, but it does suggest the wardrobe has not exactly been living a stable life lately.

Why this bug is more annoying than it sounds

Because wardrobe bugs are not supposed to be hard problems. This is the cosmetic menu. This is where players go to make their character look slightly cooler, slightly uglier, or much more expensive than they need to. If the interface starts refusing normal selections and forcing whole sets instead, the system stops feeling polished and starts feeling like one of those menus you have to “fight” into working. And for Diablo 4, that lands badly in a season already carrying too many technical complaints at once. We have already covered how the black screen teleport bug still wasn’t dead, how rubberbanding was getting worse in Season 12, how PC crashes were still killing sessions, and how Season Journey Paragon Points were reportedly going missing Another bug hitting a basic system does not help the mood.

The funny part is that players are now troubleshooting a dress-up menu like it is a raid boss

That is the vibe here. Reinstalling the game to fix a cosmetic selector is already silly. Having older threads suggest keyboard tricks just to convince the wardrobe to equip the right piece is even sillier. Diablo 4 is very good at theatrical darkness, but it probably did not mean for the transmog screen to become part of the survival experience. Right now, this is still a fresh bug report rather than a full-scale community fire, but it is exactly the sort of issue that spreads fast once enough players realize the workaround is “start clicking weird and hope.”

Read More

Diablo 4 Players Say Season Journey Paragon Points Are Going Missing, and That Is a Nasty Bug to Find This Late in the Grind

 

Claim the reward. Watch nothing happen. Very cool.

Diablo 4 has a fresh progression complaint on the board, and this one hits a little harder than your average annoying UI wobble. In a new Blizzard forum post, a player says they completed the “Lesser Than Evil” objective under Season Journey Rank V, claimed the reward, saw it marked as claimed in the interface, and still never received the 4 Paragon Points tied to it. They say the objective was completed on April 6, but by April 8 the points still had not shown up. That is not a tiny visual bug. That is the game telling you “congratulations” and then quietly keeping the prize. Blizzard’s bug thread and the current PC Bug Report board both show the report as a fresh April 8 issue.

Why this one matters more than a random bug-board grumble

Paragon Points are not fluff. They are progression. If a seasonal reward says it gave you four and your account total does not move, players are not going to shrug and call it one of life’s mysteries. The original post also says the player suspects other rewards may not have credited correctly earlier, though that part is still one player’s suspicion rather than something Blizzard has publicly confirmed. That distinction matters. The evidence right now supports a real fresh player report, not yet a proven wider outbreak. Still, when the missing thing is permanent progression, people understandably get twitchy fast.

The ugly part is that this does not feel completely out of nowhere

This new complaint lands in a season that already has a bit of a rewards-trust problem. We recently covered how Season 12 rewards still weren’t paying out correctly, and older public chatter also suggests Season Journey reward weirdness has been floating around for a while. An Icy Veins report previously flagged claim issues around Season Journey rewards, and a Reddit thread from weeks earlier described a player getting fewer Paragon Points than expected from seasonal progression. None of that proves this new Rank V report is the exact same bug. It does suggest the broader reward flow has not exactly earned blind trust lately.

Right now, the real problem is confidence

That is the story more than anything else. Diablo 4 can survive balance drama, wardrobe bugs, and even the occasional cursed Occultist moment. But when players start wondering whether claimed progression rewards are actually real, the season starts feeling flimsy in a much less funny way. For now, this is still a fresh report and not a full community firestorm. But it is exactly the kind of bug that can go from “one bad post” to “everybody is checking their Paragon total” in a hurry. And honestly, once players start auditing the game’s math by hand, the mood has already gone bad.

Read More

Diablo 4 Players Say PC Crashes Are Still Killing Sessions Minutes After Login

 

If Season 12 wanted to add survival horror, crashing to desktop was a weird way to do it

Diablo 4 has another technical headache refusing to leave the room. In Blizzard’s PC Constant Crashing after a few minutes of play thread, players say the game is crashing just minutes into a session, sometimes hard enough to take the whole system down. The thread started on March 15, 2026, and it was still active on April 8, which is usually a bad sign in a game forum. Problems that disappear fast do not keep bubbling back to the top three weeks later.

What players are actually reporting

The core complaint is ugly, but very simple: launch the game, play for a few minutes, and then watch it fall over. The opening report lists a high-end PC with an RTX 5080 and says the whole system crashes after a short time in-game, while later replies describe continued crashing even after the usual cleanup routine of driver updates, reinstalls, and general PC troubleshooting. That is what gives the story some weight. This is not one person trying to run Diablo 4 on a haunted toaster from 2012.

Blizzard is at least asking for fresh crash logs

There is one useful development here. In an April 1 follow-up visible in the same discussion, Blizzard asked players to generate and send new FenrisDebug.txt files after the team enabled “a few things on our end.” That does not mean a fix is here. It does mean Blizzard appears to still be actively chasing the issue instead of pretending the thread is decorative. In practical terms, the game is still crashing, but support is clearly still collecting evidence.

Why this one matters

Crash bugs always matter a little more because they flatten everything else. It does not matter whether loot is good, builds are fun, or bosses are finally behaving if the client decides your run has lasted long enough. And for Diablo 4, this is landing in a season that already feels a bit too friendly with technical problems. We have already covered how Season 12 lag complaints were getting worse and how the black screen teleport bug still refused to die. Add repeat crashes on top of that, and the season starts to feel less cursed by demons than by QA debt.

Right now, the best headline is still “not fixed”

That is really the story. The crash thread is still surfacing in Diablo IV’s current technical support listings on April 8, which makes it fresh enough to matter and unresolved enough to be worth watching. Diablo 4 can survive balance arguments. It gets harder when simply staying logged in starts feeling like the real boss mechanic.

Read More

Diablo 4 Players Say Sigil Powder Is Vanishing at the Occultist, Which Is a Pretty Rude Trick for an Endgame Currency

 

Salvage the sigils. See the number pop. Get absolutely nothing. Cool.

Diablo 4 has a fresh little crafting headache on the board, and this one is the sort of bug that makes a basic endgame habit feel suspicious. In a new Blizzard forum report, a player says they salvaged around a dozen sigils at the Occultist in Kyovashad, saw “15” flash on screen, and then noticed their Sigil Powder stash had not gone up at all. They added that the test included both Nightmare and Boss sigils. If that report is accurate, the game is basically handing out fake receipts for salvage.

What the report actually says

The nice thing about this one, if “nice” is the word, is that the complaint is very easy to understand. This is not a thousand-word theorycraft post about edge-case math. It is one player saying they broke down sigils, the game visually suggested powder was awarded, and the stash total did not move. That kind of bug lands hard because it attacks a very ordinary loop. You clear content, junk what you do not need, and expect the leftover value to go somewhere useful. Instead, this sounds like Diablo 4 nodding politely and pocketing the change.

Why this one is worth watching already

On its own, one short bug thread would not normally be much of a story. The reason this works today is freshness. Blizzard’s PC Bug Report board and the game’s latest-topics page both surfaced “Sigil Powder not accumulating in stash” among the newest active April 8 topics, which is enough to make it current live chatter rather than some moldy forum fossil from three patches ago.

Another small bug in a season already collecting them

That is also why the timing matters. Season 12 already has the mood of a patch where players keep finding new ways for basic systems to wobble. We have already covered how lag complaints were getting hard to ignore and how some rewards still were not paying out correctly. This new Sigil Powder complaint is smaller than those, sure, but that almost makes it more annoying. Big bugs feel dramatic. Small economy bugs feel petty. And petty bugs have a special talent for sticking in people’s heads.

The real problem is trust in the loop

That is the whole issue in one sentence. If players cannot trust a routine salvage action to actually credit the material it says it credited, then one of the game’s dullest but most necessary endgame loops starts feeling dodgy. Nobody wants to wonder whether the Occultist is quietly skimming powder off the top like Sanctuary’s saddest little taxman. For now this is still an early report, not a full community meltdown. But it is exactly the kind of bug that can grow legs fast if more players start checking their stash totals a little more closely.

Read More

Diablo 4 Players Say the Rubberbanding Is Getting So Bad the Game Feels Like It’s Fighting Back

 

First it was lag. Now it feels like the game is actively arguing with your inputs.

A few days ago, we wrote about how Diablo 4 Season 12 lag complaints were getting hard to ignore. That story was mostly about ugly ping spikes and general instability. This newer wave feels worse. In Blizzard’s fresh Severe Lagging and Rubberbanding thread, players are not just talking about “bad connection” in the abstract. They are calling the game unplayable, describing constant freezing, and saying the usual fixes like reinstalling, lowering settings, and checking their internet are doing basically nothing.

What players are seeing now

The current complaints read less like a normal server wobble and more like the game briefly forgetting how time works. In the new PC bug thread, the original poster says they made yet another thread because Blizzard had not acknowledged the others, while a reply says the game freezes “every other second” and makes even the opening quests feel miserable. That lines up with Blizzard’s PC Bug Report board, where the thread was still active on April 7.

And it is not staying neatly on one platform either. In a recent console discussion thread about rubberbanding and lag, one PS5 player said a Pit boss took 30 seconds to spawn, inputs froze for 10 to 15 seconds, and Infernal Hordes became a total mess with deaths landing after the screen effectively stopped making sense. Another player said the issue started after the last patch and persists even after router resets and other troubleshooting. That is not “a little stutter.” That is Diablo 4 turning combat into interpretive dance.

Why this matters more than one more angry forum thread

Because this is how a bad season mood turns into a bad season reputation. Diablo 4 can survive people arguing about tuning. It can survive one annoying quest bug. It gets harder to shrug off when the basic act of moving, fighting, and loading into content starts feeling unreliable. And that is on top of other Season 12 headaches we have already covered, like reward issues still not paying out correctly. At some point, the season stops feeling rough around the edges and starts feeling cursed in a much less fun way.

Right now, players mostly want Blizzard to get in the room

That may be the real story here. The technical and bug-report boards still show multiple active latency, freezing, and rubberbanding threads, including High latency, EU, 260 - 500ms, after last patch? and the newer severe-rubberbanding report. Players are clearly past the “maybe it’s just me” stage. They want Blizzard to either explain what is happening or fix it before Season 12 becomes the patch people remember for fighting the servers more than the demons.

Read More

Diablo 4 Players Say Season 12 Lag Complaints Are Still Getting Hard to Ignore

 

The bugs may rotate, but the latency threads are not going away

Diablo 4’s Season 12 lag problem is still hanging around, and at this point it is getting harder to write off as a few isolated bad sessions. Blizzard’s own Diablo IV forum pages still show active April 4 threads for “High latency, EU, 260 - 500ms, after last patch?”, “Intermittent High Latency,” and the still-active “Extreme lag and instability season 12” report. That does not automatically prove one single root cause, but it does show the same basic complaint is alive across both Technical Support and bug-report categories right now.

What players are reporting

The most specific current thread is the EU latency one. There, players say ping has been jumping into the 260 to 500 ms range after the recent patch, with one April 2 reply saying cross-play helped only “a bit in the fields” while lag and disconnects were still happening regularly. That is not subtle stutter-talk. That is the kind of latency where the game starts feeling like it is making combat decisions three seconds after you did.

And it is not just one thread sitting there unloved. Blizzard’s Diablo IV latest-topics page still shows Intermittent High Latency, the EU high-latency thread, and Extreme lag and instability season 12 all surfacing together on April 4. When multiple lag threads keep floating to the top at once, it usually means the issue is not fully dying in the background. It means players are still running into it often enough to keep feeding the fire.

Why this matters more than a random support complaint

Normally, one technical-support post is not much of a story. But recurring latency complaints hit differently in Diablo 4 because this is a game built around timing, movement, positioning, burst damage, and not getting flattened while your screen lies to you. If the connection goes bad, the whole game gets stupid fast. Dodges come late. Skills feel delayed. Enemies appear where they were not a moment ago. And suddenly the real boss fight is the route between you and Blizzard’s server. That is not a fun surprise in any ARPG, let alone one that keeps asking players to push harder seasonal content.

Blizzard’s patch notes do not offer much comfort here

That is part of why the complaints still land. Blizzard’s current Diablo IV patch-note entry for 2.6.1 is packed with Season of Slaughter fixes, reward fixes, and gameplay adjustments, but there is no obvious broad latency or server-performance fix called out there. That does not prove Blizzard is doing nothing behind the scenes, but it does mean players looking for a neat public explanation are not finding one in the official notes.

When the season’s hardest mechanic is packet travel

Maybe Blizzard gets this under control quietly. Maybe it is more regional than global. Maybe it is one of those ugly post-patch connection spells that clears up after a few days. But right now, the forum pattern is clear enough to say this much: Season 12’s lag complaints are not gone, and players are still talking about them like a real part of the game experience. In Diablo terms, that is a bad sign. Nobody wants their strongest seasonal enemy to be latency spikes with a decent internet plan. 

Read More

Diablo 4 Players Say the Wardrobe Is Just Not Working

 

Sanctuary has many horrors. Your closet should not be one of them.

Diablo 4 players have found a new bug to trip over, and this one is not exactly endgame-defining. It is just deeply annoying in a very live-service sort of way. A fresh April 4 bug report on Blizzard’s Diablo IV forums says the Wardrobe can become completely unresponsive, with no popup, no error, and no visible reaction whether the player clicks the Wardrobe NPC or the wardrobe icon from the inventory menu.

That might sound minor next to all the usual Diablo drama about loot, balance, or broken seasonal systems. But cosmetic systems matter more than game forums like to admit. If players are spending time collecting transmogs, pets, and outfits, then the basic expectation is simple: the part of the game meant to show them off should at least open.

What players are reporting

The current report is extremely straightforward. The player says the Wardrobe gives “absolutely nothing” back when interacted with. No error message. No UI window. No response at all. They also note that the issue happens both through the actual Wardrobe interaction point and through the icon inside the inventory, which makes it feel less like one broken NPC and more like the entire feature deciding to clock out for the day.

This is not buried in some ancient dead forum either. Blizzard’s current Diablo IV bug-report index shows “Issue with Wardrobe – Cannot interact (no response)” among the active April 4 topics, and the main latest-topics feed also surfaced it the same day. So even if it is not yet a giant multi-page disaster thread, it is fresh enough to count as live bug chatter, not archaeology.

Why this one is worth covering

Wardrobe bugs are not exactly new in Diablo 4. Blizzard’s forums also contain older reports from 2024 and March 2026 describing wardrobe and transmog problems on PC and Steam, including broken saves, cosmetics not sticking, and the feature failing to work properly after returning to the game. That does not prove today’s issue is the exact same bug, but it does suggest the Wardrobe has a bit of history when it comes to behaving like a cursed piece of furniture.

And that is what makes this more than a throwaway complaint. Diablo 4 already asks players to engage with cosmetics, mounts, pets, and premium looks as part of the broader live-service loop. When the styling room itself stops responding, it makes the whole system feel flimsier than it should. Nobody wants the real final boss of fashion to be a dead button.

A small bug that still makes the game feel cheap

Maybe Blizzard fixes this quickly and it disappears without much fuss. That would be ideal. But right now, the Wardrobe issue lands in that especially irritating category of bug where nothing explodes, nothing crashes, and yet the game still manages to feel broken in a way players notice instantly. In a loot game built partly on looking cool, a closet that will not open is not just cosmetic. It is a tiny quality-of-life failure wearing a very visible hat. 

Read More

Diablo 4 Players Say a Mythic Goblin Bug Can Turn a Rare Key Into Nothing

 

A rare dungeon reward is getting attention for the worst possible reason

Diablo 4 players are flagging a new frustration around the Mythic Prankster dungeon setup: a fresh April 3 bug report says a player used their first-ever Mythic Prankster key, found the goblin inside, and then watched it become effectively untouchable before it vanished, taking the reward with it. The forum post describes the goblin as taking no damage at all for a few seconds and then disappearing, leaving the player with no mythic payout and no key.

That is a nasty little bug story because the hook is brutally simple. This is not some common overworld goblin that slipped away in the usual chaos. It is tied to a rarer key-based reward setup, which means the failure feels more expensive the moment it happens. And since Blizzard’s own current Diablo IV patch notes already reference the Mythic Prankster Nightmare Dungeon reward pool, the feature itself is clearly live and relevant in the current season.

What the forum thread actually says

The original report is short, but specific. The player says they located the goblin in the dungeon, tried to kill it, and found that it could not be damaged before it disappeared. They also say this was their first mythic key of this type and asked for the key to be refunded. That part matters, because it frames the issue less as “annoying goblin behavior” and more as “rare seasonal reward consumed, nothing meaningful returned.”

There is an immediate wrinkle, though. A reply in the same thread argues this may not be a literal invulnerability bug at all. According to that response, if a goblin has already been spooked and started its escape sequence, it can remain visible for a few more seconds while no longer being damageable. In that interpretation, the player may have reached the goblin too late rather than hitting a broken enemy state. That does not make the experience feel any better, but it does mean the current evidence points to two possible readings: real bug, or badly communicated goblin escape behavior.

Why this still feels like a real story

Even with that caveat, the story works because the result is the same from the player side: a rare key was spent, the goblin could not be killed when it mattered, and the reward window slammed shut. Blizzard’s forum indexes show the thread surfacing among fresh Diablo IV bug reports on April 3, which at minimum tells you the complaint is current enough to be part of the live season’s bug chatter.

And that lands awkwardly against Blizzard’s broader Season 12 tuning. In the official Diablo IV patch notes, Blizzard already reduced Mythic Prankster Nightmare Dungeon rewards from five Mythic Uniques to one, which means the whole activity has already become less generous than before. So if players now feel they can also lose the run entirely to goblin behavior they cannot clearly read in the moment, the feature starts looking less like a jackpot and more like a slot machine with an attitude problem.

A rare reward should not end with “maybe you were too late”

That is really the issue here. Maybe this turns out to be a misunderstood escape timer rather than a true invulnerability bug. Fine. But then the design still failed in another way, because a player spent a rare key and came away thinking the encounter was broken. In a loot game, that distinction matters less than developers sometimes think. If the goblin is technically working while still feeling completely wrong, players are not going to send thank-you cards to the tooltip team. 

Read More