Diablo 2 Resurrected PTR Herald Loot May Be Overtuned

 

Blizzard spent the last stretch of Diablo II: Resurrected feedback hearing that the new Herald system felt stingy, slow, and a bit like doing paperwork in a graveyard. Now the PTR may have pushed things hard in the other direction. A fresh Diablo II: Resurrected forum thread says testers farmed Heralds for about 12 combined hours and came away with a loot pile that included 32 Rainbow Facets, 2 Stones of Jordan, 7 Raven Frosts, a Mara’s Kaleidoscope, and more. That is not exactly “one nice drop if you behave.” That is PTR loot starting to look like it found the emergency wine cabinet.

Why players think Herald loot may be overtuned

The reaction is not coming out of nowhere. Blizzard’s official PTR 3.2 notes say Heralds now have a better shot at dropping Latent Sunder Charms starting from Tier 2 instead of Tier 4, that the drop chance is no longer heavily modified by player count, and that if a Herald fails to drop a Latent Sunder Charm, it now has an increased chance to drop “something desirable instead, like a charm or amulet.” Blizzard also says the goal is for players to have a very high chance of seeing both a Tier 1 and Tier 2 Herald in a single Terrorized Zone. That is a lot of pressure being added to one farming loop all at once. 

This is funny because the mood was the exact opposite a minute ago

That is what makes the story click. Diabloz already covered how players were tearing into the Herald system for wasting time and not paying out enough. The forum mood then was basically “why am I doing this?” Now the live PTR discussion has active threads like “Herald drops are……” sitting near the top of General Discussion while players debate whether Herald farming is suddenly too rewarding. Diablo II does love making the community choose between famine and absurdity, with very little polite middle ground. 

To be fair, this is PTR territory

That disclaimer matters. PTR loot is not the same thing as final live balance, and Blizzard often uses these windows to test systems while players stress them in ways no sane human being would normally schedule. There is also disagreement in the thread itself, with some players arguing Heralds already had good elite-unique loot and that the real difference now is simply that Heralds are spawning more often and getting farmed more aggressively. So no, this is not proof Diablo II: Resurrected has permanently turned Heralds into jackpot vending machines. But it is a very fair sign that Blizzard’s fix for “Heralds feel bad” may currently be landing closer to “Heralds feel drunk.”

Read More

Diablo 4 Barbarian Dagger Drops Look Bugged

 

Diablo 4 has another fresh loot-table headache on the board, and this one is almost funny until you remember it is happening in a game built around showering players with gear. A new official PC bug report says Barbarians are getting dagger drops during Season 12, even though the player says those daggers are unusable on the class and appear in red. The stranger part is that these are not just random daggers falling out of the sky for no reason. The report says they are rolling with Barbarian-specific affixes, which makes the whole thing feel less like bad luck and more like the loot system wandering into the wrong class room with a clipboard and no supervision.

What the report actually claims

The April 24 thread is very direct. The player says they have been getting dagger drops “quite often” on Barbarian this season, that the daggers show up with Barbarian-specific affixes, and that they do not have another character who can use daggers. They also point out something important: other incompatible item types do not seem to be dropping the same way. That is what gives the complaint some teeth. If it were one weird item in isolation, you could shrug and move on. If one specific weapon type keeps slipping through with class-specific rolls attached, that starts to look like an actual loot-pool problem.

Why this is a bad look for Barbarian loot

Blizzard’s own Diablo IV material frames the Barbarian around its Arsenal identity, built on wielding multiple weapon types in close combat, with examples centered on things like two-handed maces and hand axes rather than daggers. So when a Barbarian is apparently receiving dagger drops with Barbarian affixes attached, the complaint is not just “I found vendor trash.” It is “the game seems confused about what my class is supposed to be using.” In a loot game, that distinction matters a lot.

It also fits the current Diablo 4 itemization mood

This lands at a time when Diabloz has already been tracking other item and reward weirdness, including the recent Mythic level-requirement confusion for alt characters. Different issue, same rotten smell: players trying to make sense of gear systems that do not feel as clean as they should. Diablo can survive harsh drop rates. What it handles less gracefully is loot that looks like it was generated by a treasure goblin with a concussion.

