Diablo 4 Players Say Sanguivor, Blade of Zir Still Isn’t Working Right

 

A fresh reply has pushed the bug back into view

Diablo 4’s latest round of forum frustration is centered on a Necromancer unique that sounds great on paper and, according to players, still refuses to behave like it should in practice. A Blizzard forum bug report for Sanguivor, Blade of Zir picked up fresh activity again on April 2, with the core complaint staying the same: the weapon’s special effect does not appear to be fully working, especially on the Crucible version.

What players say is broken

The forum report lays out two very specific problems. First, the item is supposed to let Vampiric Curse stack up to 20 souls, but the player says the counter still stops at 8, which is the old cap. Second, Army of the Dead is supposed to unleash those stored souls, but the report says casting it does not release anything, does not reset the counter, and does not trigger the expected bonus damage. The same post says this behavior was happening across all content, not just in one activity or zone.

Why this one stands out

This is not just some vague “my build feels weird” thread. It is one of those bugs that lands badly because the item’s whole identity is tied to the effect that players say is failing. If the soul cap stays stuck at 8 and Army of the Dead does not cash those souls out, the weapon is not merely underperforming. It is tripping over the exact fantasy Blizzard sold with it. And yes, that is a rough look for a class item built around a very specific Necromancer interaction.

Blizzard has touched this item before

What makes the bug more awkward is that Blizzard has already adjusted and fixed Sanguivor-related issues before. In Patch 2.5, Blizzard buffed the item so consuming a corpse contributes 3 souls to Vampiric Curse instead of 1, and raised its damage bonus per soul. Earlier, in Patch 2.3, Blizzard also fixed an issue where the mastery ranks from Ring of Mendeln and Sanguivor, Blade of Zir could fail to function if the player did not already have ranks in those passives. In other words, this is not the first time Sanguivor has needed maintenance.

Current status looks murky

The current 2.6.1 Diablo IV patch notes include Necromancer changes and a long list of Season of Slaughter fixes, but there is no mention of Sanguivor or Blade of Zir in that patch entry. That does not prove Blizzard is ignoring it, but it does mean players reporting the issue right now do not have an official fix note to point to yet. So for Necromancer players chasing this unique, the situation feels pretty simple: the item has a cool idea, a bug report with fresh activity, and not much public reassurance attached to it. 

Read More

Diablo 4’s April Fowls Event Is Silly, Temporary, and Honestly More Fun Than It Has Any Right to Be

 

Blizzard posted a joke. Then it appears to have put the joke in the game.

Blizzard’s April 1 Diablo IV post, “A Fowl Beast Rages,” reads like pure April Fools nonsense at first glance. It describes a mountain-sized avian terror stomping through towns and roads, reappearing every few hours, and promising players not loot, but “swift death.” On paper, it looks like a fake event page written by a villager who had a very bad day around a very large chicken.

The twist is that players on Blizzard’s own forums say this one was not just a joke page. A General Discussion thread from April 1 identifies the boss as Chi’Khan, The Fowl Beast, with multiple replies describing it as a real world boss-style encounter and calling it a fun surprise. That turns Blizzard’s usual April Fools routine into something better: an actual in-game bit, not just a corporate wink and a social post.

What the event seems to include

The official post keeps the joke alive by claiming no spoils will be earned, but forum reactions suggest there was more to it than a novelty kill. Players in the same thread reported getting items from the fight, and one poster pointed to a free emblem in the shop tied to the event. That does not make this some giant seasonal content drop, but it does make it more than a throwaway gag.

Blizzard’s Diablo social account also framed it as an “April Fowls” event rather than just a one-line prank, which helps explain why the community reaction skewed more amused than annoyed. That is a pretty useful distinction in a live-service game, because players can usually tell when they are being given a joke and when they are being given something playful to actually log in for.

Why this silly little event matters

Diablo IV has not exactly built its reputation on being loose, weird, or unexpectedly funny. So seeing Blizzard drop a giant chicken boss into Sanctuary, even briefly, stands out more than it probably should. The event seems to have landed because it feels lightweight in the right way. No spreadsheet required. No long explanation thread. Just log in, find the absurd bird monster, and enjoy the fact that someone at Blizzard was clearly allowed to be a little unserious for once.

A rare case of Diablo doing the joke and the follow-through

That may be the real takeaway here. April Fools posts are cheap. An actual timed in-game joke boss is better. Diablo IV’s chicken nonsense is still nonsense, but at least it is interactive nonsense. And in a game that can sometimes feel determined to keep a straight face, that is a surprisingly decent change of pace.

Read More

Diablo II: Resurrected’s 3.1.2 Patch Is Small, Practical, and Exactly the Kind of Cleanup Update the Game Needs

 

A patch with no fireworks, just fixes

Blizzard has pushed Diablo II: Resurrected patch 3.1.2 for Reign of the Warlock, and this one is very much a nuts-and-bolts update. No flashy system reveal, no giant feature headline, no dramatic seasonal shake-up. Just a short list of fixes aimed at crashes, disconnects, UI sizing, graphics issues, chat names, Blood Oath, and Warlock pets.

That may not sound exciting, but honestly, that is part of the appeal. Diablo patch notes sometimes read like a full legal brief written by a sorcerer. This one is refreshingly blunt. Blizzard is trying to sand down a handful of rough edges instead of pretending every update needs to reinvent the cathedral.

What Blizzard actually changed

According to Blizzard’s official notes, 3.1.2 fixes “various crash and disconnect issues,” along with “various resolution and UI panel sizing issues” and “various graphics rendering issues across multiple areas.” It also fixes a bug where a player’s Battle.net tag could appear in chat instead of their character name.

On the class and gameplay side, Blizzard says it fixed an issue where players could retain Blood Oath even after losing all skill points, and another where Warlock pets could die when Blood Boil was used multiple times in a short window. On top of that, Blizzard reduced the visual intensity of Warlock Death Hex status effects and updated the number of daggers available from vendors.

Why this patch matters more than it looks

None of those fixes are headline monsters on their own, but together they hit a pretty useful spread. Stability fixes matter because crashes and disconnects are the kind of problem that can instantly sour an otherwise solid session. UI and rendering fixes matter because Diablo II: Resurrected lives and dies by clarity more than people like to admit. When the interface misbehaves or the visuals get weird, the game starts feeling older in the wrong way.

