Diablo 4’s bug boards are full of blunt, ugly headlines. Missing loot. Broken rewards. Pets that will not unlock. Then there is one of the stranger fresh entries in Blizzard’s latest PC bug listings: “Of pests and Pestilence.” That title sounds less like a technical report and more like somebody walked out of a plague-ridden side quest muttering at the sky. Which, in Diablo 4, is usually a sign that something specific and annoying went sideways.

The problem is that the public side of this one is still thin. Blizzard’s latest Diablo IV PC bug index shows “Of pests and Pestilence” as a fresh topic active on April 20, 2026, but the listing itself does not expose much more detail from the category page. That means nobody should pretend we have a fully documented breakdown of the issue yet. What we do have is a live current report attached to what sounds very much like a quest, event, or progression step that has gone rotten in some interesting way.

The title alone points toward a quest or objective problem

Even with limited public details, there is a grounded way to read this. “Of Pests and Pestilence” sounds like the name of a questline, objective, or event step rather than a random system bug. If that reading is right, then the likely category here is progression friction: an objective not updating, an enemy not counting, an interact point failing, or the game simply refusing to acknowledge that the player did the thing it asked for.

That matters because these are some of the most quietly infuriating Diablo 4 bugs. A flashy crash is obvious. A quest or objective that half-breaks is worse in a slower, nastier way. It leaves players stuck in the middle of content, wondering if they missed something, misunderstood something, or just got unlucky enough to hit one more rotten little seam in the game.

Diablo 4 already has a habit of making normal progression feel weirdly fragile

This fresh report also lands in a game that has already been collecting too many “basic loop broke again” stories. We recently covered how players said Ashava’s world boss cache gave no loot, how some monsters were allegedly becoming unkillable, and how wardrobe and transmog issues were still lingering. Different systems, same mood: Diablo 4 keeps producing little moments where players stop trusting whether a normal activity will actually behave normally.

That broader pattern is what gives even a vague report like this some editorial value. In a calmer week, a mysterious quest-sounding bug title might just sit there unnoticed. In Diablo 4’s current climate, it immediately reads like one more possible case of a supposedly simple piece of content turning into avoidable friction.

Thin details do not make it worthless, just early

To be fair, this is still an early watchlist story, not a slam-dunk confirmed outbreak. The public bug index shows the topic is live, but without a visible full write-up from the category page, the responsible read is that something tied to “Of Pests and Pestilence” appears to have gone wrong for at least one player, and the fuller nature of the issue may become clearer once the thread develops.

Sometimes that means the problem turns out to be tiny. Sometimes it becomes one of those quest bugs that keeps resurfacing for weeks because it blocks exactly the wrong piece of content. Right now, this one is interesting precisely because it sits in that uncomfortable middle ground.

For now, it is one to watch

Diablo 4 does not need every bug report to explode into a giant story for it to matter. Sometimes a weird title in the bug index is enough to flag where the next annoying little fire might start. And with a name like Of Pests and Pestilence, this one already sounds like it came preloaded with a bad attitude.

Read More

Diablo Immortal Players Say Gauntlet 3 Legacy Feels Broken

Diablo Immortal has no shortage of bug reports, but every now and then one shows up that feels bigger than a simple broken button or missing reward. A fresh Blizzard forum thread titled “Gauntlet 3 legacy bugged and compensation required for wasted hours and days” is exactly that kind of complaint. The core claim is ugly: players say Gauntlet 3 Legacy is tuned so brutally that normal boss attacks feel like instant kills even when characters are sitting well above the listed combat rating requirement.

The complaint comes from a live thread on the official Diablo Immortal bug report forum, where the original poster argues that Gauntlet 3 Legacy “defies all logic” of combat rating, armor, and damage reduction. According to that post, bosses are still one-shotting players with 58,000+ combat rating even though the listed requirement for the activity is much lower. That is the kind of complaint that instantly gets attention, because when players are thousands of CR above the gate and still getting deleted, the whole point of the number starts looking cosmetic.

The thread gets more interesting once other players push back

What makes this story stronger than a basic rage post is that the replies do not just nod along. They argue back. One forum reply says the real problem is not that the activity is literally impossible, but that Gauntlet difficulty is only loosely tied to combat rating and instead comes down to extreme tuning, tight damage checks, and the need for highly optimized builds. Another player pushes even harder by pointing to a solo clear example from a lower-stat character, which undercuts the idea that the mode is fully broken for everyone.

That turns the whole thing into a better article than “players say impossible bug.” The actual argument looks more like this: is Gauntlet 3 Legacy truly bugged, or is it just tuned so absurdly around specific classes, setups, and high-end performance that most players were never realistically meant to beat it in the first place?

That is still a problem, even if the mode is technically beatable

And honestly, that may be the more interesting issue. The original poster eventually concedes that Gauntlet 3 Legacy is not impossible, but argues it is effectively designed for a tiny slice of the player base, especially Barbarian and Blood Knight setups with the right sustain and survivability. If that reading is even half right, then the mode may not be “bugged” in the clean mechanical sense players usually mean. It may just be tuned so narrowly that the rest of the community is wasting time walking into an activity they never had much chance of clearing.

