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

Diablo Immortal vs Diablo 4: What’s the Difference and Which One Should You Play?

At a glance, Diablo Immortal and Diablo 4 can look like two versions of the same nightmare. Both are Blizzard action RPGs set in Sanctuary, both are built around classes, loot, and grinding demons into dust, and both keep getting live updates. But they are not trying to deliver the same kind of experience. Diablo Immortal launched as a free-to-play mobile-first game with PC support, while Diablo 4 is a premium mainline release built for PC and console, with paid expansions like Vessel of Hatred.

What is happening

The biggest difference is the basic business model and where each game wants to live. Diablo Immortal is free to download, supports mobile and PC, and is designed around ongoing updates, events, and monetized progression systems. Diablo 4 is a buy-to-play game available through Battle.net, Xbox, PlayStation, and Steam, with seasonal content layered on top of the base purchase and expansion model.

The second big split is how they feel moment to moment. Diablo Immortal leans harder into social systems, repeatable activities, and PvP structure like Battlegrounds and the newer Challenge of Equals mode. Diablo 4 is more focused on the main campaign, open-world exploration, seasonal progression, and a darker, more traditional console-and-PC Diablo atmosphere. Even Blizzard’s recent updates reflect that difference: Immortal is currently pushing PvP refreshes and equalized tournament ideas, while Diablo 4’s recent major additions have centered on expansion content, the Spiritborn class, and endgame systems.

Why it matters

This matters because the better game for you depends less on which one is “best” and more on how you want to play. If you want something free, flexible, and easy to jump into on a phone or PC for shorter sessions, Diablo Immortal makes more sense. If you want the bigger premium ARPG with a heavier campaign focus, stronger atmosphere, and the more traditional Diablo feel, Diablo 4 is the cleaner choice.

Monetization is also a real dividing line. Diablo Immortal’s design is more entangled with live-service progression and in-game purchases, while Diablo 4 asks for the upfront purchase and then builds from there through seasons and expansion content. That alone is enough to decide it for a lot of players.

Current status / what Blizzard said

Right now, Blizzard is still actively supporting both games. Diablo Immortal’s 2026 updates include The Taking and a PvP refresh built around Challenge of Equals, while Diablo 4 continues to receive live patch support and has already expanded through Vessel of Hatred. So this is not a case of one game replacing the other. Blizzard is running both, just for slightly different audiences and habits.

Which one fits you better

Play Diablo Immortal if you want free entry, mobile access, and a more event-driven live-service rhythm. Play Diablo 4 if you want the bigger premium package, the darker mainline Diablo identity, and a game that feels more at home on PC and console. Same universe, same hunger for loot, very different ways of feeding it.

Read More

Diablo 4 Players Say Bloodstained Bosses Are Breaking Bleed Damage for Flay Barbarians

Diablo 4’s Season 12 bug board has been full of progression issues, item bugs, and stability complaints. Now a newer report is hitting something more specific but potentially just as ugly for the players affected: Flay Barbarians say Bloodstained bosses are behaving strangely around bleed and damage-over-time effects, with boss health appearing to jump back up instead of ticking down cleanly.

That is not just theorycraft noise. In the March 28 bug report, the player describes three separate problems during Bloodstained boss fights: bleed seeming to “heal” in chunks, Rupture removing only a tiny fraction of the applied bleed instead of cashing it out properly, and bleed appearing to hit a cap at the triangle markers on the boss health bar.

What is happening

The report was posted on Blizzard’s Diablo IV PC Bug Report board under the title “Bloodstained Bosses and Damage Over Time.” The player says they are running a Flay Barbarian and specifically noticed the issue on Bloodstained bosses, not just in general combat. A reply from another player said they had seen something similar when using Fist of Fate, suggesting at least some players are trying to connect the bug to damage variance mechanics, though that is still community speculation rather than a confirmed cause.

The thread is also live on the active March 28 bug board rather than buried in some older archive, which matters. It shows this is part of the current Season 12 bug flow, not just a stale build complaint being dragged back up for attention.

Why it matters

This matters because DoT builds live and die on consistent damage behavior. If bleed looks like it is snapping backward, if Rupture is not consuming the stored damage correctly, or if bosses are effectively walling off bleed at health thresholds while direct damage keeps pushing through, then the build stops feeling weak and starts feeling mechanically unreliable.