The class-specific fixes are arguably the more interesting part. If Blood Oath could stick around when it should not, that is not just visual clutter or menu weirdness. That is gameplay logic getting sloppy. The same goes for Warlock pets dropping dead from repeated Blood Boil use. Those are the kinds of bugs players notice fast, especially in a game where build behavior matters more than marketing copy.

The kind of update that keeps the machine running

Blizzard’s news feed lists the patch as a fresh April 1 update for Diablo II: Resurrected, and that timing matters because it shows the team is still actively maintaining Reign of the Warlock with quick cleanup passes. It is not glamorous work, but it is the work that keeps a live game from feeling neglected.

And really, that is the honest read on 3.1.2. It is not the patch that gets framed and hung on the wall. It is the patch that quietly makes the room less crooked. In Diablo terms, that counts.

Read More

Diablo II: Resurrected Players Say Today’s Steam Patch Is Breaking the Game

 

A patch meant to clean things up seems to have knocked some players offline

Diablo II: Resurrected got a fresh 3.1.2 patch on April 1, with Blizzard listing fixes for crashes, disconnects, UI sizing, graphics rendering, chat names, Blood Oath, and Warlock pet behavior. On paper, that sounds like a tidy little maintenance patch. In practice, some Steam players say it did the exact opposite by making the game stop launching altogether.

The main complaint showing up across Blizzard’s D2R forums is blunt and ugly: after the update, the Steam version throws “Initialization Error: Failed to initialize data (corrupted?) — Error Code: 1” on startup. Multiple players say the game was working fine before the patch and broke immediately afterward, which is never a great look for a stability update.

What players are reporting

One detailed Technical Support thread says the player already tried the usual ritual sacrifices to the PC gaming gods: verifying files, deleting config files, deleting the saved-game folder, reinstalling, running as admin, flushing DNS, and reinstalling Visual C++ packages. According to that report, none of it fixed the startup error. That matters because it makes this look less like one bad local install and more like a patch-side problem affecting at least part of the Steam audience.

The issue also spilled into General Discussion, where other players reported the same launch failure and tied it directly to the new Steam build. By later replies in Blizzard’s update thread, community members were already passing around a manual .build.info workaround, and several players claimed that fix got the game running again, including on Steam Deck. That is useful for affected players, but it is also the kind of sentence Blizzard probably doesn’t want attached to a routine patch day.

Why this one lands badly

A launch-breaking patch is always worse than a boring patch. Nobody gets excited about UI fixes, but at least those let you play the game. When the “fix various crash issues” patch becomes the patch that stops the client from opening, people notice. Fast.

There’s also an awkward bit of timing here. Blizzard’s official patch notes present 3.1.2 as a cleanup pass for Reign of the Warlock, not some risky overhaul. So if Steam users are getting bounced at launch with Error Code 1, this is less “new feature teething pain” and more “the patch tripped over its own boots on the way out the door.”

Right now, the forums are ahead of the official fix

As of the latest forum activity, players are still comparing notes, sharing the error, and testing community workarounds. Blizzard has the patch notes up, but the bigger story for some Steam users is a lot simpler: the patch is live, and the game they were planning to play tonight currently disagrees. 

Read More

Diablo Immortal’s Latest Bug Fixes Are Small, but They Clean Up Two Very Real Problems

Diablo Immortal just got one of those updates that looks tiny on paper and a lot more useful in practice. No giant rework. No dramatic content dump. Just Blizzard quietly fixing two issues that were messing with things players actually notice: missing clans on the leaderboard and a Legendary Gem event that apparently wasn’t running properly on Korean servers.

That makes this less of a flashy headline and more of a live-service reality check. Big updates get the trailer treatment. The cleanup comes later, usually with less fanfare and more value. And honestly, that’s often the part that tells you whether a game is being maintained properly or just decorated aggressively.

What Blizzard fixed

On Blizzard’s official all-platform Diablo Immortal bug-fix page, the March 31 update lists two gameplay fixes. First, Blizzard says it fixed an issue where some clans were no longer appearing on Clan Leaderboards. Second, it fixed an issue where the Leviathan Tomb Legendary Gem Drop Pool 50% drop rate event was not active on Korean servers. That is a pretty short list, but neither issue is especially trivial if you’re the one getting hit by it.

Why these two issues matter

The leaderboard fix matters because clan visibility is the kind of thing players expect to just work. If your clan disappears from rankings, that doesn’t feel like a small UI hiccup. It feels like the game forgot you exist, which is not ideal in a system built around competition, status, and coordinated group play.

The Leviathan Tomb fix is even more pointed. Blizzard introduced Leviathan Tomb as part of March’s broader The Taking update, which also brought a new main quest, a new equalized PvP mode called Challenge of Equals, Battleground changes, and other live-service additions. So if a drop-rate event tied to one of that update’s new Legendary Gems wasn’t actually active in Korea, that’s the kind of post-launch miss Blizzard pretty much has to clean up quickly.

A small patch can still say a lot

This is not the kind of patch that changes the shape of Diablo Immortal. It is the kind that keeps the floor from getting slippery. And for a game that runs on events, progression systems, and recurring reasons to log back in, that matters more than the patch-note word count might suggest. Sometimes the most important update is the one that stops the live-service machine from quietly dropping bolts in the background.

Read More

Diablo 4 Players Say Season 12 Still Has a Lag Problem, and EU Ping Complaints Are Getting Hard to Ignore

Diablo 4’s latest problem isn’t flashy, and that may be exactly why it’s so annoying. No broken mythic. No missing spark. Just the old live-service classic: you press a button, the game thinks about it for a while, and by the time anything happens, something has already killed you.

Fresh Diablo IV forum threads suggest Season 12 is still wrestling with lag, rubberbanding, freezes, and ugly latency spikes. One U.S. bug report, active again on April 1, describes freezes, stuck animations, delayed damage, enemies popping in late, and interactions failing every few seconds. The same thread says the issue was happening regardless of activity and made the game “simply not playable” for that player on America West.

A separate Technical Support thread points to a more specific EU headache. Players there say latency started swinging wildly after patch 2.6.1, with reports of ping jumping from around 60 ms to 300 ms and, in some cases, even 500 ms. One reply claims EU players may be getting routed into the wrong data centers, which would explain why a zone can feel fine one minute and fall apart the next. That’s still a player theory, not an official Blizzard diagnosis, but it does line up with the kind of “works until you change instance” misery people keep describing.

