Diablo 4 Lord of Hatred Prep Guide Before Launch

 

Diablo 4 players are six days out from Lord of Hatred, which means Sanctuary is entering that dangerous little pre-launch window where everyone suddenly becomes a build theorist, a systems analyst, and a part-time panic merchant. Blizzard has already locked in the expansion for April 28, 2026, and the last big info drop lands even sooner with a Developer Update Livestream on April 23. So if you have been half-paying attention and telling yourself you will “figure it out later,” this is your later.

Watch the April 23 stream before you make any big calls

This one is simple. Blizzard says the April 23 stream will cover the final launch details, including the new Class Skill Trees, Talisman system, Horadric Cube, and new endgame systems. That is not side material. That is the stuff that decides whether your return plan is smart or completely backwards. If you are thinking about respeccing, rerolling, or pretending you already understand the expansion meta, maybe wait until Blizzard actually finishes speaking.

Decide now whether you are buying in or just hovering around the gates

Blizzard’s official site is already pushing the pre-purchase hard, with Lord of Hatred sold as part of the broader expansion package and the site confirming that pre-purchase unlocks early access to the Paladin. If you know you are playing day one, sort that out before launch morning instead of doing the usual “why is checkout suddenly a side quest” routine. If you are not sure yet, then at least read the edition details properly instead of buying blind and getting mad at a bundle for being a bundle.

Clean your stash and your expectations

Expansion week is not when you want to discover your inventory looks like a haunted garage sale. If you are coming back for Lord of Hatred, clean out the junk now, pick the character you actually care about, and stop pretending every half-baked alt is part of some long-term strategy. Diablo 4 already has enough systems. You do not need your own account to add more chaos.

Do not marry your theories before Blizzard shows the receipts

Diabloz has already covered how players are speculating about major skill tree changes, and we also just looked at the Switch rating rumor around Lord of Hatred. Both are interesting. Neither should be treated like gospel. This is exactly the phase where Diablo discourse starts dressing guesses up as facts and then acting betrayed when reality arrives wearing different armor.

Launch week should be for playing, not catching up

The good news is that Blizzard is at least putting the key cards on the table before release. The bad news is that Diablo players are extremely talented at turning one official blog post into forty-eight hours of confused noise. So here is the clean version: watch the stream, decide whether you are buying in, tidy your account, and stop acting like expansion prep is something Future You will handle. Future You is usually an idiot.

Read More

Diablo 4 UI Freeze Bug May Force Full Restarts

 

Diablo 4 has another fresh bug report on the board, and this one is the kind that makes a basic menu feel more dangerous than a dungeon. A new official PC bug report says the game is freezing whenever the player opens core interface elements like the map, skill tree, clan menu, and season quests. That is not some obscure edge-case button hidden three layers deep. That is the stuff players touch constantly, which makes the whole problem feel less like a weird glitch and more like the UI turning traitor.

What the player says is happening

According to the April 22 report, the player says they had to restart both the game and their PC repeatedly throughout the day because opening “anything from interface” would instantly freeze Diablo 4. They also note that their internet connection appeared fine, other applications still worked when alt-tabbing, and after several minutes the game would sometimes throw up a “The game connection has been lost” message. That is an ugly combo: the client looks half-alive, the system itself is not dead, and the game still collapses anyway.

This is not a brand-new flavor of pain

That does not prove today’s report is widespread, but it does fit an old Diablo 4 habit. Back in June 2023, players were already filing reports about long freezes tied to menus and UI actions, including the social menu, clan menu, skill menu, and other routine interactions. Those older complaints described freezes lasting from roughly 20 seconds to several minutes, sometimes followed by reconnect issues and partial online functionality. Different season, same miserable smell.

Blizzard has fixed UI and freeze issues before

There is also some official context for why this one deserves a look. Blizzard’s February 2025 patch notes included multiple fixes for controller navigation problems in the Season menu, a freeze tied to leaving a dungeon during the Prologue, and broader UI, performance, and stability fixes. That does not confirm today’s bug is the same issue returning in a new coat, but it does show Diablo 4’s interface has needed real maintenance before. When a fresh thread says menus are now hard-freezing the game again, it is not exactly coming out of nowhere.

