Diablo Immortal Players Say Some Shop Bundles Broke After Patch

 

Diablo Immortal has wandered back into one of its favorite little disaster zones: the shop. Fresh player reports say that after the latest patch, some in-game bundles simply stopped working at checkout. The offer appears, the button responds, the game says “Processing please wait”, and then absolutely nothing useful happens. No purchase window. No bundle. No resolution. Just a live-service shrug in premium currency form. 

The clearest new complaint comes from a fresh thread on the official Diablo Immortal bug report forum, where one player says that after the patch they could no longer buy bundles like Login Boon and Gemseeker’s Chest. According to the report, other purchases such as Magnate’s Supplies still worked, which makes this look less like a total store outage and more like a selective shop failure tied to specific bundles. The player also says they tried multiple devices with the same result, which is never the kind of sentence you want attached to a monetized system.

Not every shop bug is the same bug, but players stop caring fast

That last part matters. Diablo Immortal players do not experience these problems as neat little categories. They just see another moment where money, rewards, or store items go sideways and the game starts looking like it cannot be trusted around transactions. That is why even a “specific bundles only” problem lands badly. Premium systems do not get much grace when they fail in public. 

And yes, this is also hitting a game that already has shop baggage. We recently covered how Diablo Immortal’s shop loading bug had been hanging around long enough to feel absurd, and how players were raising fresh progression alarms around Leviathan Surge. This new bundle issue is not the same story, and it should not be lazily mashed together with those. But it absolutely feeds the same mood: when the game touches transactions or progression, players are bracing for impact. 

There is also a bigger trust problem floating nearby

This is where the timing gets ugly. Just a day earlier, another Diablo Immortal forum post described a Battle.net bundle purchase that allegedly never delivered the promised Wayfarer bundles. Earlier in April, another player reported that a Rift Delver’s Hoard purchase was claimed in-game but never arrived. Different platforms, different details, same general smell. Players do not need every report to be identical before they start thinking the paid side of the game looks a little cursed. 

Fresh report, small thread, very familiar headache

To be clear, this is still a fresh bug thread, not proof that half the shop has exploded. Blizzard’s latest Diablo Immortal bug listings show the topic live today, and the current public evidence is still limited. But it is current, specific, and painfully easy to understand. A patch goes live, some bundles stop opening the payment flow, and players are left poking at a dead checkout prompt like villagers discovering a cursed relic. That is enough for a story, especially in a game where shop reliability is already on trial.

At this point, Diablo Immortal does not just need new content. It needs one quiet week where players are not wondering whether the game can safely handle a button tied to money.

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 Players Say Flay Can Double-Cast With WASD

 

Diablo 4 players have found another one of those bugs that sounds small until you imagine it happening inside an actual build. This time the complaint is about Flay, with players saying the skill can sometimes fire twice from a single input when using WASD movement. That is not just a weird animation hiccup. If true, it means a core attack is behaving inconsistently depending on how the player is moving, which is exactly the kind of thing that makes combat feel slippery in all the wrong ways.

The current report sits in a still-visible thread on the official Diablo IV PC bug report forum, where the original poster says Flay will occasionally attack twice off one click while using WASD movement and certain mouse positioning. They also note that Rend can show similar behavior, and that this is happening without the relevant “hit twice” temper being slotted. In other words, players are not describing a build doing what it is supposed to do. They are describing the game freelancing.

One extra swing sounds great right up until it is not

On paper, some people will look at this and say, “Well, free extra attack, what is the problem?” The problem is that bugs like this never stay cute for long. Once a skill starts duplicating inconsistently, you are suddenly in the murky swamp between broken damage, broken resource flow, and completely unreliable feel. A bug that helps one second can sabotage testing, build consistency, and player trust the next.

That is especially true for Barbarian players, because if there is one group in Diablo 4 that tends to notice when basic combat inputs start acting weird, it is the people counting every hit, stack, bleed tick, and timing window like their mortgage depends on it.

WASD is supposed to make combat cleaner, not stranger

Part of what makes this one interesting is the input angle. Diablo 4’s WASD movement is supposed to make the game feel tighter and more responsive for players who prefer direct control. If it is instead creating edge-case behavior where attacks can duplicate under certain input combinations, that is not some harmless little side effect. That is the sort of thing that makes players start wondering which parts of their build are real and which parts are held together by input spaghetti.

We have already covered how Diablo 4 players are dealing with another fake reward notification problem and how Mac players using CrossOver are getting a launch-to-nowhere experience. This Flay issue is a different beast, but it fits the same broader pattern: Season 12 keeps finding new little ways to make the game feel less dependable than it should.