That is not a small distinction, but it is not exactly comforting either. In some ways it is worse. A bug can get fixed. A mode designed around a tiny elite slice of builds while pretending to be broadly accessible is a much uglier live-service habit.

Diablo Immortal already has enough trust problems around progression

This also lands in a game that has already been building a miserable little pile of progression and reward frustration. We recently covered how players said rearranging legendary gems made 17 of them disappear, how 10 Legendary Crests allegedly vanished with no refund mail, and how Survivor’s Bane rewards were reportedly claimable multiple times. Against that backdrop, a Gauntlet thread arguing that a major PvE challenge is either broken or wildly misleading does not land softly.

Fresh thread, messy debate, very real mood

To be fair, Blizzard has not publicly confirmed that Gauntlet 3 Legacy is broken, and the replies in the thread make it clear there is real disagreement over what is happening. That matters. But so does the broader mood. The topic is live, current, and active in Blizzard’s bug listings, and the debate itself tells you something important: players are not just arguing about whether Gauntlet 3 is hard. They are arguing about whether Diablo Immortal is pretending a mode is fair when it is really balanced around a much narrower reality.

At this point, Diablo Immortal does not just need hard content. It needs hard content that stops making players wonder whether the numbers on the gate mean anything at all.

Read More

Diablo 4 Wardrobe Bug Is Back, and Players Are Not Surprised

 

Diablo 4 has spent plenty of time lately breaking things that matter more than cosmetics. Loot vanishes, rewards go missing, and bosses sometimes pay out like they forgot why they exist. But Sanctuary also keeps finding time for a smaller, pettier kind of misery: the wardrobe still looks like it has unfinished business with players.

A fresh Diablo IV PC Bug Report listing on April 20 shows a new topic simply titled “Wardrobe malfunction”. And yes, that title is doing a lot of heavy lifting. Blizzard’s public listing does not show much detail yet, but the fact that wardrobe complaints are surfacing again is enough to make this more than random noise. Cosmetic systems are supposed to be low-friction. Diablo 4’s wardrobe keeps behaving like a side quest in bureaucratic hell.

This is not some brand-new curse

What makes the new report worth watching is that it fits a pattern that has been hanging around for months. Back in December, players reported in Wardrobe no longer works that they could no longer change pets, mounts, trophies, mount armor, or even basic transmog looks without the system behaving strangely. In January, another PC thread, Patch 2.5.3 still has wardrobe/transmog issues, described problems that were reportedly introduced earlier and still lingering into 2026.

There is also a separate Xbox-side report from December, Wardrobe Malfunction, where players said Reliquary items were downloaded but not usable in the wardrobe, with the apply button greyed out. That is a useful reminder that wardrobe trouble in Diablo 4 has not been one clean, single bug. It has looked more like a recurring category of cosmetic nonsense that keeps changing shape just enough to stay annoying.

The closet problem sounds small until it hits paid cosmetics

That is really the hook here. Cosmetic bugs are easy to dismiss until they touch things players unlocked, earned, or paid for. Then suddenly it is not just “the wardrobe is being weird.” It is “the game is failing at one of the simplest ownership loops it has.” In a live-service game full of store bundles, event rewards, expansion bonuses, and premium visuals, wardrobe bugs do not stay harmless for long.

We already covered how Diablo 4 players said the wardrobe was just not working, and more recently how players still could not claim the Herald of Hatred pet. Those are not identical issues, but they live in the same ugly neighborhood: Diablo 4 keeps making cosmetic ownership and customization feel less reliable than they should.

Fresh report, thin details, familiar smell

To be fair, the new April 20 thread is still thin from the public side. Blizzard’s bug index confirms the topic exists, but there is not yet a full public breakdown showing exactly what failed in this latest case. That uncertainty matters, and nobody should pretend otherwise. But the reason it is still worth covering is obvious enough: wardrobe complaints do not appear in a vacuum anymore. They land on top of months of transmog, wardrobe, and cosmetic reward friction.

At this point, Diablo 4 does not just need more cosmetics. It needs a wardrobe system that stops acting like every new patch is an opportunity to reinvent basic inconvenience.

Read More

Diablo 4 Lord of Hatred Dev Stream Is the Story to Watch

 

After days of loot bugs, missing rewards, and systems behaving like they were assembled in the dark, Diablo 4 finally has a cleaner story on the board. Blizzard has officially announced a Lord of Hatred Developer Update Stream, and for once the headline is not “players say something vanished.” It is a proper expansion beat, tied directly to the next big Diablo 4 milestone.

That matters because Lord of Hatred is set to arrive on April 28, 2026, and Blizzard is clearly shifting into the part of the campaign where it starts laying out what players are actually buying into. The official expansion page says Lord of Hatred brings a new campaign, two new classes, Paladin early access through pre-purchase, and major updates for all Diablo 4 players, including a skill tree overhaul, level cap increases, and a loot filter. That is a much stronger conversation than another afternoon of people staring at empty caches and broken menus.

The stream matters because Blizzard is selling more than just a story chapter