A menu should not feel like endgame content

At the time of writing, the new thread is live and does not show a visible Blizzard reply yet, so this is still a bug-watch story rather than proof of a broad outbreak. But if opening the map or season tab is enough to send players into restart hell, that is more than a cosmetic annoyance. Diablo 4 can survive balance drama and build arguments all day. A haunted interface is different. We have already seen Season 12 generate friction around quest blockers Blizzard had to hotfix and reward bugs tied to Bloodied boss loot. If even the menus are joining in, Sanctuary is getting a little too committed to the bit.

Read More

Diablo Immortal Fierce Pursuit Task May Be Bugged

 

Diablo Immortal has rolled out Fierce Pursuit as part of its larger DOOM-flavored event push, and it did not take long for the first bug report to crawl out of the floorboards. A fresh official forum post says one of the new event tasks is not correctly counting Castle Cyrangar boss kills, which is exactly the kind of problem that makes an event tracker feel less like a reward system and more like a suspicious little gremlin with a clipboard.

What players are reporting

According to the April 22 official Diablo Immortal bug report, the player started an Endless defence in Castle Cyrangar, killed three bosses over roughly 12 minutes, and had more than 20,000 points at the end of the run. The problem is that the Fierce Pursuit task only credited them with one boss kill instead of three. That is not a tiny rounding error. That is the event basically shrugging at two-thirds of the work.

The weird part is that it may not be fully broken

The same player later updated the thread with a second test: they ran another Endless defence, killed two bosses, let the mobs overrun the door, and this time both boss kills counted correctly. That makes the story more interesting and more annoying. It does not look like the task is simply dead on arrival. It looks inconsistent, which is often worse for players because it leaves everyone guessing whether they hit a bug, missed some hidden condition, or just got mugged by event logic for no good reason.

Why this one matters more than it sounds

On paper, this is just one bug thread with low traffic so far. In practice, it lands on day one of a new event that Blizzard itself describes as a rotating, reward-driven activity running from April 22 to May 13, with weekly featured modes feeding progress through the event structure. If task tracking is already acting strange on launch day, players are going to trust the reward ladder a lot less, and live-service games really do not need more trust problems right now.

Another bug-watch, not a full-blown meltdown

At the time of writing, the thread is live in Blizzard’s Bug Report section and does not show a visible Blizzard reply yet. So this is still best read as a bug-watch story, not proof that Fierce Pursuit is broadly busted for everyone. But it is a very fair warning sign. Diablo Immortal can get away with being noisy, grindy, and a little extra. What it cannot really afford is launching a fresh event and immediately making players wonder whether their boss kills count only when Sanctuary feels generous.

Read More

Diablo 4 Duriel Death Bug Has Players Baffled

 

Diablo 4 has another fresh bug report on the board, and this one hits a boss fight that is supposed to feel brutal, not paranormal. A new Diablo IV PC bug report says the player is dying instantly during the Duriel fight with nothing visibly hitting them, nothing appearing under them, and no obvious attack crossing the room. That already sounds miserable. The extra kick in the teeth is that the player says it is reliably reproducible, which moves this out of random bad-luck territory and into proper bug-watch territory.

What the report actually says

The details are specific enough to be worth taking seriously. The player says they were trying to finish the last part of the Season Journey, fighting Duriel in a group of two, with both players using the same Hydra Sorcerer build and the same gear. Yet only one of them kept getting instantly deleted “to nothing,” including after being resurrected. The same report also says the player has noticed hitbox issues elsewhere this season, but believes this Duriel problem is worse because they were clearly not standing in anything visible when the deaths happened.

Duriel has had visibility problems before

That does not prove this is a long-running Duriel bug with the exact same cause, but it does add context. Back in June 2023, players were already filing official forum complaints about the Duriel fight saying the camera could get blocked by arena geometry and that bad hitboxes around ground hazards made the encounter harder to read than it should have been. So while today’s report is not the same bug, it fits an old Diablo 4 pattern: when players cannot clearly see what killed them, the fight stops feeling deadly and starts feeling dirty.

This is exactly the kind of death that makes players stop trusting the game