The bigger problem is combat trust

That is what makes bugs like this more serious than they first appear. Diablo 4 can survive a messy tooltip. It can survive a dumb UI prompt. Combat bugs are trickier, because they attack the one thing the game really cannot afford to make slippery: whether your character is actually doing what you told it to do.

As of now, the original bug thread is still up and the topic is also visible in Blizzard’s latest PC bug listings. That does not prove some massive Barbarian crisis. But it does make this a fair live issue to watch, especially if more players start confirming the same behavior. Because once a basic attack starts feeling haunted, people tend to remember it.

Read More

Diablo Immortal Wizard Players Say the Class Is Breaking

 

Wizard players in Diablo Immortal are having one of those weeks where every new thread feels like a fresh little insult. First came the backlash over the Wizard mobility change tied to Terminus Facade. Now the mood has shifted from “this feels worse” to “is the class actually breaking in multiple places?” New forum posts are piling up around reduced Disintegrate range, broken essence interactions, and fresh complaints that some boss fights now feel flat-out miserable on Wizard. :contentReference[oaicite:0]{index=0}

The sharpest new complaint comes from a fresh bug report on Blizzard’s Diablo Immortal forum, where a player says Disintegrate’s range feels massively reduced after recent changes. They specifically mention no longer being able to refract the beam properly on certain dungeon bosses because they have to stand too close, which in practice means getting punished harder and dying more often. That is not just a balance gripe. That is a class-feel problem, and players usually notice those faster than almost anything else. :contentReference[oaicite:1]{index=1}

It is not just one thing anymore

That would already be enough for a decent frustration story, but Wizard players are not stopping there. Another new bug thread says the Mask of Many essence is not working properly, with one player reporting that the supposed instant full-charge behavior does not correctly apply to Meteor when paired with Binding Forces. Then a separate follow-up post, Wizard bug after essence change, claims the recent changes now stop Wizards from using Ice Crystal and Disintegrate properly against certain bosses, including Pit of Anguish’s last boss and ledge-style encounters. :contentReference[oaicite:2]{index=2}

That combination matters. One awkward change can be debated. A cluster of fresh complaints touching range, essence behavior, and encounter usability starts to look less like whining and more like a class going through a rough patch in public.

Wizard players are hearing the same bad song again

The wider context makes the reaction louder too. Blizzard’s own latest Diablo Immortal bug listings show both the Disintegrate and essence reports surfacing together on April 15, while the broader forum feed also shows the still-active discussion around Terminus Facade’s speed boost removal and another complaint that Binding Force Meteor now feels clunky and unusable. That is a lot of smoke around one class in a very short window. :contentReference[oaicite:3]{index=3}

It also lands in a game that was already fighting for patience. We have already covered how Diablo Immortal’s Battlegrounds refresh is trying to calm PvP nerves, and how players are raising fresh progression alarms over Leviathan Surge. Against that backdrop, Wizard players are not exactly in a forgiving mood.

Fun is still the first stat people notice

Maybe Blizzard sees some of this as tuning. Maybe some of it really is bug-related collateral damage. But from the player side, that distinction only goes so far. If your class suddenly has less range, worse flow, broken essence interactions, and more annoying boss encounters, the experience is simple: the class feels worse than it did a few days ago.

And that is the danger here. A live-service class does not need to be mathematically dead to start feeling dead. It just needs enough friction piled on fast enough that players stop trusting it. Right now, that looks uncomfortably close to where Wizard is headed. :contentReference[oaicite:4]{index=4}

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 Immortal Players Say Leviathan Surge Just Ate 9,000 Sigils and Gave Nothing Back

 

Diablo Immortal has a special talent for making expensive progression feel like a magic trick gone wrong. The latest complaint is a nasty one: a player says Leviathan Surge consumed 9,000 sigils during an upgrade attempt and then failed to upgrade the gem at all. The sigils vanished. The upgrade did not happen. That is not a small annoyance. That is the sort of thing that makes people stare at the screen in silence for a full ten seconds before the swearing starts.

The report comes from a fresh post on the official Diablo Immortal bug report forum, where the player says they tried to upgrade a four-star Leviathan gem to five stars using 9,000 accumulated sigils, only for the game to take the currency and leave the gem unchanged. On its own, one report does not prove a widespread system meltdown. But in Diablo Immortal, when progression currency disappears into the void, people tend to assume the worst for a reason.

This is the kind of bug players do not shrug off

There are plenty of bugs players can laugh off. A weird animation. A menu hiccup. A bit of UI acting possessed. This is not one of those. Currency-linked upgrade systems sit way too close to time, grind, and in some cases real money for players to be casual about them. When something in that chain breaks, the mood turns ugly fast.