What makes this interesting is that Blizzard is not pitching Lord of Hatred as a simple campaign add-on. The official expansion page frames it as a broader Diablo 4 reset point, with reshaped hero progression, deeper customization, and new tools for mastery landing alongside the expansion. In other words, this is not just “more Mephisto.” Blizzard is trying to position Lord of Hatred as the next big systems era for the game.

That is exactly why the dev stream matters more than the usual marketing trailer drip. Players have already seen the broad pitch. What they want now is the practical stuff: what the systems actually look like, how the progression changes feel, what kind of buildcraft this opens up, and whether Blizzard can make the expansion feel like more than a glossy pre-order page with fire behind it.

There is also free bait, because of course there is

Blizzard is also dangling a couple of livestream drops during the event. According to the official stream announce blog, players can watch any Diablo IV stream with drops enabled for 30 minutes to earn the Decaying Corona staff cosmetic, and for 1 hour to earn the Double Trouble sword cosmetic. Blizzard says those drops can be earned until April 24, 2026 at 10:59 a.m. PT.

That is not earth-shaking, but it does tell you Blizzard wants eyes on this one. This is not being treated like some minor blog post tucked behind a patch note wall. They want the audience there, they want the conversation moving, and they want Lord of Hatred back in the spotlight for something other than store confusion or expansion bonus headaches.

This is probably the healthiest Diablo 4 story on the table right now

And honestly, that is part of the appeal. We recently covered how players still could not claim the Herald of Hatred pet, how Ashava’s world boss cache reportedly gave no loot, and how some monsters were allegedly becoming unkillable. Those stories are real, but they also make the game feel like a haunted machine. A straight-up official expansion update is a much better look for everyone involved.

If Blizzard nails the stream, it gives Diablo 4 something it badly needs this week: momentum that is not built out of forum damage control. If the details are strong, Lord of Hatred stops being just another pre-order pitch and starts looking like the actual next phase of the game.

April 28 is close enough that this stream should matter

The timing is what makes this more than filler. With Lord of Hatred launching April 28, 2026, Blizzard is well past the stage where it can get away with broad mood pieces and vague promises. Players are close enough to release that they should expect real answers, real system detail, and a clearer sense of whether this expansion is going to fix things, deepen things, or just add another layer of expensive fire on top of the current mess.

Either way, this is the Diablo 4 story worth watching right now. Not because it is rumor bait. Not because something broke. Because for once Blizzard is actually stepping forward to explain what comes next.

Read More

Diablo 4 Players Say They Still Cannot Claim Herald of Hatred Pet

 

Diablo 4 has another one of those bugs that looks small until you remember it sits right on top of money, ownership, and expansion bonuses. A fresh player report says they still cannot claim the Herald of Hatred pet even though the game presents it as a free reward. In a live-service game, that is exactly the kind of thing that turns a cosmetic issue into an argument about entitlement, storefront logic, and whether Blizzard’s messaging makes any sense at all.

The latest complaint comes from a new thread on the official Diablo IV PC bug report forum, where a player says they own Vessel of Hatred, bought the Ultimate Edition, and still cannot claim the free pet. One reply in the same thread suggests the reward may only be available to players who purchased Vessel of Hatred before it was folded into Lord of Hatred. If that is true, then this is not just a pet issue. It is a wording issue, a claim-flow issue, and a very Blizzard-style “the store and the player expectation are no longer speaking the same language” issue.

This bug has been hanging around for months

What makes this worth covering is that the April 19 thread is not some isolated little one-post confusion bomb. Blizzard’s forums already have older threads from January where players were reporting the same basic problem. In Herald of Hatred Pet not available, players said the pet appeared locked, showed up as free, and still could not be equipped or claimed. In another thread, Herald of Hatred cosmetics not showing up after buying Lord of Hatred Standard Upgrade, players described the same broader problem: the reward looked available, but the actual unlock path broke down.

That longer trail matters because it changes the story from “one player is confused” into something uglier. If the Herald of Hatred reward has been sitting in this half-claimable state for months, then Blizzard is not just dealing with a cosmetic hiccup. It is dealing with an expansion-bonus mess that still does not look clearly communicated or cleanly fixed.

Cosmetics are not “just pixels” when the store is involved

Yes, some players will always roll their eyes and say it is only a pet. That misses the point. The issue is not whether the wolf changes combat. The issue is that Diablo 4 is showing players a free reward tied to expansion ownership and then apparently failing to make the claim rules obvious or the unlock path functional. That is how a cosmetic complaint becomes a trust complaint.

It also lands at a time when Diablo 4 has already been stacking too many stories about rewards and ownership feeling shaky. We recently covered how Season 12 reward complaints were still hitting boss loot, and how Lord of Hatred is already driving fresh speculation around Diablo 4’s next big platform move. Against that backdrop, an expansion-linked pet that still cannot be claimed properly just makes the whole ecosystem look messier than it should.

The pet is small. The signal is not.