This also doesn’t look like one isolated post blowing off steam. On the EU Diablo IV forums, multiple lag-related threads were sitting near the top of recent topics on March 29 through April 1, including “High latency, unplayable,” “Unplayable Lag in Diablo 4,” and the less poetic but very direct “Serwer Lag support fix the servers.” Sometimes the community writes your subheadline for you.

What makes this stick is the timing. Blizzard’s 2.6.1 patch went live on March 24 and included a long list of Season of Slaughter fixes, dungeon fixes, and reward fixes. What it did not include was any broad networking or server-latency fix tied to the complaints players are still surfacing now. That doesn’t prove the patch caused the problem, especially since the U.S. instability thread began before 2.6.1 landed, but it does suggest the season’s stability issues haven’t been cleanly put to bed.

When latency becomes the real boss fight

Season 12 was supposed to be about slaughterhouses, bloodied sigils, and pushing harder content. Instead, for some players, the toughest mechanic in Sanctuary is still the server deciding whether your inputs count today. And that’s not dark fantasy. That’s just bad netcode with a better art team. 

Read More

Diablo 4 Players Think Mother’s Blessing Ended Early, but the Tree Event May Be the Real Problem

Something odd hit Diablo 4 on April 1, and for once the joke doesn’t seem intentional. Players began reporting that Mother’s Blessing no longer looked active, with one forum thread saying the bonus appeared to be gone on Xbox and another claiming the extra Tree of Whispers cache had stopped dropping entirely. Both threads popped up on Blizzard’s Diablo IV forums the same day and quickly landed among the game’s latest active discussions.

The immediate complaint is simple: turn in Grim Favors, get normal rewards, and then… nothing extra. That matters because this kind of event is supposed to be a small but useful accelerator, not another thing players have to troubleshoot between nightmare dungeons and stash cleanup. One player report frames it as Mother’s Blessing ending early, while the bug-report version focuses more narrowly on the missing bonus cache from the Tree of Whispers.

Here’s where it gets messy. In Blizzard’s earlier official Mother’s Blessing runs, the event has included boosted XP and gold alongside bonus caches tied to Tree turn-ins. But current community coverage around the March 2026 event says Gift of the Tree was only scheduled through March 31, while Mother’s Blessing itself was expected to continue through April 7. In plain English: players may have been stacking two overlapping events, and one of them may have quietly fallen off the calendar first.

If that’s the case, then the missing extra cache on April 1 may not mean Mother’s Blessing fully ended early. It may mean the shorter Tree event expired on schedule while the longer XP-and-gold bonus kept running. That theory would fit at least part of the confusion. It also lines up with one player in the general discussion thread saying the buff still appeared to be working on PC, while others on console said it looked gone. So this may be part event overlap, part platform weirdness, or just Diablo 4 once again turning a simple bonus week into a detective quest.

A bonus event shouldn’t need patch notes-level decoding

Whether this is a real bug or just muddy event timing, the result is the same: players don’t know if they’re losing rewards because something broke or because Blizzard explained two overlapping events badly. And in a live-service game, that distinction matters. Bonus weeks are supposed to bring people back. They’re not supposed to make everyone stare at their buff bar like it owes them money.

Read More

Diablo 4 Players Say Blood Maiden Is Not Giving Grim Favors

Diablo 4’s Season 12 bug pile is still growing, and the latest complaint hits a system players touch constantly during Helltide farming. A new PC bug report posted on March 30 says killing the Blood Maiden is not awarding Grim Favors at all, even after multiple kills across two different characters. The report is short, but the problem it describes is not. If a Helltide boss stops feeding Whisper progress, one of Diablo 4’s most routine reward loops starts breaking down.

What is happening

According to the report, the player killed Blood Maiden four times total — twice on one character and twice on another — and still got no Grim Favors. One character was already sitting at 9 Grim Favors, while the other had none, which makes the complaint a little more useful than a vague “something felt off” post. The report also says it happened on version 2.6.1.71172. As of March 31, the thread was still visible in the live PC bug-report index, which means it is part of the current Season 12 complaint flow and not some buried old post dragged back up later.

Why it matters

This one matters because Grim Favors are not side fluff. They are tied directly to Tree of Whispers progression and the broader reward loop that keeps Helltide and related activities feeling worth the time. Blizzard has previously treated Grim Favor pacing and Helltide reward structure as important enough to tune in patches and PTR notes, including changes meant to make it easier to earn 10 Grim Favors within a Helltide window. If Blood Maiden kills are now failing to grant that progress, the issue lands right in the middle of a system Blizzard has already spent time refining.

There is also some history here. Blizzard has fixed Blood Maiden-related Helltide issues before, including a past bug where defeating the Blood Maiden after a Helltide ended would not progress an associated quest objective. That does not prove this is the same bug returning, but it does show Blood Maiden progression problems are not entirely new territory for the game.

Current status / what Blizzard said

So far, Blizzard’s public Season 12 List of Known Bugs does not appear to mention Blood Maiden failing to grant Grim Favors. The official list covers issues like Slaughterhouse problems, missing NPC text, Paladin bugs, and Bloodsoaked aspect roll problems, but not this specific Helltide/Whisper complaint. That means there is no public workaround or official acknowledgment for it in the main roundup yet.

When routine farming stops paying out

A missing spark is dramatic. A broken boss fight is obvious. But a farm target quietly failing to give Grim Favors may be worse in a different way: players can lose progress without realizing the loop is broken until they have already wasted the run.

Read More

Diablo 4 Players Say Season 12 Still Has a Transmog and Pet-Swap Bug

Not every Diablo 4 problem this season is about missing rewards, broken damage, or failed trades. Some of the complaints hitting players are smaller on paper but still ugly in practice — especially when they affect cosmetic systems people paid into. A new PC bug report posted on March 31 says the player cannot change the appearance of their shield, weapon, or headstone, and also cannot swap pets, with the issue described as ongoing since the start of Season 12.

That makes this one more than a throwaway wardrobe annoyance. Cosmetic friction tends to get dismissed until it touches things players actually use every session, and in Diablo 4 that includes pets, mounts, portals, weapon skins, and individual armor looks. If those systems stop responding correctly, part of the game’s customization layer starts feeling jammed shut.