And Leviathan Surge was already carrying baggage. Players were recently arguing over its drop behavior in community discussion, with some questioning whether the experience actually matched expectations around the event. That means this new complaint lands in territory that was already a little radioactive before the 9,000-sigil horror story showed up.

Diablo Immortal keeps wandering back into the same swamp

That is the broader problem here. Diablo Immortal does not just get judged on isolated bugs anymore. It gets judged on pattern recognition. Players have seen too many stories where something tied to progression, rewards, or premium-adjacent systems feels off, unclear, or painfully slow to resolve.

We have already covered how the shop loading bug has overstayed its welcome and how Blizzard is trying a much bigger Battlegrounds refresh. Those are different stories. But they feed the same general mood around the game: players are still willing to log in, but they are much less willing to blindly trust systems that touch progression.

No fix yet, and that is where the tension starts

As of now, the original bug report thread is live, and there is no visible public fix attached to it yet. Maybe it is a one-off failure. Maybe it is something Blizzard can restore cleanly. But until that happens, this is exactly the kind of report that spreads because it hits a nerve players already have.

In a game like Diablo Immortal, people can tolerate grind. They can even tolerate greed, up to a point. What they do not tolerate well is the feeling that a hard-earned pile of upgrade currency can simply fall into a crack in the floor while the game shrugs and moves on.

Read More

Diablo Immortal Players Are Already Furious About a Wizard Mobility Change, and Honestly It Is Not Hard to See Why

 

For once, Diablo Immortal players are not mainly yelling about crashes, disappearing menus, or the shop falling through the floor. This time the heat is on class feel, and the target is Wizard. More specifically, players are arguing over the apparent removal of the speed boost tied to the Terminus Facade essence, and they are not reacting like this is some harmless little tuning pass.

The spark comes from a fresh thread on the official Diablo Immortal forums, where one player argues that removing the movement boost guts both the fun and the viability of the setup. A matching Reddit discussion is carrying the same mood: less speed, less flow, less reason to keep playing Wizard the same way.

Not every nerf is just numbers on a spreadsheet

That is the real hook here. Players can live with damage nerfs. They can even survive the usual live-service ritual where something fun quietly gets dragged into a back alley and rebalanced. What they do not take lightly is when a class suddenly feels worse to move, worse to route, and worse to enjoy moment to moment.

And that is what makes this more interesting than a simple balance footnote. If the speed boost really is being stripped out of the Terminus Facade setup, players are not just losing power. They are losing rhythm. In an action RPG, that matters a lot more than some developers seem to think. A build can survive lower numbers. It is much harder to survive feeling clunky.

Wizard players are hearing a familiar Blizzard sound

The tone of the backlash is also revealing. A lot of the frustration is not really about one essence in isolation. It is about the old Blizzard problem of taking a setup people actually enjoy and “fixing” it in a way that makes the game feel flatter. That does not always kill a class, but it can absolutely make people stop loving it.

It also lands at a time when Diablo Immortal has already been in one of those classic messy stretches where the conversation keeps drifting back to system friction and player trust. We recently covered how Blizzard is reshaping Battlegrounds with a much bigger PvP refresh, and how the shop loading bug has been hanging around far too long. Against that backdrop, even a class-mobility change starts feeling less like isolated tuning and more like another reason for players to stay annoyed.

Fun is the stat players notice first

Maybe Blizzard sees this as a reasonable correction. Maybe it is one. But players almost never experience these things as clean design philosophy. They experience them in the gut. If a build suddenly feels slower, stiffer, or more annoying to pilot, the spreadsheet explanation does not save it.

That is why this story has legs. It is not just about Wizard balance. It is about whether Diablo Immortal is once again shaving off the part of a class that made people actually want to log in. And in a game built on repetition, fun is not some bonus stat. Fun is the whole engine.

Right now, the argument is only getting louder

As of now, the forum thread is still live, the Reddit discussion is active, and there is no visible Blizzard response attached to the complaint yet. That does not automatically mean the sky is falling. It does mean Wizard players think something that felt good has been made worse, and they are making that point with the usual subtlety of a hammer through stained glass.

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 Immortal’s In-Game Shop Hasn’t Worked for Some Players in Over a Month, and That Is a Very Blizzard Problem to Have

Diablo Immortal has spent the last stretch trying to keep players interested with events, rewards, and shiny little retention hooks. So there is something almost darkly funny about one of the game’s freshest complaints being this: some players say the in-game shop still doesn’t work at all, and for a few of them, it apparently has not worked for weeks. In a live-service game built to sell convenience, cosmetics, and battle pass upgrades, that is not just a bug. That is the cash register coughing blood.