For now, this stays in bug-watch territory

At the time of writing, the 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 every Barbarian in Sanctuary is drowning in unusable daggers. But it is a clean enough report to watch, because the complaint is specific, class-bound, and easy to understand: if a Barbarian is getting repeated dagger drops with Barbarian affixes on them, the loot table is doing something it probably should not be doing. And in Diablo 4, players usually notice that kind of nonsense fast.

Read More

Diablo 4 Grandfather Drop Vanished After Disconnect

 

Diablo 4 has another ugly bug-watch story on the board, and this one hits the exact part of the game that is supposed to feel euphoric. A fresh official PC bug report says a player got The Grandfather from Andariel, got disconnected immediately after the drop, then logged back in to find the Mythic gone. Worse, the player says the rollback did not return the boss keys either. That is not just bad luck. That is the kind of story that makes a loot game feel like it pickpocketed its own jackpot moment.

A brutal story, even if it is only one report so far

According to the thread, this happened on the player’s 12th Andariel run. They say the Grandfather dropped, the game disconnected, and when they got back in, the item was gone from the ground and not sitting in stash either. The player also says the rollback did not refund the keys used for the run. At the time of writing, the thread is live in Blizzard’s PC Bug Report section and does not show a visible Blizzard reply yet, so this is still best treated as a single-report bug watch rather than proof of a widespread issue. But for a Mythic drop, one report is enough to make people nervous fast.

Why this one stings harder than a normal disconnect

Because this is not some random trash loot from a forgettable dungeon clear. This is The Grandfather, one of Diablo 4’s Mythic Uniques, dropping from one of the game’s marquee boss-farming targets. If you are running Andariel, you are already deep in the grind loop and burning resources for a shot at exactly this kind of payoff. Diabloz has covered how the Ritual of Anguish works for Andariel farming, and that context matters here: these runs are not free, and Mythic jackpots are the whole reason players put up with the ritual in the first place.

This is exactly the sort of rollback horror story players hate

Loot games can survive bad RNG. They can survive long dry spells. What they do not survive gracefully is a moment where the rare item actually appears, then the server yanks the floorboards out and pretends it never happened. That is a very different kind of frustration because it does not feel unlucky. It feels invalidating. And right now, with players already arguing over Mythic rules and requirements, Diablo 4 really did not need a fresh story about the loot disappearing after it finally showed up.

For now, this stays in rollback-watch territory

There is no visible Blizzard acknowledgment on the thread yet, and no pile of matching reports behind it at the moment. So no, this is not enough to claim Andariel is broadly eating Mythics. But it is exactly the kind of report worth watching, because when a rare drop vanishes on disconnect and the keys vanish with it, players do not just lose an item. They lose trust in the whole boss-farm loop. In Diablo, that is a much nastier loss.

Read More

Diablo 4 Mythic Level Rules Are Confusing Alt Players

 

Diablo 4 has stumbled into another itemization mess, and this one is especially good at irritating anyone who likes gearing alts. A fresh General Discussion thread asks whether Mythic Uniques are now level 60 only after a player tried to equip one on a level 35 character and found it locked at 60 instead. That would be annoying enough on its own. The more classic Diablo 4 twist is that other players immediately replied saying some Mythics still show level 35 while others show level 60, which makes the whole thing feel less like a clean rule change and more like item logic wandering around unsupervised.

Players do not even agree on what the rule is

That is what makes this story work. In the new April 24 thread, one reply says “some pieces are Lv.60, some pieces are 35,” while older April discussion around the same issue says natural drops seem to be showing up at level 60, crafted Mythics can still appear at 35, and lower-level characters opening certain caches may still get level 35 versions. Another player even claims Mythics can jump from 35 to 60 when they are modified. None of that adds up to a clean, player-friendly system. It adds up to people trying to reverse-engineer loot rules from a pile of contradictory item tooltips.

Why alt players are the ones getting punched here