What is happening

The fresh March 31 report is short and direct, but it lines up with a wider pattern from earlier in the month. On March 11, another PC bug thread said players could not select individual armor skins, could not equip pets, and could not select weapon skins or effects properly. That same thread also described a specific wardrobe problem where clicking once could apply the full set/theme instead of just the chosen piece.

A separate general-discussion thread from March 11 described similar symptoms: no pet selection, no mount changes, and individual clothing pieces behaving incorrectly. By March 12, players in that thread were already sharing temporary workarounds, including holding left click and tapping space bar to get some appearance changes to register. Another bug thread described a similar mouse-button workaround for pets, mounts, portals, weapons, and shields, while noting that armor-piece transmog still remained broken.

Why it matters

This matters because the problem seems to cut across both convenience and monetized customization. One March 12 post explicitly tied the bug to frustration over a Reliquary purchase, with the player asking about refunds after saying they could not use pets, transmogs, or mount changes. Even if that is just one player’s reaction, it shows why cosmetic bugs hit differently when they overlap with paid systems.

Current status / what Blizzard said

So far, Blizzard’s public Season 12 known bugs roundup does not list this transmog/pet issue in its main bullet list. Players did raise the problem inside that known-bugs thread on March 14, mentioning broken transmog selection, pet choice, and mount issues, but it does not appear as one of the officially summarized items in the top post.

When “just cosmetics” stops being minor

A broken reward stings. A broken build hurts. But when Diablo 4 starts fighting players over how their character even looks, the season starts feeling messy in a different way — and a lot more personal.

Read More

Diablo Immortal’s New Update Goes Live With Better Matchmaking, Refined Cosmetics, and a Fresh Reward Push

Diablo Immortal has a new update rolling out, and for once the cleanest Diablo story of the day is not a bug report. Blizzard’s latest content update, “Become Sanctuary’s Undoubted Savior,” began server maintenance on March 31 for Europe and other non-Americas regions, with Americas maintenance following on April 1, bringing a new reward event, matchmaking changes for top-ranked PvP, Battle Pass cosmetic upgrades, Battleground tweaks, and a pair of timed events for April.

That makes this a useful reset point for Immortal players who have mostly been watching class balance debates, PvP complaints, and live-service fatigue pile up in the background. This update is not a full expansion-sized shake-up, but it does touch enough meaningful systems to matter, especially if you play regularly and care about rewards, queue quality, or Battle Pass value.

What is happening

The headline feature for many players will be Winds of Fortune, which runs from April 9 to April 16 local server time. During the event, players can activate a 24-hour buff that boosts rewards, including duplicate drops for things like Gold, Experience, Battle Pass Points, Normal Gems, and Legendary Items. Blizzard also says rewards from activities such as Horadric Bestiary, Challenge Rifts, Bounties, Fishing, Dungeons, Purge the Depths, Accursed Towers, Hidden Lairs, wilderness farming, and Codex Activities can also drop in duplicate quantities during the event.

Blizzard is also adjusting Legendary Rank matchmaking to improve what it calls competitive integrity. Player overall power is now once again included in matchmaking for Legend rank and above, affecting Assault, Convoy, and Tower War. According to Blizzard, that check had been removed in the past to reduce queue times, but is now being restored to improve match quality.

Why it matters

That matchmaking change is probably the most important long-term part of the update. Bonus rewards are nice, but ranked matchmaking is where live-service frustration tends to harden into player resentment. If higher-end matches feel more balanced, that does more for Immortal’s day-to-day health than another short burst of extra loot.

The update also continues Blizzard’s newer Refined Battle Pass cosmetics system. Blizzard says the first Refined Battle Pass cosmetic set arrives in Battle Pass Season 51, following the multi-season progression introduced in Season 50 where cosmetics can be earned, refined later, and eventually unlocked for additional classes.

Current status / what Blizzard said

Blizzard has also added two timed events to the update window: Spring into Action from April 1 to April 16, and The Hells Quake from April 9 to April 18. Battlegrounds are also getting mechanical changes, including healing zones dealing continuous damage to enemies and updated Idol progress tracking for Spirit of Corvus.

A quieter kind of Diablo update

This is not the loudest Diablo patch of the year. It is just one of the cleaner ones: more rewards, more structure, and at least one system fix that could actually improve how the game feels to play.

Read More

Diablo 4 Players Say Wildbolt Aspect Is Stuck at 3.5 Seconds No Matter the Tier

 Diablo 4’s Season 12 bug flow keeps drifting back to one familiar pressure point: item systems that do not seem to scale the way players expect. The latest complaint is smaller than a missing reward cache or a failed trade, but it hits the same nerve. A new PC bug report posted on March 30 says Wildbolt Aspect is stuck at a 3.5-second cooldown even when the player has the highest Codex tier unlocked.

What gives the report some weight is how specific it is. The player says the cooldown stays at 3.5 seconds whether the aspect is applied to an Ancestral, Blessed, or normal Legendary item. That suggests the complaint is not about one bad drop or one oddly rolled piece of gear. It is being framed as a broader scaling problem tied to the aspect itself.

What is happening

The forum post is short, but the core claim is clear: the player unlocked the highest Wildbolt tier and expected the cooldown to improve, yet the aspect allegedly remains fixed at the same number every time. As of March 30, the thread also appears in the live Diablo IV PC bug-report index, which puts it alongside the current wave of Season 12 issues players are actively posting about right now.

Why it matters

Cooldown scaling on aspects is not just flavor text. For players building around a specific interaction, the difference between the intended top-end value and a stuck baseline can change how reliable a setup feels in actual play. Even if this turns out to be a narrow issue, it lands in a season where players are already watching aspect behavior closely after Blizzard publicly acknowledged other Season 12 aspect problems, including Bloodsoaked Legendary items receiving only the minimum aspect value from the Occultist regardless of unlocked Codex tier.

That context matters because Wildbolt is not arriving in a vacuum. Another aspect issue, Wanton Rupture, has also been discussed on the forums this season as players argue that imprint behavior is not scaling correctly on two-handers and amulets. Even if the two bugs are not directly connected, they feed the same wider concern: players do not fully trust that Diablo 4’s item modifiers are behaving the way the game says they should.

Current status / what Blizzard said