To be fair, this is not some game-breaking disaster. Nobody is claiming Herald of Hatred being locked out will destroy a season. But that is not really the standard here. The real issue is that a reward described as free still appears confusing or inaccessible months after earlier players started flagging the same problem. If Blizzard wants expansion bonuses to build goodwill, it probably should not keep turning them into support riddles.

At this point, Diablo 4 does not just need the pet to unlock. It needs the rules around the pet to stop sounding like they were written by two different departments in a dark room.

Read More

Diablo Immortal Players Say Rearranging Gems Made 17 Disappear

 

Diablo Immortal has another progression nightmare brewing, and this one is exactly the kind of bug that makes players go from confused to furious in about three seconds. A fresh report on Blizzard’s forum says a player lost 17 legendary gems after rearranging them. Not one gem. Not a weird tooltip. Seventeen. In a game where legendary gems sit right at the center of power, grind, and spending anxiety, that is not a minor inconvenience. That is a live-service horror story. (official Diablo Immortal bug report thread)

The report appeared on Blizzard’s latest Diablo Immortal bug listings on April 20, 2026, posted by a PC player running version 4.3.0. Publicly, the thread is still thin. Blizzard has not posted a response in it, and the forum view does not show much more than the headline and basic device details right now. That means nobody should pretend we have a full technical breakdown of what “rearranging” involved. But the claim itself is brutally clear, and the category is bad enough that even one live report matters.

This is one of the few bug categories that instantly sounds expensive

There are lots of Diablo Immortal bugs players can laugh off for a minute. A busted menu. A weird animation. A reward icon acting possessed. Legendary gems disappearing are not in that category. They hit the exact part of the game where time investment, luck, and sometimes real money all overlap, which is why a thread like this gets ugly fast even before anyone has full details.

And honestly, it should. If a player moves gems around in their own inventory or build setup and the result is that seventeen of them apparently vanish, that is not just a systems hiccup. That is the kind of thing that makes people wonder whether they can safely touch the interface at all without losing something valuable.

Diablo Immortal already has way too much baggage around gem and reward trust

This report also lands in a game that has already been having a miserable little run of progression-related stories. We recently covered how a legendary gem reportedly vanished after a Rift, how players said 10 Legendary Crests disappeared with no refund mail, and how a Leviathan Surge upgrade allegedly consumed 9,000 sigils and gave nothing back. Different bugs, same ugly mood: when Diablo Immortal touches gems, rewards, or progression systems, players are increasingly expecting something cursed to happen.

That matters because pattern recognition changes how every new report lands. In a healthier game week, a one-post thread about missing gems might feel like an isolated account issue. In Diablo Immortal right now, it reads more like yet another reason players are side-eyeing the entire reward economy.

Fresh report, thin details, terrible category

To be fair, this is still one fresh public report with limited visible detail. Nobody should oversell it as a giant confirmed outbreak. The grounded version is simpler: a player says rearranging their legendary gems caused 17 of them to disappear, the thread is live on Blizzard’s bug board, and there is no public resolution attached yet. That is already enough for a real story, because the category is explosive on its own.

At this point, Diablo Immortal does not just need its gem systems to work. It needs players to stop feeling like opening their inventory is a high-risk activity.

Read More

Diablo Immortal Players Say Battlegrounds Were Super Laggy

 

Diablo Immortal players are complaining about another rough night in Battlegrounds, and this one sounds less like normal PvP salt and more like the servers briefly forgetting what a fight is. A fresh bug report says Battlegrounds were “super laggy” on April 19, with heavy stuttering, delayed reactions, and moments where attacks appeared to land while everyone’s health bars stayed full for five to ten seconds. That is not just annoying. That is the kind of lag that makes a match feel fake.

The report comes from a fresh thread on the official Diablo Immortal bug report forum, where a PC player says all six Battleground matches they played that night were unusually laggy. In a follow-up post, the same player says there were moments where six or seven players were visibly dashing around and attacking, but nobody’s HP moved for several seconds. According to that report, the desync was bad enough that idol progress kept moving in situations where players probably should have died much earlier.

That is not ordinary Battleground frustration

Anyone who has spent time around Diablo Immortal PvP knows players can blame lag for just about anything, usually five seconds after getting deleted by a whale. But this report has a more specific smell to it. It is not just “I lost and therefore the servers are cursed.” It is “the combat state looked visibly wrong, attacks seemed to connect, and the match logic stopped lining up with what was on screen.” That is a much uglier category of complaint.

And it matters because Battlegrounds already live on a fragile little edge where fairness is debated constantly. The second server behavior starts looking unreliable on top of the usual class balance and matchmaking arguments, the mode goes from frustrating to clownish very quickly. If players cannot trust whether hits are registering in real time, then the whole PvP experience starts feeling like an expensive argument being held underwater.

The timing is bad because Blizzard just tried to refresh Battlegrounds

This also lands awkwardly because we recently covered how Blizzard rolled out a much bigger Battlegrounds refresh to calm some of the long-running PvP complaints. That update was supposed to make the mode feel more stable, more readable, and less miserable. A fresh “Battlegrounds are super laggy tonight” report does not automatically mean the refresh failed. But it absolutely undercuts the mood around it.