That is the real issue here. Diablo players will tolerate hard bosses. They will even tolerate getting flattened when they know why it happened. What they do not tolerate for long is a death that looks like the game forgot to show its work. We have seen that frustration before in broader Diablo 4 complaints, including a January 2025 “Unknown Killer” thread where Hardcore players reported sudden one-shots with no clear source. That does not mean Duriel is caused by the same thing, but it does show how quickly invisible or unreadable deaths poison confidence in the game.

For now, this one stays in bug-watch territory

At the time of writing, the April 22 Duriel thread is live in Blizzard’s PC Bug Report section and does not show a visible Blizzard reply yet. So no, this is not proof that Duriel is broadly broken for everyone. But it is a very usable warning sign, especially in a season where Diabloz has already covered issues like quest steps soft-locking progression and world boss rewards going missing. Sanctuary is at its best when it feels cruel on purpose. “You died to absolutely nothing” is a different flavor, and it is a lot less charming.

Read More

Diablo 4 Quest Bug May Be Soft-Locking Progress

 

Diablo 4 has another progression headache on its hands, and this one is nastier than a cosmetic bug or a cursed menu. A fresh Diablo IV PC bug report says players are getting stuck on the step where they need to corrupt the Crooked Staff, Rusted Bell, and Jabbering Gemstone. According to the report, the corruption simply does not trigger, which means the questline does not move and the player is left parked in limbo like Sanctuary’s least glamorous side quest victim.

What players say is happening

The new report is blunt about it. The player says they are “soft locked” from continuing, have gone 0 for 20+ across different characters, including seasonal and eternal, and that the usual workaround ideas have not helped. There is no dramatic theorycrafting here and no grand conspiracy board with strings on it. The complaint is simple: the step will not complete, and repeated attempts are going nowhere.

This is the part that makes it harder to shrug off

What gives the story a little extra bite is that this does not appear to be some totally new one-day gremlin. A March 2025 forum post about the same three items described the same basic failure: the objects would not corrupt properly, they would not turn purple, and the next interaction would not unlock. That does not prove today’s report is widespread, but it does suggest this item step has been capable of going sideways for a long time. Some bugs are accidents. Others keep crawling back out of the crypt.

Season 12 is not exactly earning trust points here

That is why this lands a little harder than a random one-off complaint. Diabloz has already covered how Blizzard needed to push Hotfix 2 to fix the Season 12 quest blocker in “A Taste of Power”, and we have also seen players complain that Pit 100 can badly distort the season’s Bloodied farming loop. So when another report shows up with the words “soft locked” attached to it, it does not feel like harmless background noise. It feels like another crack in a season that keeps making players test the patience stat they never asked to level.

No Blizzard reply yet, just another ugly bug-watch

At the time of writing, the April 22 thread is live in the official PC Bug Report section and does not show a visible Blizzard response. That means this is still best treated as a bug-watch story, not a solved issue and not proof that every player will hit the same wall. But if a quest progression step can still randomly refuse to work after dozens of attempts, that is more than enough to deserve attention. Diablo 4 can survive players arguing about balance all day. Progression blockers are different. Those make the game feel like it is arguing back.

Read More

Diablo 4 Prestige Halo Reward Has Players Confused

 

Diablo 4’s new Tower mode was supposed to give the game’s leaderboard crowd something shiny to chase, and now some of that crowd is asking the obvious question: where exactly is the Prestige Halo cosmetic? A fresh Diablo IV forum thread asks when top players are meant to receive it, after expecting an exclusive reward for top placements. That sounds like the start of a reward bug story. It is probably not. It is messier than that, and honestly a little more annoying.

:contentReference[oaicite:0]{index=0}

Players are asking for a reward they thought was part of the deal

In the April 20 thread, one player asks about the “exclusive rewards for top 10,” specifically the Prestige Halo cosmetic. Replies quickly jump in to say the Tower currently has no rewards and that any Halo payout is not happening this season, though that part is player speculation rather than an official Blizzard statement. That distinction matters. A forum reply can explain the mood, but it is not the same thing as Blizzard actually confirming a reward timeline. Right now, players are filling the silence themselves, which is usually when things get stupid fast.

What Blizzard actually said before launch