The strongest thread right now is Blizzard’s official bug report post titled “The in-game Shop hasn’t worked for over a month, cannot purchase anything.” The original poster says the shop on their main account gets stuck on “Loading…” and then throws Error Code: 0 after around 45 seconds, while a second account on the same machine, same network, and same client loads the shop normally. A Blizzard forum MVP reply in that thread says it is a known issue, which is the kind of sentence that sounds reassuring right up until you notice players were still replying weeks later saying it remained broken for them.

And that is where the story gets uglier. A separate technical support thread, “Cannot access in game store,” goes back to February 10 and shows multiple players reporting the same basic failure: the store will not open, daily boons cannot be collected, battle pass purchases are blocked, and in one April 9 reply a player even says they could not retrieve rewards or outfits they had already paid for. That does not automatically prove every report shares the exact same backend cause. It does show this problem is not some one-day shop wobble that quietly fixed itself.

That timing also makes Blizzard look a little silly. Diabloz just covered how Diablo Immortal’s New Refined Battle Pass Push Looks Smart, and The Hells Quake Is Blizzard’s Little “Don’t Drift Away” Bonus, while Diablo Immortal’s Winds of Fortune Is Back on April 9, and Yes, This Is the Week to Farm Like a Maniac framed the current update cycle as Blizzard trying to keep players engaged with cleaner reward incentives. That is all well and good. But if part of the audience cannot reliably open the in-game shop at all, then the game’s monetization layer starts looking less like a polished machine and more like a haunted vending machine in Westmarch.

Blizzard has not posted a visible full fix in the source threads checked here. So the careful version is still this: these are active player reports, not proof the entire shop is down for everyone. But when a “known issue” hangs around long enough for players to start joking that Blizzard apparently does not want their money, that stops being a tiny support annoyance. It becomes one of those bugs that makes the whole game feel a little less under control than it should.

Read More

Diablo II: Resurrected’s Warlock Nerf Debate Is Starting to Turn Into a Casual-Player Problem

Yesterday’s D2R story was about backlash. Today’s version is a little more interesting, because the argument is shifting. This is no longer just hardcore players yelling about balance philosophy and busted metas. A growing chunk of the forum debate is now about whether Blizzard’s Warlock changes are about to suck the fun out of the class for the people who were supposed to love it most: regular players with limited time, limited gear, and limited patience.

The center of that discussion is the Blizzard forum thread “Warlock nerf demotivates casual players, which was posted on April 13 and is still active today. The thread itself is not even cleanly anti-nerf, which is what makes it such a good read on the current mood. Some players argue Warlock should not be nerfed because casuals finally had a class that felt powerful without absurd investment. Others argue the exact opposite: that Warlock is so overtuned it actually ruins progression and makes the game boring, even for casuals. In other words, Blizzard has managed to land on the most Diablo problem possible — a class that feels empowering to one group and game-killing to another.

That debate only makes sense in the context of the actual PTR 3.2 notes. Blizzard is not making one tiny adjustment here. It is hitting multiple Warlock tools at once, including Miasma Bolt, Miasma Chains, Ring of Fire, Flame Wave, Echoing Strike, and the class’s one-hand-two-hand weapon interaction, while also reworking Herald and Latent Sunder Charm behavior. If you liked Warlock because it felt like a fast-track power fantasy, PTR 3.2 looks like Blizzard showed up with a bucket of cold water.

The reason this follow-up matters is that the forum front page now shows several parallel threads pushing the same underlying anxiety from different angles, including “The best way is to strengthen other chars, not weaken warlock” “I , Have 2x 99 Warlocks... And I STILL Want the Nerf”, and a broader stream of PTR 3.2 arguments still crowding the active D2R discussion list. That is a sign Blizzard is no longer dealing with one angry thread. It is dealing with a class-identity fight.

Diabloz already covered the first wave in our PTR 3.2 breakdown and the initial Warlock backlash piece. What feels new now is the tone: less “you nerfed my broken build” and more “you sold me a fun class, and now you’re deciding what kind of fun is allowed.” That is a much harder complaint for Blizzard to shrug off, because it hits the paid-expansion fantasy right in the throat.

Read More

Diablo 4 Players Say Missing Loot Cases Are Piling Up Again, and That Is a Rotten Trend

Diablo 4’s reward bugs are starting to build a nasty little pattern. One missing item is a headache. Two fresh missing-loot reports in barely a day starts to feel like the game’s reward system is wandering around Sanctuary with its pockets turned inside out. The latest cases are not identical, but they rhyme in exactly the wrong way: players say high-value rewards are disappearing, and they are already asking Blizzard for help getting them back.