So far, Blizzard’s public Season 12 known bugs roundup does not appear to list Wildbolt Aspect specifically. The official thread includes Slaughterhouse bugs, audio issues, missing NPC text, furnace-fire rendering problems, and the minimum-roll Bloodsoaked aspect issue, but not this cooldown complaint. That means there is no public fix or official workaround posted for Wildbolt yet.

When the number refuses to move

Sometimes a bug is dramatic. Sometimes it is just one stat refusing to budge. In a loot game, that can be enough.

Read More

Diablo 4 Players Say a Trade Bug Is Falsely Saying They Do Not Own Vessel of Hatred

Diablo 4’s Season 12 bug list keeps throwing up problems in the usual places, but this one hits a part of the game that players tend to notice fast: trading. A March 18 PC bug report says the game is blocking item trades with an error claiming the other player does not own Vessel of Hatred — even though, according to the report, both players actually do own the expansion. The thread picked up a fresh reply on March 30, which is why it is back on the radar now.

What is happening

The original report says the issue appeared while trying to sell an item for gold through Diablo.trade, with the in-game trade being stopped by a false expansion-ownership message. The newer March 30 reply adds a useful detail: that player said they had traded other Vessel of Hatred DLC items without trouble, and singled out Band of the First Breath as the item involved in their failed trade. That does not prove the bug is limited to one item, but it does suggest the problem may be narrower than a full trade-system collapse.

Why it matters

Trade bugs land differently from balance complaints because they interrupt a basic transaction players expect to just work. If the game is incorrectly flagging expansion ownership, then the problem is not really about Vessel of Hatred access at all. It is about the game rejecting valid trades with an error that points players in the wrong direction. That creates confusion for both sides of the trade and makes it harder to tell whether the failure is account-related, item-specific, or just another Season 12 systems issue.

The timing also matters. The thread is still visible in the current PC bug-report index as of March 30, alongside other active Season 12 complaints like missing sparks, teleport black screens, lag, and crafted Mythics showing up as non-Ancestral. In other words, this is not a dead report buried in last week’s pages. It is sitting in the middle of the live bug flow players are still posting into.

Current status / what Blizzard said

So far, Blizzard’s public Season 12 known-bugs roundup does not appear to list this false “Vessel of Hatred not owned” trade error. The current roundup includes issues with Slaughterhouse, Bloodsoaked Legendary aspect rolls, seasonal objective tracking, missing NPC text, invisible furnace fire, and other Season 12 problems, but not this trade-block message specifically. That means there is no official public workaround or fix posted for it yet in the main known-bugs thread.

When the error message is the wrong problem

That is what makes this one interesting. If players are right, the game is not failing because someone lacks the expansion. It is failing because Diablo 4 is using the expansion as the excuse.

Read More

Diablo 4 Players Say the Brutallity Reward Is Missing a Resplendent Spark

Diablo 4’s Season 12 bug trail has not slowed down much, and the latest complaint hits one of the game’s most valuable reward types. A new PC bug report posted on March 30 says a player finished the Season 12 Brutallity event, claimed every reward on the board, but never received the cache containing the Resplendent Spark. The board allegedly showed the rewards as already claimed anyway.

That makes this more than a small UI annoyance. Resplendent Sparks sit near the top of Diablo 4’s crafting economy, so when one appears to vanish after a seasonal reward claim, players are going to treat it like a real progression problem, not just another visual glitch.

What is happening

The March 30 report is very direct: the player says they completed the Brutallity event, claimed all rewards, and did not receive the spark cache even though the reward board marked those caches as claimed. The issue also appears in the current PC bug-report listings, which confirms it is part of the active Season 12 complaint cycle rather than an old thread getting resurfaced.

There is also a related Xbox report from March 20 describing a missing “Brutality Resplendent Mythic Cache / Spark” reward after the player tried to claim it. That does not prove both reports are the exact same bug, but it does suggest the missing-reward complaint may not be limited to a single one-off post on one platform.

Why it matters

Seasonal reward bugs always land harder when the missing item is rare enough to matter. Resplendent Sparks are closely tied to Mythic crafting value, which means a failed reward claim can feel like lost progression rather than bad luck. In a season already crowded with reports about missing progress, bugged rewards, and broken systems, that kind of complaint gets attention fast.

Current status / what Blizzard said

So far, Blizzard’s public Season 12 known-bugs roundup does not appear to list a Brutallity reward bug involving a missing Resplendent Spark. That means there is no official public fix or workaround posted for this specific issue in the current roundup.

When a reward board says “claimed” but the loot is gone

That is the part likely to frustrate players most. If the reports are accurate, the problem is not just that a reward is delayed. It is that the game may be marking a high-value seasonal reward as collected while the player never actually gets it.

Read More

Save 45% on Diablo: Tales from the Horadric Library — A Diablo Lore Pickup Actually Worth Grabbing

Not every Diablo deal needs to be some oversized collector item or another piece of merch that ends up sitting on a shelf gathering dust. Today’s better pickup is a lot simpler: Diablo: Tales from the Horadric Library (A Short Story Collection) is currently listed at a claimed 45% off through this Amazon deal link

For Diablo fans who actually care about Sanctuary beyond patch notes and bug reports, this is the kind of discount that makes sense. Instead of another live-service purchase that disappears into the grind, this one gives you something physical to keep. Blizzard’s own Gear Store describes Tales from the Horadric Library as an officially licensed hardcover anthology exploring the darkest corners of Sanctuary, complete with original artwork and metallic ink on its illuminated pages.

What is happening

The short version is easy: Amazon is offering a notable discount on one of the more interesting Diablo books out there, and that makes it a decent “deal of the day” candidate for anyone who likes Diablo’s world as much as its loot. If you want to check the offer directly, the deal link is here again

This is not some random tie-in paperback either. Blizzard’s Gear Store lists it as a 196-page hardcover and names contributors including Courtney Alameda, Delilah S. Dawson, Brian Evenson, Matthew J. Kirby, Barry Lyga, Catherynne M. Valente, and Tamsyn Muir. In other words, this book leans into Diablo as horror, not just as a franchise label slapped on generic fantasy filler.

Why it matters

One of the easiest traps with Diablo merchandise is paying premium prices for things that look better in a promo image than they do in real life. Books are a little different. When they are done right, they expand the setting, build atmosphere, and give the universe room to breathe outside the endless cycle of nerfs, buffs, and broken seasonal systems.