It also fits a broader recent pattern where Diablo Immortal keeps stumbling into stories about systems not behaving the way players expect. We have already covered how players said 10 Legendary Crests vanished with no refund mail and how a legendary gem reportedly disappeared after a Rift. Different systems, same broad issue: the game keeps producing moments where trust takes a hit.

Fresh report, small thread, ugly symptom

To be fair, this is still one fresh public report with limited follow-up, not proof that every Battleground in every region turned into slideshow PvP overnight. Nobody should oversell it. But the symptom is bad enough to matter. When players describe a fight where attacks are flying, movement is happening, and health bars simply refuse to update for several seconds, that is not normal latency grumbling. That is the kind of thing that makes a competitive mode look broken in the most visible possible way.

At this point, Diablo Immortal does not just need Battlegrounds to be balanced. It needs them to feel like the server and the screen are participating in the same match.

Read More

Diablo 4 Switch Rating Rumor Returns With Lord of Hatred

 

For once, Diablo 4’s latest talking point is not a missing reward, a haunted menu, or a boss chest full of disappointment. This one is a platform rumor, and it has a little more meat on it than the usual wishful thinking. Multiple gaming outlets have reported that Diablo 4: Lord of Hatred has surfaced on Indonesia’s game rating system for Nintendo Switch, which is exactly the kind of thing that gets handheld Diablo fans sitting up fast. :contentReference[oaicite:0]{index=0}

The important catch is the obvious one: Blizzard has not officially announced Diablo 4 for Switch or Switch 2. Right now, the real story is the rating itself and what it might mean. GamesRadar’s report on the Indonesian rating says the listing is specifically tied to Lord of Hatred, Diablo 4’s upcoming expansion, while Nintendo Life’s coverage notes that the listing has kicked the old Switch 2 rumor back into motion. That does not equal confirmation. But it is a lot more interesting than some random insider whisper on social media. :contentReference[oaicite:1]{index=1}

Why people are taking this one seriously

There are two reasons this rumor has legs. First, ratings boards do leak real releases often enough that people pay attention when they show up. Second, Diablo already has history on Nintendo hardware. Diablo 3 made the jump to Switch years ago, and Blizzard clearly does not treat Nintendo platforms as off-limits for the franchise. So when a rating appears for Lord of Hatred, people are naturally reading it as a possible sign that Blizzard wants Diablo 4 on handheld hardware too. That is still an inference, but it is a grounded one. :contentReference[oaicite:2]{index=2}

The detail making this slightly messier is that some reports say the Indonesian listing points to Switch, while the wider conversation around it is really about Switch 2. Nintendo Life specifically frames it in the context of Switch 2 discussion, and other coverage has done the same. So the rumor currently lives in that awkward zone where the rating is real enough to discuss, but the exact hardware target still looks blurry. :contentReference[oaicite:3]{index=3}

If it happens, Blizzard would not be short on reasons

There is also a very practical argument for why this rumor keeps sounding plausible. Blizzard is about to push Lord of Hatred as a big new Diablo 4 beat, and a platform expansion would be one of the cleanest ways to make that expansion feel even bigger. A handheld Diablo 4 pitch is easy to understand, easy to market, and dangerously good at separating ARPG fans from their free time. That is not proof. It is just the kind of business logic that makes the rumor feel annoyingly believable.

And honestly, if Blizzard is looking for a cleaner headline than Ashava caches giving no loot or monsters allegedly becoming unkillable, “Diablo 4 might be heading to Nintendo hardware” is a much nicer story to have in circulation.

Right now, it is a rating, not a reveal

That is the line worth holding. The Indonesian rating report is real enough to make this a legitimate rumor story. But until Blizzard says something publicly, it stays exactly that: a rumor story. No port has been confirmed, no release date has been announced, and nobody should write the Nintendo eShop page in ink just yet. Still, as Diablo rumors go, this one at least has an actual paper trail instead of just someone’s cousin’s favorite leaker.

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 Ashava’s World Boss Cache Gave No Loot

 

Diablo 4 has another reward complaint on the table, and this one hits one of the game’s most visible public events. A fresh player report says Ashava’s world boss cache gave no loot at all, which is exactly the kind of sentence that can turn a routine boss kill into a giant waste of time. World bosses are supposed to feel like a quick burst of chaos followed by a neat little payout. Getting the chaos without the payout is a much uglier deal.

The current complaint comes from a fresh thread on the official Diablo IV PC bug report forum, where the player says Ashava’s cache did not give them any loot after the kill. The thread showed up in Blizzard’s latest Diablo IV PC bug listings on April 19, which makes it current, visible, and very easy for annoyed players to latch onto.

This is not a glamorous bug, but it lands hard

There is a reason world boss reward issues always feel worse than they probably look on paper. These fights are not just random dungeon trash with a bad mood. Players show up on a timer, burn the boss down with a crowd, and expect the reward loop to be clean. If the cache opens and hands back nothing, the whole experience suddenly feels like it was built to waste your schedule instead of reward it.

And yes, some of that sting is because this is Ashava. World boss kills are big, noisy, public little rituals. They are not supposed to end with a player standing there wondering whether the cache was empty, broken, or swallowed by some invisible loot gremlin.