The loudest frustration is not really about one number on an item. It is about what that number does to alt progression. In the early-April discussion, multiple players say level 60 requirements “suck the joy out of leveling alts” because Mythics used to be one of the funniest ways to turn a fresh character into a temporary monster at level 35. That is not some fringe complaint either. Diablo players love hand-me-down power. Taking that away, or making it inconsistent enough that nobody knows what will happen, kills a very specific kind of fun fast.

The weird part is that Blizzard does not appear to have clearly announced this

That is where the irritation gets sharper. Blizzard’s Patch 2.6 notes do mention Mythic-related changes and bug fixes, including a fix for Mythic Uniques not dropping with Greater Affixes, but there is no obvious note in that patch summary saying Mythic equip requirements were deliberately changed from 35 to 60 across the board. That does not prove the current behavior is a bug. But when players are actively reporting mixed results and the official notes do not clearly explain the new rule, Blizzard is basically outsourcing item clarity to rumor and forum archaeology.

Right now, this looks messy more than settled

So no, this does not read like a simple “Blizzard nerfed alt fun” story with a neat little bow on it. It reads like Diablo 4 has Mythics in two or three different states depending on how they dropped, who opened what, or what got done to the item afterward. That is a bad look this close to Lord of Hatred launch prep, especially when players are already trying to sort characters, gear plans, and stash clutter before the expansion lands. Diablo can survive brutal systems. What it keeps struggling with is systems that feel like they were explained by a drunk treasure goblin.

Read More

Diablo 4 Lord of Hatred Pre-Download and Launch Times

 

If you have spent the last day asking when you can finally preload Lord of Hatred, you are not alone. Blizzard has now posted the full “Prepare for the Reckoning” launch guide, and it answers the stuff players actually care about: when pre-download starts, when the rollout begins, what is free for everyone, and what extra launch-week bait Blizzard is hanging in front of the player base. The timing matters too, because players were already asking “Where is the pre-download?” on the official forums today. 

Pre-download is up now for the platforms that matter

Blizzard says pre-download for Lord of Hatred and patch 3.0.0 began on April 23 at 4:00 p.m. PDT for Battle.net, Xbox, and PlayStation. More importantly, Blizzard also says you can pre-download the 3.0.0 patch whether or not you bought the expansion, which is useful because not everyone wants to make a purchase decision while half-awake and staring at a progress bar. If you play Diablo IV at all, you may as well get the patch loaded now instead of pretending Future You is going to handle it gracefully.

Launch starts rolling out on April 27

The actual Lord of Hatred rollout begins on April 27 at 4:00 p.m. PDT, according to Blizzard’s global launch schedule. Then, half an hour later, the Season of Reckoning kicks off at 4:30 p.m. PDT. That season is a bit of an odd duck, because Blizzard says it does not introduce a new seasonal story, theme, or gameplay gimmick. Instead, it leans on the expansion’s major system changes, including the reworked progression and broader gameplay updates, to carry the season. That is either refreshingly clean or slightly lazy, depending on how charitable you are feeling today.

There is also the usual launch-week sugar pile

Blizzard is padding launch week with a few extras. The Hatred’s Downfall Community Challenge promises the Crown of Hatred to all Diablo IV players if the community reaches 266,600,000 global Paragon Points. On top of that, Blizzard has lined up Lord of Hatred launch Twitch Drops beginning April 27 at 4:00 p.m. PDT, with additional weekly rewards following into May. So yes, the expansion is the headline, but Blizzard is also very clearly doing that live-service thing where every doorway into launch has another shiny object hanging over it. 

The useful version

Here is the clean takeaway: if you plan to play Diablo IV next week, preload now, check Blizzard’s launch map, and stop guessing. The official information is finally live, and this is one of those rare cases where the boring logistics story is actually the most useful one on the board. Sanctuary will still be full of arguments in a few days. At least your install does not have to be one of them. 

Read More

Diablo 4 Lord of Hatred Trailer Pushes the Endgame Hard