That is also why this one stands out. GameSpot highlighted the same book as one of the better Diablo reading picks, describing it as a collection of short stories written by members of the Diablo development team and horror authors.

Current status

As always with Amazon, pricing can move fast, so this is the kind of deal that is better checked sooner rather than later. But if the discount is still live when you click, it is a pretty clean pickup for lore fans, collectors, or anyone who wants a Diablo item that feels a little less disposable than another cosmetic.

Amazon link one more time

A Diablo deal with actual shelf value

There is a lot of Diablo merch out there. Not all of it deserves your money. This one at least looks like it belongs in the library of someone who knows what the Horadrim were doing before the servers started melting.

Read More

Diablo 4 Players Say Crafted Mythic Uniques Are Coming Out Non-Ancestral

Diablo 4 players are raising a new Season 12 complaint that cuts deeper than a bad tooltip. Multiple reports on Blizzard’s PC bug boards say crafted Mythic Uniques are appearing only as “Mythic Unique” instead of “Ancestral Mythic Unique,” even when they are item level 800 and roll with a Greater Affix. For players burning rare materials at the Jeweler, that is not a cosmetic detail. It can affect whether the item counts for seasonal progression at all.

What is happening

The first report landed on March 17, when one player said a newly crafted Mythic came out non-Ancestral despite having a Greater Affix. Another reply argued the item looked correct statistically, but the original poster pushed back, saying the real issue was that the item did not count toward the season objective because it lacked the Ancestral label.

A second thread appeared on March 22 with the same complaint. That player said they crafted two Shrouds of False Death, both appeared as “Mythic Unique,” and neither gave credit for Season Journey Rank VI’s “Fabled Power” objective. On March 30, another player added that they had seen the same behavior with Heir of Perdition. By March 30, both threads were still visible in the current PC bug listings, which suggests this was not an isolated one-post report that disappeared into the void.

Why it matters

This one hits a sensitive part of Diablo 4’s endgame loop: expensive crafting tied to progression. Mythic Uniques are not throwaway items, and players crafting them are usually doing so with a very specific goal in mind. If the item rolls with the right power and affixes but fails to register properly for a Season Journey objective, the problem stops looking like a naming quirk and starts looking like a systems bug with real cost attached.

It also lands in a season that is already carrying a crowded bug reputation. Blizzard’s community-known-bugs roundup for Season 12 lists problems ranging from Slaughterhouse issues to Bloodsoaked Legendary aspect rolls and seasonal objective tracking problems. That context makes players more likely to treat a Mythic labeling problem as part of a broader pattern rather than a harmless edge case.

What Blizzard has said

So far, Blizzard’s Season 12 known-bugs list does not appear to specifically mention crafted Mythic Uniques showing up as non-Ancestral. That means there is no official workaround or fix posted for this exact issue yet, at least not in the current public roundup.

When the label becomes the bug

In most loot games, labels are just shorthand. In Diablo 4, they can decide whether a costly craft actually advances your season. That is why this report matters. If players are right, the problem is not that crafted Mythics look slightly wrong. It is that a top-end reward may be failing one of the checks players need it to pass.

Read More

Diablo 4 Players Say Wolf Companions Are Breaking in Infernal Hordes

Diablo 4’s Season 12 bug board keeps finding new ways to make endgame runs feel unstable, and this time the complaint is landing on Druid players. A new PC bug report posted on March 30 says Wolf Companions can stop attacking entirely inside Infernal Hordes, even when the same setup appears to work normally in other parts of the game.

What makes this one worth watching is how specific it sounds. The player reporting the issue says they are running a wolf-focused Druid build with the Storm’s Companion Unique chest and the Aspect that turns wolves into dire wolves, but inside Infernal Hordes the companions allegedly stop functioning as expected. On the Diablo IV bug board, the thread showed up alongside several other fresh Season 12 reports on March 30, which suggests the post is part of the current wave of live complaints rather than an old issue getting bumped back to the surface.

What is happening

According to the report, the wolves seem to work fine outside Infernal Hordes, but begin breaking or refusing to attack once the player enters that activity. That distinction matters. This is not being framed as a general “companions feel weak” complaint. It is being framed as a mode-specific failure inside one of Diablo 4’s repeatable endgame activities.

Why it matters

For a companion-focused Druid, wolves are not cosmetic clutter. If they stop attacking mid-run, a core part of the build’s pressure and consistency can effectively disappear. That is the kind of issue that can turn a playable setup into a dead slot the moment a run starts. It also hits a sore spot for longtime Druid players, because companion behavior has been a recurring frustration since much earlier in Diablo 4’s life. Back in 2023, players were already reporting wolves floating, failing to engage, or getting stuck after activation.

What Blizzard has said

So far, Blizzard has not publicly listed this exact Infernal Hordes wolf-companion problem in the current Season 12 known bugs roundup. That said, the official known-bugs post does show Blizzard has already been dealing with at least one wolf-related Druid issue this season: “The Ceh rune does not summon Druid Wolves,” which is marked as fixed. In other words, wolf bugs are not exactly foreign territory right now.

One more crack in the Season 12 wall

Maybe this turns out to be a narrow edge case. Maybe it spreads once more Druid players push the mode harder. Either way, it is one more sign that Season 12’s bug list is still growing in the places players actually spend their time.

Read More

Diablo Immortal’s PvP Refresh Is Still Alive — But the Bug Board Is Starting to Crowd It Out

Diablo Immortal still has one genuinely strong selling point in its current update cycle: Blizzard is pushing Challenge of Equals as a fairer PvP format where normalized power matters more than raw account advantage. In a game that has spent years dragging pay-to-win arguments behind it, that is not a small angle. It is one of the more credible ideas Blizzard has put on the table for Immortal in a while.

The problem is that the bug board is now getting loud enough to steal the headline. On March 29, Diablo Immortal’s active bug board was showing fresh reports about Horrid Ancient Nightmare altars not charging, the in-game shop not working for over a month, and Ephemeral Treasures not appearing in the Collector’s Empowered Battle Pass. That is on top of an already-active Mt Zavain battleground objective bug and continuing Midnightmoon claim complaints.

What is happening