It also fits the wider Season 12 mood. Blizzard’s Diablo IV bug board on March 28 was already showing fresh reports about teleport black screens, permanent Butcher stuns, rune loss, Bloodied key conversion, and other progression issues. In that environment, a Bloodstained boss DoT problem does not read like a tiny niche side note. It reads like one more system under stress.

Current status / what Blizzard said

Blizzard’s latest official Diablo IV patch notes, version 2.6.1 from March 24, say the team has been monitoring feedback and include fixes for Bloodsoaked Sigils plus several Season of Slaughter issues. Those notes do not mention a Bloodstained boss bleed or Rupture bug.

So for now, the clearest signal is still the player report itself: the complaint is new, public, and not matched by a listed official fix yet.

When the health bar starts lying

Loot games can survive balance arguments. What they handle worse is when damage stops looking trustworthy. If Bloodstained bosses really are bending bleed behavior in ways players cannot predict, that is the kind of bug that makes an entire build feel cursed. 

Read More

Diablo 4’s Teleport Black Screen Bug Looks Back — And Players Say It Is Still Forcing Hard Quits

Diablo 4’s Season 12 bug board has already spent days filling up with progression issues, combat problems, and item reports. Now another old headache appears to be back in force: players say teleporting can dump the game into a black screen that never properly resolves, leaving them stuck until they force the client closed.

That is not just a minor loading hiccup. In the newest March 28 reports, players describe the game going black after teleporting while the rest of the PC keeps running normally, with some saying the menu can still be opened but the world itself never comes back.

What is happening

The cleanest new thread is titled “Black screen when teleporting to a location on the map.” In it, the player says every teleport after updating sends the game to a black screen that does not recover, forcing them to quit out completely.

A second March 28 thread, “Constant blackscreens after teleport + disconnects,” describes a similar problem from another angle. That player says every few teleports in Seasonal play the game dies into a black screen, the OS itself remains fine, and they had to fully kill the client at least three times in one day; they also mention random disconnects happening alongside it.

This also does not look isolated to just two fresh posts. Blizzard’s PC Bug Report index currently shows multiple black-screen topics active at once, including “Latest Patch Black Screen with GUI still showing after teleport,” which had more than 500 replies and over 18,000 views by March 27, plus older threads like “Black screen after teleport” and “Black screen with Season 12 start.”

Why it matters

This matters because teleporting is not some niche edge-case mechanic. It is basic movement, pacing, and session flow. When a core travel action starts sending players into forced black screens, the bug stops feeling cosmetic and starts making the game itself feel unreliable minute to minute.

It also fits a broader Season 12 pattern. Blizzard’s current PC bug board is already stacked with fresh reports around lag, healing, item handling, progression tracking, and black-screen behavior. In that context, teleport crashes do not look like one weird technical outlier. They look like another stress point in a season already under pressure.

Current status / what Blizzard said

Blizzard’s latest official Diablo IV patch notes, version 2.6.1 dated March 24, 2026, say the team has been monitoring feedback and include fixes for Bloodsoaked Sigils, Season Rank and Capstone issues, and general stability-related problems. But the notes do not specifically call out the current teleport black-screen reports.

So right now, the clearest picture is still coming from the forums: the new March 28 threads are live, older black-screen threads remain active, and there is no listed official fix yet that clearly maps to this specific teleport problem.

When travel becomes the crash

Diablo 4 can survive rough tuning debates and bad seasonal objectives. What it handles worse is making normal movement feel dangerous to the client itself. If players start treating every teleport like a coin flip, that is the kind of bug that poisons a session fast.

Read More

Diablo 4 Players Say The Butcher Can Permanently Stun Them in Infernal Hordes

Diablo 4’s Season 12 bug board has already been busy with progression issues, key problems, and item weirdness. Now there is a fresh report that hits something even more immediate: a player says The Butcher can lock them into a permanent stun during Infernal Hordes, leaving them able to evade, drink potions, and trigger Unstable Currents, but unable to do much else until they die or get knocked free.

That is not just another awkward edge-case complaint. If an enemy can trap a character in a half-playable state during a live fight, the problem stops being balance or annoyance and starts becoming basic combat reliability.

What is happening

The report was posted on Blizzard’s Diablo IV PC Bug Report board on March 28 under the title “Butcher Permanently stuns me.” The player describes the issue happening on a Sorcerer during Infernal Hordes and says it has happened multiple times in the days since the latest patch. According to the post, the effect persists until the character either dies or gets close enough to a mass to be hit by knockback, which clears the state.