This is where the story gets more interesting. In a Blizzard forum post summarizing a November developer interview, the team said prestige titles and “Halo’s” were planned as exclusive cosmetics for top leaderboard placements. But the same explanation also said those rewards were not immediately available because Blizzard wanted the Tower to be a high-integrity competitive space before handing out prestige items. In plain English: yes, Halos were discussed, but no, Blizzard was not saying they were ready to start raining down right away. That is a very different thing from “win now, collect now.”

The Tower launched with beta language all over it

Blizzard’s own Tower and Leaderboards Beta post did not frame the mode like a fully locked-in reward machine either. It described the Tower as an evolving beta feature, laid out the two-week leaderboard round structure, and said the team’s focus was on tuning difficulty, improving mechanics, expanding monster variety, and introducing new rewards through feedback over time. That wording matters because it points toward future reward support, not a clean promise that a Prestige Halo should already be sitting in someone’s wardrobe waiting to be claimed.

Bragging rights, just with more fine print than players wanted

So no, this does not currently look like a clean missing-reward bug. It looks more like Diablo 4 has once again managed to turn a simple expectation into a foggy little shrine of confusion. Players heard “exclusive Halo cosmetic” and naturally assumed the race would eventually pay out. Blizzard, meanwhile, seems to have treated the Tower as a longer-build competitive system that still needs work before prestige rewards really mean anything. That gap is the story. Diablo has always flirted with competitive flex culture, going back to older leaderboard obsession like the Gauntlet era we covered on Diabloz, but if Blizzard wants the Tower to matter, it probably needs to stop making top players guess whether the prize is delayed, disabled, or still living in concept art.

Read More

Diablo Immortal x DOOM Event Brings Slayer’s Reign

 

After a stretch of Diablo Immortal stories involving broken shops, missing purchases, and general live-service gremlin activity, Blizzard has finally dropped something much cleaner: a full Diablo Immortal x DOOM: The Dark Ages crossover event. It is called Slayer’s Reign, and no, Blizzard is not pretending to be subtle about it. This is basically two versions of Hell shaking hands and agreeing to make everyone’s week more violent.

What Blizzard is adding

According to Blizzard, the event runs from April 16 to May 13 and reworks Survivor’s Bane into a DOOM-flavored slaughter pit with six Slayer-inspired skills, classic weapons like the Shield Saw and Super Shotgun, and a Cyberdemon boss fight waiting at the ugly end of it. Players can also earn the new 2-Star Legendary Gem The Crucible, along with limited-time weapon cosmetics and other event rewards. In other words, this is not some lazy login bonus dressed up in crossover paint. Blizzard actually built a whole noisy little murder carnival around it.

The cosmetics are not shy either

The event is also bringing premium DOOM-themed cosmetics through the Phantom Market, including Praetor Armor-inspired sets, while Bethesda’s own Slayers Club breakdown says players can also chase Slayer Marks through event tasks for weapon transmogs and other unlockables. It even lists matching armor sets for each current class, plus crossover companions like the Serrat and the extremely unpleasant-looking Cacodemon. Diablo Immortal has always liked ornate fantasy polish. DOOM arriving to kick the door in with a shotgun feels like the game finally letting itself be a little less polite.

There is one tiny date wrinkle

Blizzard’s official post frames Slayer’s Reign as running through May 13, while Bethesda’s page says the crossover content is available until May 14 at 3:00 a.m. server time. That is probably just a timezone or end-of-event wording issue, not some great demonic conspiracy, but it is worth keeping in mind if you are the kind of player who likes cutting things close and then blaming the calendar.

For once, the noise is fun

That may be the real appeal here. Diablo Immortal has recently generated more headlines for things going missing than for things going hard. Compared with our earlier coverage of the Refined Battle Pass and Hells Quake push and the broader reward-trust weirdness hanging around events like Winds of Fortune, this one feels refreshingly straightforward. It is a crossover, it is ridiculous, and it actually fits. If Diablo Immortal is going to be extra, this is the kind of extra it should be.

Read More

Diablo 4 Bloodied Provisions Bug Still Blocking Progress

 

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

The quest sounds simple, which makes this worse

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

This is not a brand-new complaint

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

Why this one actually matters

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

Still alive, still ugly

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

Read More

 

Diablo 4’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