Blizzard’s March update sold The Taking as a broad refresh: a new main quest, the Rocky Waste zone, a Battleground update, and the Challenge of Equals tournament with power normalization rules that disable or reduce several progression-based advantages. Blizzard also said a larger Battleground seasonal refresh is coming in April 2026.

But the live bug flow looks rougher than the pitch. The newest March 29 report says the Horrid Ancient Nightmare event is “not working right” because the altars do not charge from kills, making it harder to bring down the boss shields. The Mt Zavain guide objective tied to participating in a battleground is still not progressing for some players, with fresh confirmations on March 27. Meanwhile, the PC client stuck on “Updating files 0/502” thread remained active on March 27, with one player describing a repair loop that kept the launcher from entering the game at all.

The monetization-side complaints are not helping either. One March thread says the in-game shop has not worked for over a month for some players, while another says Ephemeral Treasures still do not show up properly after buying the Collector’s Empowered Battle Pass. The Midnightmoon event claim bug is also still active, with players saying they completed the required World of Warcraft unlocks but still could not claim the cosmetic in Immortal.

Why it matters

This matters because Blizzard is trying to sell a cleaner competitive story at the exact moment the rest of the game looks messy. Equalized PvP only works as a headline if players trust the client, trust the rewards, and trust the surrounding systems enough to believe Blizzard can actually deliver a fair battlefield.

When the same board is filled with event bugs, launcher problems, reward failures, and claim-button issues, the PvP refresh starts to feel less like a big step forward and more like one good idea trapped inside a noisy technical patch window. That is an inference from the current spread of player reports, not a formal Blizzard statement.

Current status / what Blizzard said

Blizzard’s official message is still forward-looking: The Taking is live, Challenge of Equals is part of that rollout, and the bigger Battleground seasonal update is still slated for April 2026. What Blizzard has not done in those public update posts is directly address this broader cluster of active client, event, and reward complaints.

When the side problems start eating the update

Challenge of Equals is still one of Diablo Immortal’s smarter ideas. But right now, the bug board is doing everything it can to bury that fact. Fair PvP is hard to sell when too many other systems around it still look unstable. 

Read More

Diablo III Clan Tags Are Vanishing Again — and EU Players Say the Problem Is Still Not Fixed

Diablo III Season 38 is live, but not every problem around the game is tied to ladders or server load. A fresh March 29 bump to Blizzard’s Diablo III bug forum has dragged an older social bug back into view: players say clan tags are still vanishing, especially on EU, and in some cases the issue is now bleeding into clan chat as well.

That may sound smaller than a login outage, but for a game this old, the social layer matters more than it used to. If players cannot reliably see clan identity in multiplayer games or even use clan chat normally, that chips away at one of the few things still holding long-time groups together.

What is happening

The forum thread currently sitting on Blizzard’s Diablo III bug board is titled “CLAN Tags vanishing on EU servers! Most EU players affected!” The original post says many EU players have lost visible clan tags in multiplayer games, cannot see which players belong to which clan, and even lose tags inside their own clan interface. The poster also says leaving and rejoining a clan can briefly restore the tag, but only for a short time before it vanishes again.

The bigger problem is that this does not look new. The same thread was originally opened on February 17, and replies on March 28 and March 29 confirm that players still say the bug is there. One March 29 reply says several members of the same clan remain affected and adds that they cannot even write in clan chat, throwing error code 319012 instead.

There is also disagreement about scope. The thread title frames it as an EU issue, but one reply argues it is happening “across the board” and has been around for a few seasons already. That means the regional impact is still somewhat unclear, but the ongoing reports suggest the underlying problem has not gone away.

Why it matters

This matters because Diablo III in 2026 is not being held together by novelty. It is being held together by seasonal habits, friend groups, and clan-based routine. If clan tags disappear and clan chat starts failing too, the damage is not just cosmetic. It hits community glue.

It also lands at a bad time. Blizzard is trying to keep attention on Season 38: Ethereal Memory, but social bugs like this make the game feel older in the wrong way. Season hype can survive rough edges. It handles neglected community tools a lot worse.

Current status / what Blizzard said

Right now, the clearest public signal is the bug thread itself. It remains active on Blizzard’s Diablo III bug board as of March 29, with fresh confirmations from affected players. I did not find a Blizzard staff reply in the surfaced thread excerpt, so there is no visible public confirmation of a fix yet.

When the community layer starts fading out

Diablo III can survive old tech and aging systems. What it handles worse is the feeling that even basic clan identity is starting to flicker out. For a game this dependent on long-time players, that is a more serious problem than it first sounds.

Read More

Diablo 4 Players Say Loyalty Mantle Has Multiple Bugs in Season 12

Diablo 4’s Season 12 bug stream is still coughing up fresh problems, and this time the spotlight is on a specific item instead of a dungeon or activity. On March 29, Blizzard’s PC Bug Report board picked up a new thread titled “Loyalty mantle has multiple bugs,” with the player claiming the item is misbehaving in several different ways at once.

That matters because item bugs tend to land harder than minor UI annoyances. If a piece of gear is not displaying correctly, not linking correctly, and not rolling or buffing stats the way players expect, then the problem is no longer cosmetic. It starts to chip away at trust in the loot itself.

What is happening

According to the March 29 report, Loyalty Mantle is showing at least three separate issues. The player says linking it in chat only prints a text-format ID instead of creating an actual clickable item link, even though party members can still see it. They also say the item is only appearing with movement speed as the Ancestral stat. On top of that, when the item is Bloody, the only stat getting buffed is the Bloody stat, which the player says is the same every time when the item is both Ancestral and Bloody.

This is also not the first time Loyalty Mantle has shown up on Diablo IV’s bug boards. Older forum listings show reports tied to the same item in October 2024 and October 2025, including one thread titled “Loyalty Mantle not lowering Cooldown of Unstable power.” That does not prove the March 29 complaints are the same underlying bug, but it does suggest this item has had a history of trouble.

Why it matters

This matters because Diablo 4’s item game is supposed to be the part players can rely on, even when balance gets messy. If a unique item starts generating bad links, odd stat behavior, and questionable Bloody/Ancestral interactions, it becomes harder for players to tell whether they found a bad roll, misunderstood the item, or hit an actual bug. That confusion is part of the damage.