Two fresh reports, same ugly feeling

The first is a new Blizzard forum thread called Missing loot season of slaughter, posted on April 13. The player says seasonal loot from tiers V and VI in Season of Slaughter simply disappears when they try to open the chest and collect the contents. The second is an April 14 console bug report titled Item Restoration Request - Missing "Heir of Perdition" due to Error Code 395002, where the player says a synchronization issue after Error Code 395002 left them missing a specific item from inventory. Blizzard’s current PC and console bug indexes both show these as live recent topics, which is enough to make this more than one random sob story.

This is becoming a trust issue, not just a loot issue

That is why the story has teeth. Diablo players can survive stingy drops. They can survive rough RNG. What they do not take well is the game acting like a reward existed five seconds ago and then politely refusing to produce it. And Diabloz has already been covering that exact mood lately, from Mythic Unique caches disappearing after crafting to Greater Bloodied Caches vanishing before a crash. This latest pair of reports is not the same bug, but it absolutely feeds the same suspicion: rewards in Diablo 4 are starting to feel less secure than they should.

Blizzard does not need a confirmed disaster to have a problem

To be clear, this is not proof of a massive account-wide loot-loss crisis. These are still fresh player reports, not a Blizzard-confirmed widespread incident. But that distinction only carries you so far when the public-facing forum pages are stacking multiple missing-item threads in the same window. Once players start talking about item restoration instead of just bad luck, the tone changes fast. At that point, the grind is no longer frustrating. It is suspect.

When “did it drop?” becomes “did the game eat it?”

That is the real damage here. Diablo 4 is supposed to make players obsess over loot quality, not loot existence. If Blizzard wants people focused on Season 12’s actual content instead of wondering whether their next reward will evaporate into technical smoke, it probably needs to get ahead of this kind of report before “missing loot” becomes the game’s most reliable drop.

Read More

Diablo 4 Players Say Crafted Mythic Uniques Are Coming Out Non-Ancestral, Which Kinda Defeats the Point

Diablo 4’s top-end item grind has developed a nasty habit lately: the more expensive the reward loop gets, the less trustworthy it feels. The latest example is an active Blizzard forum thread titled Crafted Mythic Unique is Non Ancestral, where players say Mythic items created through crafting are showing up as regular Mythic Unique items at item level 800 with one Greater Affix, instead of counting as Ancestral Mythic Unique items the way they expected. The original report says this is also blocking progress on the Season Journey objective “Fabled Power.”

That is a pretty ugly bug to have attached to one of the game’s most expensive reward paths. In the original thread, the first player says they crafted two Shroud of False Deaths and both came out wrong, while later replies say the same thing happened with Heir of Perdition and additional Shroud crafts. So this is not just one player screaming into the void after a bad roll. It is a small but very real pile of people all describing the same kind of top-end crafting failure.

It is not brand new, but it is very much still alive

This is where the story gets interesting. The actual thread started on March 22, 2026, so this is not some surprise bug that appeared out of nowhere this morning. But Blizzard’s current Diablo IV PC Bug Report index and broader latest topics page both still show Crafted Mythic Unique is Non Ancestral among the active current bug discussions on April 14, which tells you players are still hitting it or at least still pushing it back into view. That makes it less of a one-day complaint and more of an unresolved irritation that keeps refusing to stay buried.

This also fits Diablo 4’s current reward-trust problem a little too well

That is probably why the story lands so easily. Diabloz has already covered how a Mythic Unique Cache could disappear after crafting, and how 19 Greater Bloodied Caches allegedly vanished before a crash. Different bug, different failure point, same basic rotten feeling: players are putting serious resources into reward systems and getting back something unreliable, incomplete, or just gone. That is not great in any loot game. In Diablo, it is basically sacrilege.

The real problem is not just the item level

Because this is not only about whether a crafted Mythic should have a different label. The original post explicitly says the bug is also preventing Season Journey credit for Fabled Power, which means the problem bleeds into progression tracking too. Once a bug starts messing with both item quality and seasonal progress, it stops feeling like a weird display issue and starts feeling like the game’s reward logic is drunk.

Expensive crafting should not feel like a gamble on whether the game understands its own rules

Blizzard has not posted a visible public fix on the thread from the sources checked here. So the careful framing is still this: it is an active player-reported issue, not a Blizzard-confirmed widespread incident. But it is absolutely article-worthy, because once top-end crafting starts producing rewards that do not count the way players think they should, the whole prestige loop gets a little harder to take seriously.