Right now, there is no visible Blizzard reply attached to that thread in the indexed forum view. But the report is clearly live on the active bug board, and it is showing up among the newest Diablo IV PC bug topics for March 28.

Why it matters

This matters because it hits core combat flow, not just seasonal bookkeeping. Infernal Hordes are supposed to be frantic, reactive fights. If a player can still move a little, drink potions, and trigger certain effects while the rest of their kit is effectively dead, that creates the worst kind of bug feeling: the game is still technically running, but your character is no longer really functioning.

It also lands in a season where Diablo IV’s bug board is already stacked with fresh reports. On the same March 28 board view, Blizzard’s forums are also showing black-screen threads, Rank VI tracking complaints, rune-loss reports, and Bloodied key conversion bugs. That broader context makes this Butcher report feel less like a weird one-off and more like another crack in a messy seasonal patch window.

Current status / what Blizzard said

Blizzard’s latest official Diablo IV patch notes are for version 2.6.1, published March 24, and they focus on Bloodsoaked Sigil tuning plus several Season of Slaughter fixes. Those notes do not mention a Butcher stun bug in Infernal Hordes.

So for now, the clearest picture is coming from the player report itself and the live bug board: the complaint is new, public, and not matched by a listed official fix yet.

When the fight stops working

Diablo 4 can survive angry tuning debates. What it handles worse is a fight where the monster is not just deadly, but apparently capable of turning your character half-off. If that Butcher bug starts spreading, players will remember it fast. 

Read More

Diablo III Season 38 Has a Leaderboard Problem — and It Is Showing Old Soul Shard Data

Diablo III Season 38 only just went live, but some players are already looking at leaderboards that do not seem to belong to this season at all. Fresh reports on March 28 say the Season 38 boards on console are showing old Soul Shard-era results instead of clean data for the new Ethereal Memory season.

That is a bad look this early. Season 38 is supposed to be about Ethereals returning on a fresh ladder, not players opening the boards and finding numbers that appear to be stuck in the past.

What is happening

The clearest report came from Blizzard’s Diablo III forums, where a PS5 player said the Season 38 leaderboards were “not fresh for the new season” and were instead reflecting data from the last Soul Shard season. A reply from an Xbox player pushed the same concern further, saying leaderboard scores, Greater Rifts, and even one Conquest looked like they were still pulling from Season 36, with dates going back to November.

This does not look like one stray post buried in the void, either. The topic showed up in both the Console Bug Report and Technical Support sections on March 28, which at least suggests the issue was visible enough for players to raise it in more than one place right away.

Why it matters

Leaderboard issues hit harder in Diablo III than they might in a busier live-service game, because the seasonal ladder is a big part of the ritual now. Blizzard’s own Season 38 post frames this season around Ethereals, seasonal progression, Conquests, and Haedrig’s Gift rotations. If the boards are showing carryover data from a previous Soul Shard season, that muddies the competitive picture from the start.

It also creates a weird identity clash. Season 38 is an Ethereal Memory season, while players are reporting leaderboard data that appears tied to the older Soul Shard theme from Season 36. Even if the issue ends up being limited to console boards, it is exactly the sort of early-season glitch that makes a fresh reset feel less fresh.

Current status / what Blizzard said

Blizzard’s official Season 38 article says the season began on March 27 at 5 PM PDT/CET/KST and lays out the Ethereal-focused theme, but it does not mention any leaderboard problems. So right now, the evidence is coming from player reports rather than a formal Blizzard acknowledgment of the bug.

When a fresh ladder starts on old history

A new Diablo III season does not need many surprises. It mostly just needs a clean reset and a reason to grind. If players are opening Season 38 leaderboards and seeing leftovers from Soul Shard season instead, Blizzard has managed to make a new ladder feel haunted before the race has even really begun. 

Read More

Diablo 4 Players Say Bloodied Lair Boss Keys Are Converting Into Normal Keys

Diablo 4’s Season 12 bug traffic is still chewing through basic systems, and the latest report hits something players do not usually expect to second-guess: boss keys. A fresh March 28 post on Blizzard’s PC Bug Report board says Bloodied Lair Boss Keys are being converted into normal Lair Boss Keys when picked up, instead of staying separate.

That is not just a messy inventory quirk. The player who filed the report said this is not about Sigils, but about the keys used to open boss chests, which means the problem cuts directly into how seasonal rewards are tracked and stored.