It also lands inside a wider Season 12 atmosphere that already looks unstable. On the same March 29 board view, Blizzard’s forums were showing fresh reports for Bloodmark problems, Rank VI tracking issues, black screens, and Hellish Descent access bugs. In that context, Loyalty Mantle does not look like a quirky one-off. It looks like one more system slipping at once.

Current status / what Blizzard said

Blizzard’s latest official Diablo IV patch notes, version 2.6.1 dated March 24, 2026, focus on Bloodsoaked Sigil tuning and several Season of Slaughter fixes. Those notes do not mention Loyalty Mantle or any of the specific item issues described in the March 29 thread.

When the loot starts feeling suspect

Diablo 4 can survive balance arguments. What it handles worse is the feeling that a unique item might not even be behaving like itself. If Loyalty Mantle is genuinely bugged on multiple fronts, that is the sort of problem that makes every drop feel a little less trustworthy. 

Read More

Diablo 4 Players Say Hellish Descent Is Missing From the Map in Season 12

Diablo 4’s Season 12 bug board keeps finding new ways to make basic progression feel unreliable. The latest report is not about damage, rewards, or lag. It is about access. On March 29, Blizzard’s PC Bug Report board picked up a fresh thread titled “Season 12: Unable to Enter Hellish Descent – No Map Marker / ‘View on Map’ Not Working.”

That is a nasty kind of bug because Hellish Descent is not some random side cave. Blizzard has previously listed it as one of Diablo 4’s Capstone Dungeons, with a suggested level of 50 and a specific difficulty tier attached to it. If the map marker is missing and the game’s own navigation tool fails, the problem hits progression before the player even gets to fight anything.

What is happening

The March 29 report says players are unable to enter Hellish Descent because the dungeon is not being surfaced properly through the map. The title itself points to the two key complaints: no visible map marker and a “View on Map” function that does not work as expected. Even without a long reply chain yet, the topic was visible enough to show up immediately on Blizzard’s active PC bug board and latest-topics feed the same day.

What makes this angle stronger is that Hellish Descent has history. Blizzard’s Diablo IV Patch Notes 2.5 from December 2025 specifically said the team fixed an issue where teleporting via the world map to the Hellish Descent dungeon took the player to the wrong location. The same patch also fixed a boss reset issue inside Hellish Descent. That does not prove this March 29 map-marker bug is the exact same underlying problem, but it does show this dungeon has already been on Blizzard’s fix list before.

Why it matters

This matters because access bugs feel worse than normal tuning bugs. If a dungeon is overtuned, players can complain and still attempt it. If the marker is missing and the game cannot point you there, the activity starts feeling half-removed from the season. In a patch window already crowded with Season 12 reports about Bloodmarking, item problems, Rank VI tracking, and black screens, that kind of friction lands harder.

It also cuts against Blizzard’s broader design intent. Capstone Dungeons are meant to gate progression through difficulty tiers. When one of them effectively disappears from the map, the challenge stops being the dungeon and becomes the UI.

Current status / what Blizzard said

Blizzard’s latest public Diablo IV patch notes, version 2.6.1 from March 24, focus on Bloodsoaked tuning and several Season of Slaughter fixes. They do not mention a fresh Hellish Descent map-marker issue. So right now, the clearest signal is the bug board itself: the report is live, current, and not matched by a visible official fix yet.

When the dungeon disappears before the fight

Diablo 4 can survive angry arguments about balance. What it handles worse is a Capstone Dungeon that players cannot reliably locate or enter in the first place. If Hellish Descent is slipping off the map again, that is the kind of bug that makes progression feel cursed before the run even begins.

Read More

Diablo 4 Players Say They Cannot Bloodmark in PvP Zones

Diablo 4’s Season 12 bug flow is still spitting out fresh problems, and this one cuts straight into PvP. On March 29, Blizzard’s PC Bug Report board picked up a new thread titled “Unable to bloodmark in pvp zones,” putting a basic Fields of Hatred function under the spotlight.

That matters because Bloodmarking is not some side mechanic buried in a submenu. Blizzard’s Season of Slaughter update says Fields of Hatred now revolve around the Ceremony of Slaughter, a PvP race where kills fuel Savagery and the top contender can become the Butcher. If players cannot reliably bloodmark in those zones, one of the mode’s basic PvP assumptions starts looking shaky.

What is happening

The bug board listing shows the report as a fresh March 29 topic with early replies and views already attached, which is usually how these issues start gathering momentum. At the same time, the same board is crowded with other new March 29 Diablo IV reports, including Hellish Descent access problems, Rank VI tracking complaints, and item bugs, which places the bloodmark issue inside a broader live patch mess rather than as some isolated oddity.

What makes the timing worse is the seasonal context. Blizzard’s own Season of Slaughter article says Fields of Hatred are no longer standard PvP in the usual sense. Instead, they now run a Butcher-themed event structure where kills build Savagery, push players toward supremacy, and culminate in one contender taking the Butcher’s Idol. A bloodmark problem in that environment is not just awkward. It hits an activity Blizzard is actively trying to sell this season.

Why it matters

This matters because PvP systems fall apart fast when basic participation tools stop working. If a player enters a PvP zone and cannot bloodmark as expected, the whole setup starts to feel unreliable before the fight even begins. In a season already loaded with bugs around progression, combat flow, and item handling, that kind of friction lands harder than it otherwise would.

It also risks undercutting Blizzard’s bigger seasonal fantasy. Season 12 is built around becoming more brutal, more blood-soaked, and more dangerous in Sanctuary. But if the actual PvP groundwork is misfiring, that fantasy starts to look great in the patch notes and much less convincing in live play. That last point is an inference based on Blizzard’s season design and the new bug report, not a formal Blizzard statement about the bloodmark issue itself.

Current status / what Blizzard said

Right now, Blizzard has publicly explained how the new Fields of Hatred structure is supposed to work in Season of Slaughter, but there is no visible official note in that article addressing this March 29 bloodmark report specifically. So for the moment, the clearest signal is the forum itself: the complaint is live, new, and sitting on the active PC bug board with the rest of the season’s current issues.

When PvP starts breaking before the fight

Diablo 4 can survive angry arguments about balance. What it handles worse is a PvP zone where players are already wrestling with the rules before anyone swings a weapon. If bloodmarking is genuinely failing in Fields of Hatred, that is the kind of bug that makes a whole activity feel compromised. 

Read More