The new official Lord of Hatred launch trailer has finally landed, and the interesting thing is not that Blizzard made another expensive-looking Diablo video. Of course it did. The more useful takeaway is that the trailer phase now feels less like mystery-building and more like a blunt sales pitch for what Blizzard thinks actually matters six days before launch: Mephisto, Skovos, two new classes, and a much bigger systems reset than the average expansion usually dares to promise.

This is no longer just a story expansion pitch

Blizzard’s official Lord of Hatred page makes that crystal clear. Yes, the campaign centers on Neyrelle, Mephisto, and the corruption spreading into the sacred isles of Skovos. But the real weight of the marketing is sitting on the systems side: major skill tree reworks for every class, level-cap increases, a new loot filter, skill variants, the Horadric Cube, the new Talisman system, War Plans for endgame progression, and Echoing Hatred as a new horde-style test. That is not small-print support material. That is Blizzard telling players the expansion needs to feel like a structural shake-up, not just more cutscenes and another haunted coastline.

The trailer is really selling three things

First, it is selling Mephisto as the obvious center of gravity. Second, it is selling class fantasy hard. Blizzard is already letting players access the Paladin immediately through pre-purchase, while the Warlock is positioned as the darker counterweight and gets its own full feature spotlight in Blizzard’s Warlock class overview. Third, it is selling the idea that Lord of Hatred is where Diablo 4 finally stops tiptoeing around its broader progression problems and starts rearranging the furniture properly.

That last part is the real hook

Because honestly, Diablo 4 does not need another trailer that only says “evil is back” in a dramatic voice. It needs a reason for players to believe this expansion changes how the game feels after the credits roll. That is why the launch marketing keeps hammering endgame, customization, and class identity. Even Xbox’s store copy frames Lord of Hatred around the new campaign, Skovos, two new classes, and “major updates like an overhauled endgame, transmutation, and set bonuses.” Blizzard knows where the pressure is.

The real test starts after the trailer glow wears off

That is where Diabloz readers should probably keep their eyebrows raised. We already looked at the pre-launch prep side, and we have been tracking how skill tree overhaul talk keeps surfacing around this expansion. The launch trailer does its job well enough: it makes Lord of Hatred look big, costly, and confident. But six days from release, Blizzard is no longer being judged on vibes. It is being judged on whether all those promised systems actually land without turning Sanctuary into another bug diary with prettier lighting.

Read More

Diablo 2 Resurrected Chronicle Still Feels Unfinished

 

When Reign of the Warlock first hit Diablo II: Resurrected, the Chronicle system looked like one of the smartest additions in the whole package. On paper, it is exactly the kind of thing long-time loot goblins want: an in-game way to track uniques, sets, and runewords, plus where and when they dropped. In practice, though, Chronicle keeps showing up on Blizzard’s bug boards for all the wrong reasons. And at this point, that is starting to feel less like launch dust and more like a feature that still is not fully settled in its own skin.

The promise was great

Blizzard pitched Chronicle as a clean way to track “every item you’ve ever collected” in-game, including uniques, sets, and runewords. That is a genuinely strong idea for Diablo II, especially in a game where players have spent years building mule armies and homemade checklists like medieval tax records. The problem is that Chronicle has kept colliding with reality. Blizzard’s own known issues thread at launch already listed Chronicle bugs, including crashes, incorrect runeword labeling, and “eligible” text appearing when it should not. So yes, the warning signs were there early.

The ugly part is that the bug list did not really stop

Fast forward to April, and Blizzard’s Diablo II: Resurrected bug board is still littered with Chronicle complaints. Recent reports include found items not registering correctly, Chronicle rewards not staying selected between games, Town Portal reward issues, and players saying they have to re-enable cosmetic rewards every single session. One of the roughest reports came in March, when an offline player said their Chronicle progress dropped all the way back to 0% after previously reaching nearly 50% on uniques and 58% on sets. That is not a cosmetic annoyance. That is the kind of bug that makes collectors stare at the screen like the game just stole their weekend.

To Blizzard’s credit, some fixes have landed