Ashava cache complaints already have history

What makes this fresh report more interesting is that it is not arriving in a vacuum. Diablo IV’s forums already have older Ashava and world boss cache complaints stretching back to 2023, including reports that Ashava did not drop the cache properly and threads about weekly world boss loot caches failing to appear. That does not prove the new report is the same bug wearing a dusty old mask. But it does mean players have seen this category before, which makes a fresh Ashava complaint feel a lot less isolated and a lot more annoying.

We recently covered how players said Bloodied boss rewards were still going missing in Season 12 and how Band of First Breath was reportedly dropping like a cursed object. This new Ashava report is different, but it fits the same broad pattern: when Diablo 4 touches loot right now, players are not exactly giving it the benefit of the doubt.

Fresh report, small thread, old frustration

To be fair, this is still just one fresh public complaint, not proof that Ashava is broadly eating everyone’s rewards today. Nobody should oversell it. But it is a clean and very understandable story, and those are often the ones that travel fastest. Kill world boss. Open cache. Get nothing. There is no complicated theorycrafting required there.

At this point, Diablo 4 does not just need loot to drop. It needs players to stop feeling like every reward container in the game has a non-zero chance of being mostly decorative.

Read More

Diablo Immortal Players Say 10 Legendary Crests Vanished

 

Diablo Immortal has another one of those bugs that instantly makes people suspicious, because it hits the exact place where progression, value, and player trust all overlap. A fresh report says 10 Legendary Crests were lost and never returned through in-game mail, which is normally the fallback players expect when an Elder Rift entry goes sideways. If that safety net fails too, the whole thing stops feeling like a small hiccup and starts feeling expensive. (official Diablo Immortal bug report thread)

The new complaint appeared on Blizzard’s latest Diablo Immortal bug listings on April 19, 2026, with a player on Android saying they lost all 10 crests and never received the expected refund in mail. The thread is still small, and one reply points out that crest returns can sometimes take a while rather than showing up instantly. That matters, because it means this story is not “Blizzard confirmed players are permanently out 10 Legendary Crests.” It is “a fresh live report says the crests vanished and the expected recovery did not happen right away,” which is still a very bad sentence for a live-service game to wear. (thread here)

This bug category already has baggage

What gives this story real weight is that crest-loss complaints are not exactly new folklore in Diablo Immortal. Older Blizzard forum threads show similar reports from previous patches and crashes, including players saying Legendary Crests disappeared during Elder Rift issues and crests were lost from Elder Rift entries without immediate return. In some older cases, players later reported the crests did come back by mail. In others, the tone was a lot less comforting. That does not prove this new report is the same bug. It does show why players react badly the second “missing crests” appears in a thread title.

And honestly, it makes sense. Legendary Crests are not some throwaway resource players forget about ten minutes later. They are a big deal, whether someone earned them slowly, saved them carefully, or paid for them. That means even a delay in the refund flow feels awful, because the player experience is still the same in the moment: crest gone, reward gone, mailbox empty, blood pressure rising.

Diablo Immortal keeps coming back to reward-trust problems

This also lands in a game that has already been collecting too many stories about rewards and progression systems behaving badly. We recently covered how a legendary gem reportedly vanished after a Rift, how a Leviathan Surge upgrade allegedly consumed 9,000 sigils and gave nothing back, and how Survivor’s Bane rewards were reportedly claimable more than once. Different symptoms, same broad problem: Diablo Immortal keeps drifting into stories where players are not sure the reward systems can be trusted to behave normally.

Fresh report, small thread, very sensitive issue

To be fair, nobody should oversell this. Right now, this is still one fresh public report with limited follow-up, and the most grounded reading is that the player says the crests were lost and the mail refund had not arrived by the time they posted. But that is already enough for a real story, because this is one of those bug categories where even a single live complaint has weight. When a game tied this closely to crests, gems, and monetized progression starts eating premium-adjacent items, people notice immediately.

At this point, Diablo Immortal does not just need its Elder Rift systems to work. It needs players to stop feeling like every time they slot valuable crests, they are handing their account over to a haunted vending machine.

Read More

Diablo Immortal Players Say Gem Upgrade Numbers Look Wrong

 

Diablo Immortal has another gem-related complaint on the table, and this one lands in exactly the sort of menu where players really do not want ambiguity. A fresh bug report says either the gem description or the progressive upgrade preview is showing the wrong numbers for a legendary gem upgrade. Which means one of two things is happening: either the text is lying, or the upgrade screen is. Neither option is exactly comforting when gems sit so close to power, progression, and wallet pain.

The report appears in Blizzard’s latest Diablo Immortal bug listings under the title “Either gem description or progressive upgrade preview has wrong numbers”, active on April 16, 2026. The public listing is small, but the premise is nasty enough on its own. If the description for a gem says one thing and the progressive upgrade interface says another, players are left guessing which number is actually real before they commit resources. In a game built around incremental upgrading, that is not a small trust issue.

When the UI argues with itself, players stop trusting both sides