Read More

Diablo 4 Players Say an Infinite Nightmare Dungeon Farming Exploit Is Back, and That Is a Very Bad Look

Diablo 4 has enough ordinary bugs without adding “the loot economy might be getting bent over a chair again” to the list. But that is where the conversation is heading after a fresh April 14 post on Blizzard’s Diablo IV bug report forum claimed a critical exploit is allowing infinite Nightmare Dungeon farming. Blizzard has not publicly confirmed the claim, and that matters. Right now, this is a player report — not a proven incident report from Blizzard. But in a loot game, that kind of accusation spreads faster than rot.

The headline is ugly even before you get into the details

The forum post says players are allegedly using a reset interaction to keep farming Nightmare Dungeon targets repeatedly, turning rare-item runs into something much closer to a conveyor belt. I am deliberately not repeating the method here, because the story is the accusation and its potential impact, not the instructions. What matters is that the report explicitly frames this as an economy and fairness problem, and Blizzard’s latest Diablo IV forum pages show the thread sitting among the newest active bug topics today.

This lands badly because Diablo players have seen this movie before

That is why the story has real bite. Diabloz has already covered what happens when Diablo 4’s item economy starts smelling wrong, including Blizzard Shuts Down Diablo 4 Trading Amid Item Duplication Exploit. This new report is not the same thing, and nobody should pretend it is. But it touches the same nerve: the second players think repeatable exploit farming is back in circulation, every rare drop and every trade starts feeling a little dirtier.

The timing makes it worse

Diabloz has spent the last stretch covering Diablo 4 stories where rewards and systems already looked shaky, from Mythic caches disappearing after crafting to Greater Bloodied Caches vanishing before a crash. Drop an exploit accusation into that atmosphere and people are not going to stay calm and analytical about it. They are going to assume the floorboards are all rotten.

Blizzard does not need to prove it is real to have a problem

That is the brutal little truth here. If Blizzard later shows this report is exaggerated, great. But until it says something, the thread itself is enough to start poisoning trust. And in Diablo, suspicion alone can do damage. When players stop believing the grind is honest, they stop caring whether the next drop was lucky, earned, or just dragged out of a bugged machine.

Read More

Diablo 4 Players Say Arbiter Duration Is Breaking Early, and Paladin Builds Are Falling Apart Mid-Fight

Diablo 4 has a lot of ways to ruin your rhythm, but this one is especially nasty because it hits right in the middle of a build doing what it is supposed to do. A fresh April 11 bug report says Arbiter duration is ending far too early, leaving one Paladin player with a setup that looks fine on paper and collapses in practice. That is not just annoying. That is the kind of bug that makes a build feel like it is lying to you.

The numbers are ugly

The report on Blizzard’s Diablo IV PC Bug Report forum is brutally simple. The player says their Arbiter duration is 54 seconds and their cooldown is 49.57 seconds, but Arbiter still runs out about 20 seconds before the cooldown is ready again. Their conclusion is not subtle either: it makes Torment 4 bosses unbeatable. One reply says they could not replicate the issue, so this is not yet proof of a broad outbreak, but it is absolutely a live current complaint.

That matters because Arbiter is built around staying active

Blizzard’s own Paladin reveal describes Arbiter of Justice as a transformation that sends you into Arbiter form, boosts movement, replaces evade with Angelic Leap, and deals damage around you while active. In other words, this is not a tiny passive buff nobody notices. It is a whole form with a clear power window, and if that window collapses early, the build fantasy gets kicked in the teeth.

The awkward part is Blizzard has already been fixing Arbiter-related bugs

That is what gives this story extra bite. In Blizzard’s current Diablo IV patch notes,  the team already lists a Paladin bug fix for an issue where the Armor while in Arbiter form temper did not update correctly if values changed while Arbiter was active. That is not the exact same problem as a duration collapsing early, but it does show Arbiter has already needed technical cleanup in live Diablo IV.

It also fits a broader pattern

That is probably why this one lands so hard. Diabloz already covered how Dawnfire stacks can vanish when entering a World Boss Zone,  which is another Paladin-flavored case of a build setup falling apart at the exact moment it should matter most. Different mechanic, same rotten feeling: you prep, you ramp, you get ready for the fight, and then the game quietly pulls a floorboard out from under you.

When your uptime is fake, your build is fake

That is really the whole story. Diablo players can live with nerfs, long grinds, and ugly boss damage. What they hate is unreliable uptime on a core power state. If Arbiter is expiring twenty seconds early for some players, then the problem is not just damage loss. It is trust. And in a season already packed with technical weirdness, that is one more thing Diablo 4 really did not need.

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 19 Greater Bloodied Caches Vanished at Once, Then the Game Crashed