What is happening

According to the March 28 report, the issue appears when a player already has one version of the key in inventory. If they pick up a Bloodied boss key while holding a stack of normal keys, the Bloodied key can merge into the normal stack and lose its separate identity. The reverse also reportedly happened: normal keys stacked into Bloodied keys if the Bloodied version was already in inventory.

The player said a friend tested the same behavior and did not see the conversion happen, which makes the bug look inconsistent rather than universal. That may be worse in one sense, because inconsistent item behavior is harder for players to predict and harder to trust.

The report also picked up traction quickly. Blizzard’s PC Bug Report index shows the thread with 23 replies and 626 views on March 28, making it one of the more active fresh Diablo IV bug topics on the board that day.

Why it matters

This matters because Season 12’s systems are built around Bloodied variants being distinct, higher-stakes versions of existing activities and rewards. Blizzard’s 2.6.0 patch notes introduced Bloodied Sigils for Nightmare Dungeons, Infernal Hordes, and Lair Bosses, and said Bloodied content is meant to deliver stronger reward pressure than standard versions.

So if Bloodied boss keys are collapsing into normal stacks, players are no longer just dealing with clutter. They are dealing with uncertainty around whether seasonal resources are being preserved correctly at all. In a season already crowded with tracking bugs, reward issues, and progression blockers, that is a bad look.

Current status / what Blizzard said

Blizzard’s latest Diablo IV patch notes, 2.6.1 from March 24, include multiple Season of Slaughter fixes and general stability improvements, but they do not mention Bloodied Lair Boss Keys converting into normal keys.

So for now, the clearest signal is the bug board itself: the report is live, active, and not matched by a listed official fix yet.

Short closing paragraph

Loot games can survive balance complaints. What they handle worse is the feeling that reward items might quietly change into something else once they hit your inventory. That is the kind of bug that makes even routine pickups feel suspect. 

Read More

Diablo 4 Players Say Runes Are Disappearing After Unsocketing at the Jeweler

Diablo 4’s Season 12 bug traffic is not slowing down, and the latest complaint hits a part of the game players tend to take personally: their items. A fresh March 28 post on Blizzard’s PC Bug Report board says runes can disappear after being unsocketed at the jeweler in Cerrigar, turning a normal gear-management step into something that looks a lot more expensive than it should.

That is the kind of bug players remember fast. A broken objective is annoying. Losing socketed runes while trying to move them into new gear feels a lot closer to having progress eaten by the game itself.

What is happening

The March 28 thread is not a one-off listing with no traction. Blizzard’s bug board shows the post drew replies and several hundred views the same day, which is usually enough to get attention when the issue involves disappearing item components. The thread title is blunt: “Runes disappeared after unsocketing at jeweler vendor in Cerrigar.”

There is also a reason this report lands harder than a random new bug. A similarly titled Diablo IV bug thread from October 2024 described the same basic problem, with players saying runes vanished after being removed at a jeweler and could not be found in the socketables tab afterward. That does not prove the March 28 report is the exact same underlying bug, but it does suggest this is not a brand-new kind of complaint appearing out of nowhere.

Why it matters

This matters because rune handling sits inside one of the most routine loops in the game: upgrade item, move socketables, keep going. If players start thinking unsocketing itself is risky, that introduces distrust into basic inventory management, not just endgame optimization. In a season already crowded with reports around progression, trade, and stability, item loss bugs hit especially hard because they make ordinary actions feel unsafe.

It also feeds a wider Season 12 pattern. Blizzard’s current PC bug board is stacked with fresh reports involving Rank VI objectives, Bloodied key conversion, lag, healing problems, and trade issues. The rune story fits into that same atmosphere: another small system that players expect to just work now drawing bug traffic instead.

Current status / what Blizzard said

Blizzard’s latest Diablo IV patch notes, version 2.6.1 from March 24, include Season of Slaughter fixes, reward fixes, and general stability improvements. They do not specifically mention rune loss after unsocketing at a jeweler.

So at the moment, the clearest signal is the bug board itself: players are reporting the problem, the post is active, and there is no matching fix in the latest official notes yet.

When gear management starts feeling cursed

Loot games can survive balance drama. What they handle worse is the feeling that your items might vanish during normal maintenance. If that fear starts spreading, even a jeweler visit begins to feel like a gamble. 

Read More