This is the kind of bug that can look boring from a distance and feel awful the second it touches your account. Plenty of systems in Diablo Immortal are already fiddly enough without the menus starting an internal argument over what your upgrade is actually going to do. If one screen shows a stat increase and another suggests a different result, the player is stuck in the middle trying to decide whether the problem is bad wording, bad preview math, or a genuinely broken upgrade path.

And yes, players will absolutely care about that more than Blizzard would probably like. Gem upgrades are not just cosmetic noise. They are one of the game’s core progression systems, and they are tangled up with time, grind, and in plenty of cases real spending. The second the UI looks unreliable there, the whole thing starts smelling expensive in the worst possible way.

Diablo Immortal keeps coming back to the same cursed room

This is also not happening in a vacuum. We recently covered how players reported a legendary gem disappearing after a Rift, how a Leviathan Surge upgrade allegedly consumed 9,000 sigils and gave nothing back, and how Survivor’s Bane rewards were reportedly showing up more than once. Different bug shapes, same broad result: systems tied to rewards and progression keep looking shakier than they should.

That matters because once players start seeing a pattern, even a smaller UI-side report gets more attention than it normally would. In another game, mismatched preview numbers might be a footnote. In Diablo Immortal, it lands in a community already primed to side-eye anything involving gems, rewards, or upgrade menus.

Fresh report, small thread, bad category

To be fair, this is not proof of some giant gem-system collapse. The public report is still small, and Blizzard’s forum listing does not by itself show a huge wave of confirmations. Nobody should pretend otherwise. But this is still a very live and very sensitive category of bug. If players cannot trust the number shown on a gem description or the upgrade preview, they are not just dealing with bad UI. They are dealing with uncertainty right at the point where the game asks them to spend scarce resources.

At this point, Diablo Immortal does not just need its gem systems to work. It needs the numbers on screen to stop looking like they are negotiating with each other.

Read More

Diablo Immortal Players Say Survivor’s Bane Rewards Can Be Claimed Multiple Times, and That Is Not the Kind of Surprise Blizzard Wants

 

Diablo Immortal may have another reward problem brewing, and this one comes with a slightly different flavor of danger. Instead of rewards disappearing, a fresh player report says some Survivor’s Bane rewards can apparently be claimed multiple times. According to the post, that includes legendaries, dust, and scraps, with some rewards reappearing after others are claimed. That is the sort of bug that goes from “huh, weird” to “this could get messy fast” in about five seconds. 

The report comes from a new thread on the official Diablo Immortal bug report forum, posted on April 17, 2026. The player says they noticed that after claiming certain Survivor’s Bane rewards, others appeared again and could be taken more than once. They also admit they claimed some of them before realizing something was wrong, which is exactly how these things usually go. Nobody loads into a live-service game expecting to become an accidental test case for duplicated loot. 

This is the fun kind of bug right up until it is not

On the surface, sure, this sounds better than rewards vanishing into the void. Players are obviously going to find a duplicate-claim bug a lot more entertaining than a missing-reward bug. But Blizzard tends to treat both categories as radioactive for the same reason: if reward systems start behaving unpredictably, the whole economy around progression, grinding, and fairness starts wobbling.

That is what gives this story some weight even though the public thread is still tiny. Survivor’s Bane is not supposed to be a slot machine that spits out extra prizes because the menu got confused. If rewards are really reappearing after being claimed, then the issue is not just funny. It is the kind of thing that can turn into rollback anxiety, player paranoia, and the usual ugly argument over whether early claimers “exploited” it or just clicked what the game put in front of them. 

Diablo Immortal already has enough reward baggage

The timing also does this bug no favors. We recently covered how players reported a legendary gem disappearing after a Rift, and how a Leviathan Surge upgrade allegedly consumed 9,000 sigils and gave nothing back. Different bug category, same broader problem: Diablo Immortal keeps ending up in stories where rewards and progression systems look shakier than they should.

That is why even a one-post thread like this matters. In a calmer game week, it might just be a strange footnote. In Diablo Immortal, it lands in a live environment where players are already primed to assume that if something touches loot, gems, or claimable rewards, there is a decent chance it is about to get weird. 

Fresh report, small thread, potentially ugly category

To be clear, this is still just one fresh public report, not proof that Survivor’s Bane has turned into a free-legendaries parade for half the player base. Nobody should oversell it. But the category is bad enough on its own. When missing rewards break, players get angry. When duplicate rewards show up, players get excited for a moment and then start worrying about what Blizzard will do next. Neither outcome is especially healthy.

At this point, Diablo Immortal does not just need its rewards to work. It needs them to fail in fewer creative directions.

Read More

Diablo Immortal Players Say a Legendary Gem Vanished After a Rift, and That Is Exactly the Kind of Bug That Starts Fights Fast

 

Diablo Immortal has another progression-flavored headache on its hands, and this one hits a nerve immediately. A fresh player report says a legendary gem dropped at the end of an Elder Rift, appeared as earned, and then simply never made it into the player’s inventory. No mail recovery. No obvious fallback. Just the sort of missing reward story that makes people start checking every menu like they are trying to catch a ghost in the act.