This is not a case of Blizzard doing absolutely nothing. Patch 3.1.1 in February fixed several Chronicle-related issues, including the wrong runeword name showing up, the false “eligible” text, and a Nintendo Switch Chronicle crash. That matters. But it also makes the current situation more frustrating, because Chronicle is now in that awkward zone where it is clearly live, clearly useful, and still clearly unreliable for a chunk of players. That is almost worse than a feature being obviously broken, because it keeps tempting people to trust it.

Right now, Chronicle feels like a great idea with loose bolts

That is the real headline. Chronicle is still one of the best ideas in Reign of the Warlock, but the April bug traffic makes it hard to call the feature fully locked down. Some of the issues may be platform-specific. Some may hit offline harder than online. Some are clearly quality-of-life annoyances rather than total feature killers. Even so, when your item-history system forgets items, forgets cosmetics, or in the worst case seems to forget progress, players are going to stop treating it like a trophy case and start treating it like a haunted filing cabinet. For Diablo II, that is a very on-brand problem. It is also one Blizzard still needs to finish cleaning up.

Read More

Diablo 4 Missing Skill Point Bug Still Frustrates Players

 

Diablo 4 has another bug report making the rounds, and this one is not flashy enough to dominate a trailer breakdown or set Reddit on fire. It is worse in a quieter way. A fresh official PC bug report says a level 60 Eternal Druid with every renown tier completed, including Nahantu, is still stuck at 70 skill points instead of 71. After refunding everything in respec mode, the player says the game still only gives back 70 points to spend. That is the kind of bug that does not scream. It just sits there and ruins your build by one stupid little notch.

What the player is actually reporting

The new April 23 thread is pretty direct. The player says they finished every renown tier for every zone, claimed all of them, and still cannot reach the expected cap. They also note that the usual forum folklore about “level up a bit more and the points come back” is not much help here, because this character is already level 60 and sitting at cap. So this is not just a UI hiccup during leveling. It looks more like the game deciding one of the most basic build resources in Diablo 4 is optional.

This is not a new complaint crawling out of the swamp

That is what gives the story teeth. Diablo 4 players were already posting about missing skill points back in June 2023, including reports of renown rewards not properly counting and respec behavior making points seem to vanish. More recently, players were still reporting the same broader issue in January 2026 and March 2026, with max-level characters saying they were stuck on 69 instead of 71 even after hitting full renown progress. So no, this does not look like some charming new one-day glitch. It looks like one of those bugs that keeps getting dragged behind the game like a tin can tied to a hearse.

Why one missing point matters more than it sounds

In a game like Diablo 4, one missing skill point is not just a cosmetic accounting error. It can break a build path, force compromises, or lock players out of the exact setup they are trying to run. That gets even more annoying with Lord of Hatred this close, because players are already thinking harder about skill allocation, respecs, and future build planning. We have already touched on that broader pressure in our Lord of Hatred prep guide and earlier speculation around possible skill system changes. This is exactly the wrong time for the live game to be casually eating part of a character sheet.

Still a bug-watch, but an ugly one

At the time of writing, the new thread is live in Blizzard’s PC Bug Report section and does not show a visible Blizzard reply. So this is still bug-watch territory, not proof that every max-level character in Sanctuary is secretly underfunded. But when the same type of complaint keeps resurfacing across multiple years, it stops sounding like isolated player confusion and starts sounding like one of Diablo 4’s favorite bad habits. A missing skill point may be small on paper. In practice, it is the kind of bug that makes a finished character feel unfinished.

Read More

Diablo 4 Hydra Enchant Bug May Cut Sorcerer Damage

 

Diablo 4 has another fresh bug report on the board, and this one lands right on a build interaction that should feel clever, not self-destructive. A new official PC bug report says Hydra Sorcerer damage drops hard when the Hydra Enchantment effect kicks in. According to the player, normal Hydra burn ticks usually climb to roughly 110–130 million, but once the enchant-spawned Hydra appears after crossing the 200 Mana threshold, both Hydras fall to around 50 million burn ticks instead. That is not a cute little edge-case. That is your “bonus” mechanic apparently showing up with a crowbar and kneecapping the build.

What the report is actually claiming