Diablo 4 has done plenty of irritating things to player rewards lately, but this one is especially filthy. A fresh April 12 report says a player opened 19 Greater Bloodied Caches, got no items at all, and then watched the game crash seconds later. That is not bad luck. That is the sort of bug that makes a reward screen feel like a mugging.

The report is ugly in exactly the way you think

The current complaint appeared on Blizzard’s PC Bug Report forum under the title “I click all 19 greater bloodied cache , and no items came out. seconds later, game crash and shutdown.” The same issue also shows up on the broader Diablo IV forum index and in a separate Technical Support-style thread, which gives it a little more weight than one lonely post screaming into the void. It is still not proof of a widespread disaster, but it is definitely not nothing.

This lands badly because Diablo 4 already has cache trust issues

That is where the story gets nastier. Diabloz already covered how a Mythic Unique Cache could disappear after crafting, so this new report lands in a game environment where players are already primed to expect reward containers to behave like cursed prank boxes. This new case is different — it is not crafting, it is bulk opening followed by a crash — but the emotional effect is basically the same: you did the work, the reward existed in theory, and then Diablo 4 decided theory was enough.

Bulk opening makes the whole thing feel even worse

That is really the hook here. One missing reward is annoying. Nineteen at once is the kind of thing that makes a player immediately start counting what else they no longer trust. If the report is accurate, this was not just a cache bug. It was a cache bug chained directly into a client crash, which is about the least reassuring combo a loot game can offer. And because the post specifically says the items never came out before the shutdown, players are left with the classic Diablo question: did the loot fail to spawn, or did it spawn just long enough to disappear into some invisible administrative hell?

Reward systems should not feel this haunted

Blizzard has not attached a public fix or explanation to the report yet. So the careful version is still this: fresh player report, not confirmed mass issue. But even at that level, it is a strong story, because Diablo players can tolerate stingy drops far better than they tolerate vanishing ones. When a game starts eating containers, eating rewards, and then crashing on the way out, people stop arguing about balance and start wondering whether the loot system itself is drunk.

Read More

Diablo 4 Players Say the Duplication Bug Might Be Back, and That Is the Kind of Rumor Blizzard Cannot Let Linger

Diablo 4 already has enough normal chaos without adding “maybe the economy is broken again” to the pile. But that is the mood right now after a fresh April 12 post on Blizzard’s official bug forum claimed the duplication bug is back. Blizzard has not confirmed that publicly, and at this stage it is still a player report, not a proven full-scale incident. Even so, duping accusations are never small. The second that word shows up, people stop talking about one bug and start talking about whether the whole loot ecosystem can be trusted.

The current report does not prove it, but it is serious enough to watch

The thread itself is blunt: “Duplication bug is back!” The player says the problem has “recently returned,” points to item-selling activity on outside trading platforms, and hopes Blizzard gets it fixed before Season 13. There is also a second same-day Diablo IV forum topic, “Serious Copy Bug！”, which adds a little more heat — but not as much as it first sounds like, because it appears to come from the same poster, not a wave of separate confirmations. So the responsible read here is still: fresh allegation, not established fact.

Why this hits harder than a normal bug thread

This is the real hook. If a dungeon breaks, players get annoyed. If a cache disappears, they get angry. But if duping is even possibly back, the conversation gets darker fast because it touches trading, item value, and the basic credibility of the game’s economy. That is exactly why Blizzard previously had to act hard when Diablo 4’s economy got hit by a duplication exploit. Back in 2024, Blizzard temporarily disabled trading over the issue — something we covered in Blizzard Shuts Down Diablo 4 Trading Amid Item Duplication Exploit. This is not that same event, but it is why the current claim will make people nervous almost instantly.

It also lands at a bad time

Part of the problem is timing. Diabloz has already been covering a run of Diablo 4 stories where rewards, progression, and item behavior feel shaky — from Mythic caches disappearing after craftingto Dawnfire stacks vanishing at World Bosses. A duplication accusation drops right into that atmosphere and makes every other systems bug feel a little more sinister. Blizzard may end up proving this thread is noise. But until it says something, the rumor alone is toxic.

Read More

Diablo II: Resurrected’s Warlock Nerf Backlash Is Getting Ugly Fast

Yesterday, Blizzard dropped the official PTR 3.2 notes for Diablo II: Resurrected. Today, the Warlock community is acting like someone kicked over the altar and stole the candles. This is no longer just a “players react to patch notes” story. It has turned into a full-on backlash cycle, with fresh forum threads accusing Blizzard of betrayal, overcorrection, and gutting the class that just sold an expansion a few weeks ago.