The current complaint comes from a new thread on the official Diablo Immortal bug report forum, where one iPad Pro player says they completed a rift, saw a Leviathan gem awarded, then found it missing after leaving the run. According to the report, the item also never arrived through in-game mail, which matters because mail is usually the emergency parachute for loot problems like this. If that backup did not trigger either, the whole thing starts feeling a lot less like visual confusion and a lot more like a real reward failure.

This is the sort of bug players take personally

There are plenty of Diablo bugs people can laugh off. A weird animation. A broken tooltip. A menu acting drunk for ten seconds. Missing progression items are different. They always land harder, because they hit the ugly little intersection where time, luck, and sometimes real money all live in the same room.

That is what gives this story teeth. A legendary gem is not just some random scrap item players forget five minutes later. It is exactly the kind of reward that people remember, track, and absolutely do not want disappearing into thin air after a run that already ate their time.

It also fits an uncomfortable Diablo Immortal pattern

The bigger issue is not just one gem report. It is the pattern Diablo Immortal keeps building whenever progression or monetized-adjacent systems start acting unreliable. We recently covered how players said a Leviathan Surge upgrade consumed 9,000 sigils and gave nothing back, and how some shop bundles reportedly stopped working after the latest patch. Those are different problems, but they all feed the same mood: when Diablo Immortal touches rewards, progression, or paid systems, players are getting less willing to trust the machine.

There is older baggage here too

That distrust does not come out of nowhere. The Blizzard forums have seen older reports in the same family, including previous claims that high-value rewards dropped or were earned but never properly appeared in inventory. That does not prove every new report is part of one giant shared bug. It does mean players have seen this kind of story before, which is why even a single new gem-loss complaint can get people tense very quickly.

Fresh report, small thread, very bad category

To be fair, this is still one fresh public bug report, not proof of a massive ongoing inventory meltdown. Nobody should oversell that. But the category matters. Missing legendary rewards are one of those bugs that always look worse than the thread size, because players instantly understand the pain point. Kill things, finish run, see prize, prize disappears. That is a remarkably efficient way to make people angry.

At this point, Diablo Immortal does not just need more rewards. It needs players to feel confident that when a legendary gem shows up, it will still exist ten seconds later.

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 Players Say Band of First Breath Loot Is Still Broken

 

Diablo 4 has another loot bug on its hands, and this one is weird enough to feel almost personal. Players are once again reporting that Band of First Breath, the Spiritborn unique ring, does not always drop normally. Instead, it may fail to appear on the ground, show up only on the minimap, or get dumped into stash later as missed loot. That is not exactly the dramatic loot explosion players had in mind. :contentReference[oaicite:0]{index=0}

The latest live report is a still-active thread on the official Diablo IV PC bug report forum, where players say the ring cannot drop properly and may be “falling through the world” before being sent to stash instead. The topic was still visible in Blizzard’s latest PC bug listings on April 16–17, 2026, which makes it current enough to matter and not just some dusty December ghost. :contentReference[oaicite:1]{index=1}

This bug has been haunting the same item for months

What makes this one especially ugly is that it does not look new in the purest sense. The same item has been tied to similar complaints since at least December 2025, including reports that it would not appear normally on the floor, could not be picked up, or would only show up later in stash. Blizzard’s own Season 12 known bugs thread even includes a player note from March describing Band of First Breath as having “a strange way of generating.” That is a very diplomatic way to say your loot is acting haunted. :contentReference[oaicite:2]{index=2}

That longer history actually helps the story rather than hurting it. This is not just one player having a cursed afternoon. It looks more like one very specific unique item keeps misbehaving in a very specific way, across boss drops, obol gambling, and ordinary pickup flow. If a unique keeps refusing to arrive like a normal piece of loot, players are going to notice, especially when it is tied to a class item they may already be farming repeatedly. :contentReference[oaicite:3]{index=3}

Loot bugs land harder than they should, because they always do

There is also a reason this kind of bug annoys people more than some random UI nonsense. Loot is the heartbeat of Diablo. Players can tolerate grind. They can tolerate dry streaks. What they do not love is killing a boss, seeing evidence that an item exists somewhere in the universe, and then having to pray it turns up in stash like a late apology.

We have already covered how Nightmare Keys were sometimes failing to point players toward the right dungeon and how Flay was acting strangely with WASD input. Those were annoying. This is more primal. When loot itself starts behaving like an urban legend, Diablo 4 begins to feel less like an ARPG and more like an unreliable witness. :contentReference[oaicite:4]{index=4}

Fresh report, old smell

To be fair, this is not proof that every Band of First Breath drop is broken for everyone. But it is a fresh live report attached to an item that has already built a suspicious little trail behind it. That is enough to make it a real story, because the pattern matters almost as much as the bug itself. If the same unique keeps failing to materialize properly month after month, players stop treating it like bad luck and start treating it like one of the game’s weird little cursed objects. :contentReference[oaicite:5]{index=5}

At this point, Band of First Breath does not just need to drop. It needs to stop making an entrance like a magician who forgot the second half of the trick. :contentReference[oaicite:6]{index=6}

Read More

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