The player says this happens specifically on a burn-focused Hydra setup that also stacks extra heads through passives and gear. Their theory is that the enchant-spawned Hydra is not being treated as a separate entity, and that its fixed head count may be overwriting the extra-head scaling on the regular Hydra as well. In plain English: instead of getting a free extra summon, the whole setup may be collapsing into a worse version of itself the moment the enchant effect procs. For a Sorcerer build built around sustained burn pressure, that is brutal.

Why Sorcerer players will care about this one fast

This is not some obscure cosmetic annoyance buried in a menu. It is a build-performance complaint, and those travel fast because players notice them immediately in boss fights, pit runs, and any content where damage consistency matters. It is also the kind of bug that feels especially dirty because the enchantment system is supposed to add power or utility, not quietly shave huge chunks off your output. If the report is accurate, Hydra Enchant is not just underperforming. It is acting like a trap option for a build that should want it.

For now, this stays in build-specific bug-watch territory

There is an important caveat here: at the time of writing, the thread is very new, sitting in Blizzard’s PC Bug Report section with no visible Blizzard reply yet. So no, this is not proof that every Hydra Sorcerer in Sanctuary is broken in exactly the same way. But it is a very clean technical complaint with clear numbers, a clear trigger, and a very obvious “this should not work like this” logic behind it. Those are usually the bug reports worth watching.

Sorcerer does not need another hidden tax

That is really the whole problem. Diablo 4 already has enough weirdness this season without builds punishing players for slotting the mechanic that looks like it should help. Diabloz has recently covered how Season 12 bugs have been making party play rougher, and even yesterday’s Duriel instant-death report involved a Hydra Sorcerer setup in the mix. If Hydra Enchant is now quietly cutting Hydra damage in half, Sorc players have every right to be annoyed. A class mechanic should not feel like a sabotage button with nice branding.

Read More

Diablo Immortal Fierce Pursuit May Be Missing Tasks

 

Diablo Immortal has another Fierce Pursuit problem on the table, and this one looks nastier than a tracker counting one kill when it should count three. A fresh official bug report says the event launched without the expected Survivor’s Bane tasks for week one, even though Blizzard’s own event breakdown lists April 22 to April 29 as the Survivor’s Bane phase of the rotation. If that is accurate, this is not just a small UI hiccup. It is the kind of thing that makes the whole event reward ladder feel crooked from day one.

What players say is missing

According to the forum post, Fierce Pursuit currently shows only Weekly Tasks and Defense of Cyrangar-related objectives, with no Survivor’s Bane tasks available at all. One reply says they completed every available objective except the “level up five times” task and still only reached 202 points, while the first week should total 282 points. That leaves a gap of 70 points, which is a lot harder to shrug off than the usual “maybe I missed one checkbox” confusion.

Why this looks bigger than one annoyed forum post

The complaint lines up with Blizzard’s own official event details, which say each week of Fierce Pursuit is built around a featured gameplay mode and specifically list Survivor’s Bane as the first week’s focus. A matching Reddit bug post is also circulating with the same basic argument: week one is supposed to revolve around Survivor’s Bane, but the event tasks do not reflect that in-game. That does not prove the entire player base is blocked, but it does make this look less like one lonely player hallucinating at the reward screen.

That is bad timing for Fierce Pursuit

It is especially bad because Diabloz already covered one early Fierce Pursuit bug tied to Castle Cyrangar boss kills not counting properly. If the event is now also missing an entire set of week-one Survivor’s Bane objectives, then Fierce Pursuit is starting to feel less like a clean limited-time reward push and more like a haunted spreadsheet wearing DOOM armor. That is funny for about eight seconds, and then players start asking whether the reward path can actually be trusted.

Another bug-watch, but a stronger one

At the time of writing, the thread is live in Blizzard’s Bug Report section, has at least one direct confirmation reply, and does not show a visible Blizzard response yet. So this still sits in bug-watch territory, not full confirmed meltdown territory. But if Blizzard told players Survivor’s Bane would anchor week one and the live event launched without those tasks, that is a pretty ugly own goal. Live-service events can survive grind. What they do not survive gracefully is math that stops adding up on day one.

Read More

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