The patch notes lit the fuse

The anger is not hard to understand. PTR 3.2 does not just tap one or two Warlock outliers. Blizzard is hitting multiple parts of the class at once, including Miasma Bolt, Miasma Chains, Ring of Fire, Flame Wave, Echoing Strike, Bind Demon, and the old two-hand-plus-shield setup. Blizzard is also changing Herald and Latent Sunder Charm behavior, while openly admitting Herald spawn rates and charm drops “feel too low.” That last part is probably healthy. The Warlock part is what set the forums on fire.

Players are calling it a rug pull

The tone on the forums has shifted from normal balance grumbling to something much saltier. In one active thread, a player says they feel “betrayed” and asks why Blizzard is nerfing one class instead of uplifting the rest. Another argues the changes “break” Bind Demon and likely the summoner tree by making unique demon binding too expensive in skill points. A separate complaint thread says players already built around these mechanics, spent time and trade wealth on them, and now feel like Blizzard is turning that investment into trash after the fact. That is where the “rug pull” language is coming from.

Not everyone is mad, but the mood is nasty

To be fair, this is not one-sided. There are also active threads defending the nerfs as overdue, arguing Warlock launched absurdly overpowered and was crowding out older class identities. One poster called it a “tough but right decision,” while another said they were actually excited for the patch because Warlock had started replacing too many traditional roles. But even in the pro-nerf camp, the underlying message is basically: yes, Blizzard had to do this, but it probably should not have let things get this messy in the first place.

The real problem is timing

That is why this story has bite. Blizzard is probably right that Warlock needed balancing. But when a class arrives with a paid expansion, dominates the meta, and then eats a giant PTR correction almost immediately, players do not read that as clean stewardship. They read it as Blizzard selling the fantasy first and fixing the consequences later. In Diablo, people can handle nerfs. What they hate is feeling like they bought the honeymoon build and got handed the divorce papers two months later.

Read More

Diablo 4 Players Say Paladin’s Dawnfire Gloves Lose Their Stacks the Second a World Boss Shows Up

Diablo 4 has plenty of bugs that feel annoying. This one feels rude. Players say Paladin’s Dawnfire gloves can lose their built-up stacks the moment you enter a World Boss Zone, which is exactly the kind of bug that turns a carefully prepared build into a shrug and a loading screen. If your big item setup falls apart right before a major fight, that is not “friction.” That is the game kicking your chair away.

The current complaint is visible again on Blizzard’s Diablo IV forums, where the topic “Paladin’s Dawnfire gloves lose their stacks when you enter a World Boss Zone” showed up among the latest active Diablo IV discussions on April 11. The underlying bug report says that if you build up Dawnfire stacks before entering the zone, they vanish as soon as you cross into the World Boss area. The same player also says they may have seen something similar around Belial’s Palace during the PTR, suggesting this might be tied to specific zone transitions rather than just one boss arena.

It matters because Dawnfire is built around ramping power

This is not just some random stat stick losing a buff nobody notices. Blizzard’s own 2.6.0 PTR notes show Dawnfire as a Paladin unique that was actively being tuned: the tooltip was updated to better explain the aura, Holy Light was changed to refresh the duration, the buff duration was increased from 15 to 20 seconds, and Blizzard added a buff number and duration indicator to the icon. In plain English, this is an item that clearly wants players to care about maintaining and tracking its stacks. So if a zone boundary is deleting that setup, the whole item fantasy gets kneecapped right before the part that should feel coolest.

Blizzard has already been fixing Dawnfire-related issues

That is the awkward bit. In the March 20 Diablo IV patch notes, Blizzard already fixed multiple Dawnfire problems, including issues where allies had the visual fire aura when Dawnfire was equipped and where Dawnfire’s Holy Light Aura changed how NPC allies dealt damage. That shows the item has already needed cleanup in live Diablo IV. So when players are still flagging another Dawnfire-related issue on the forums, it starts to look less like a weird one-off and more like an item that keeps finding new ways to misbehave.

Losing stacks at the doorway is a special kind of ugly

There is also something uniquely rotten about a bug like this. Players can live with low damage. They can live with balance tweaks. What they hate is prep work being erased by a technicality. If Dawnfire stacks disappear when entering a World Boss Zone, the problem is not just damage loss. It is that the game teaches you to ramp up a mechanic, then wipes it the second you reach the content where it should matter most. In a loot game, that kind of bug always feels worse than the tooltip makes it sound. 

Read More