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

Diablo Immortal Is Still Selling Fairer PvP — But the Bug Board Is Getting Harder to Ignore

Diablo Immortal still has a smart angle on the table. With Challenge of Equals, Blizzard is trying to sell a version of PvP where normalized power matters more than raw account advantage, and that is a meaningful pitch in a game that has spent years dragging pay-to-win baggage behind it.

The problem is that the fairness pitch is now sharing space with a wider technical mess. The Diablo Immortal bug board is currently stacked with reports about the PC client getting stuck on “Updating files 0/502,” the Mt Zavain battleground guide objective not progressing, missing Bout of Realms rewards, and event claim problems tied to Midnightmoon.

What is happening

Blizzard’s March update positioned The Taking as a major step forward, tying together a new story arc, Rocky Waste content, PvP updates, and Challenge of Equals as part of a broader refresh. Blizzard also said Battlegrounds will get their first major seasonal refresh in April 2026, with new visuals and gameplay rhythm changes across Classic and Convoy maps.

But while Blizzard is pitching structure and momentum, the live bug traffic looks uglier. One March 26 report says Challenge of Equals itself may not be equalizing properly, with players describing opponents who felt massively stronger despite the mode’s normalized rules. Another thread says a player could not collect their Top 32 Bout of Realms placement reward before the event closed.

Outside PvP, the noise is spreading. A March 21 thread says the PC client can get trapped in an “Updating files 0/502” repair loop after the recent update, preventing players from entering the game at all. Another thread reports the Mt Zavain objective to participate in a battleground still failing to progress even after successful battleground wins, with new replies still appearing on March 27.

Why it matters

This matters because Blizzard is trying to push a cleaner competitive message at the exact moment the broader player experience looks messy. Equalized PvP only works as a headline if players trust the mode, trust the rewards, and trust the client enough to actually get into the game.

When the surrounding conversation fills with stuck launchers, broken progression checks, and claim-button failures, the PvP refresh risks getting buried under general instability. That is an inference from the current spread of bug 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 refresh is still coming in April 2026. What Blizzard has not publicly done in those update posts is address this latest cluster of client, reward, and objective complaints directly.

When the side problems start stealing the headline

Challenge of Equals still looks like one of Diablo Immortal’s better ideas. But a game cannot really sell fairness while too many other systems around it feel unreliable. Right now, that is the risk Blizzard is running.

Read More

Diablo III Season 38 Launches Into Server Trouble — And Players Are Already Running Into Error 395002

Diablo III Season 38 was supposed to be a clean nostalgia hit. Blizzard brought back Ethereal Memory and set the new season to begin on March 27 at 5 PM PDT/CET/KST, giving players one more excuse to dive back into an old loot ritual that still works.

Instead, the launch window has been crowded with login errors, disconnects, character-loading problems, and players trying to figure out whether the issue was local, regional, or something broader. By March 27, Blizzard’s Diablo III forums were stacked with threads about Error 395002, 395000, “game terminated” messages, and server instability.

What is happening

One of the biggest discussion threads right now is “Code 395002, anyone else?”, where players reported not being able to find heroes, failing to sign in, getting booted out of Greater Rifts, and losing progress after disconnects. The same thread also includes reports of 395000 license-loading errors, which suggests the problem is not limited to one single failure point.

Other forum posts point in the same direction. In “Servers aren’t working properly,” players described failed character loading, busy-server errors, games terminating shortly after launch, and repeated connection problems over multiple days. Another March 26 thread asked whether the issues were only hitting NA, while replies suggested Americas was seeing the worst of it, though at least some players also mentioned problems in Europe.

By March 27, the forum index was still showing active topics like “Repeated drops with ‘The game was terminated’,” “Can’t login Error 395002,” and “Retrieving Hero List,” which makes this look less like one unlucky launch hiccup and more like a messy opening stretch for Season 38.

Why it matters

This matters because Diablo III is in maintenance-mode territory now. Seasonal launches are the event. When the big draw is a returning theme like Ethereals rather than a massive expansion, a rough login window stands out even more than it would in a newer live-service game.

It also undercuts the exact mood Blizzard was trying to sell. Season 38 is built around a loot chase players already love, with 21 Ethereals to collect for permanent transmog unlocks through Ethereal Recollection. If players are spending launch day staring at error codes instead of hunting those drops, the season starts on the wrong note fast.

Current status / what Blizzard said

Blizzard’s official position is still the same in the Season 38 preview: the season launched on March 27 and is centered on the return of Ethereals. The preview does not mention these launch-day server or login issues.

So right now, the clearest picture is coming from the forums rather than a formal Blizzard service update: players are in Season 38, but not all of them are getting there cleanly. That is an inference based on the active reports, not a Blizzard confirmation of a specific outage scope.

When nostalgia meets login errors

Diablo III can still pull people back with the right seasonal hook. But on launch day, nostalgia only carries so much weight if the servers are busy throwing 395002 back at the door

Read More

Diablo 4 Trade Issues May Be Getting Worse — Not Better

Diablo 4’s Season 12 already has enough trouble without the economy wobbling too. But that is where the conversation is drifting now, as fresh PC bug reports suggest trading problems are no longer limited to one awkward item-window glitch. Players are now reporting issues with both item trading and Trade Chat, which makes the whole trading loop look shakier than it did a few days ago.

That matters because Diablo 4 does not need a giant player economy to feel the damage. If players cannot reliably move items through the trade window or even communicate through Trade Chat, then one of the game’s few remaining social market systems starts to feel half-broken.

What is happening

The most direct report is still the March 26 thread “Unable to trade items,” where a player said they tested multiple non-account-bound items and could not place any of them into the trade window. The workaround they used was dropping the item on the ground and trusting the other player to send gold afterward. A March 27 reply added that clicking the item directly in the inventory worked for at least one player, which suggests the system may be failing inconsistently rather than being fully disabled for everyone.

That would already be enough for one article. The newer wrinkle is Trade Chat. In the March 24 thread “No Trade chat on PC,” one player said they could see their own messages going out but could not see anyone else’s, and others could not see theirs either. A March 27 reply claimed the chat channel had apparently turned itself off in settings and had to be re-enabled multiple times. Blizzard’s PC Bug Report board also shows a separate March 26 thread titled “Trade Chat Completely Dead - Trapped in ‘Ghost Instance’ (No Messages In or Out),” which makes this look bigger than one isolated settings problem.

Why it matters

This matters because Diablo 4 trading is already limited compared with more open ARPG economies. When a limited system starts misfiring, the friction hits harder. If players cannot trust the item window, and they also cannot trust Trade Chat to help line up deals, the whole feature starts to feel unreliable instead of merely restricted.

It also lands at a bad time. Blizzard’s current PC bug board is crowded with Season 12 issues across progression, combat, healing, and stability. Trading problems landing in that environment do not look like a side annoyance. They look like one more system slipping at once.

Current status / what Blizzard said

Blizzard’s latest official Diablo IV patch notes for 2.6.1, published March 24, include Season of Slaughter fixes, reward fixes, and general stability improvements. They do not specifically list a current fix for these item-trading or Trade Chat reports. That does not prove Blizzard is ignoring them, but as of now, the trading complaints are still visible on the active bug board after that patch went live.

When even the market feels unstable

Season 12 does not just have a balance problem. It is starting to feel like the small systems around the edges are fraying too. And when players have to choose between broken trade tools and trust-trading items on the ground, that is a bad look for Sanctuary. 

Read More

Diablo 4 Season 12 Is Running Into a Bigger Problem Than Balance — Basic Survivability and Stability

Diablo 4’s Season 12 has already spent days buried under complaints about Bloodsoaked tuning, broken objectives, and reward issues. Now the mood on Blizzard’s PC bug board is drifting into something more fundamental: some players say the game is starting to feel unstable at the level of basic survival and responsiveness.

On March 27, Blizzard’s Diablo IV PC Bug Report board showed active threads for “Extreme lag and instability season 12,” “Defiance Aura with Rite of Prayer not healing for correct amount,” and an older “Healing and fortify suddenly not working on my paladin character” thread that was still active again today. That is not one narrow class complaint. It is the kind of cluster that makes a live season feel shakier than Blizzard probably wants.

What is happening

The lag thread paints the broadest picture. Players describe freezes, rubber-banding, stuck animations, enemy pop-in, queued attacks and damage, repeated disconnect-style behavior, and menus or interactables needing multiple attempts to work. Multiple replies say the issue happens regardless of activity and started recently enough to feel tied to the current season state.

At the same time, healing-related reports are adding a nastier edge. In a new March 27 post, one player said Defiance Aura with Rite of Prayer was healing for only 5–6 HP per second instead of the roughly 91 HP per second shown by the tooltip. The older paladin thread reports healing and fortify being “completely busted,” with healing ticking for less than 10 HP and fortify failing to register from healing at all.

Why it matters

This matters because players can tolerate a rough objective or a badly tuned activity longer than they can tolerate systems that make the game feel unreliable second to second. Lag can kill characters. Broken healing or fortify can make builds feel suddenly hollow. When both appear in the same live conversation, the season starts to look less like it has isolated bugs and more like it has general instability.

It also widens the story beyond one subclass or one mechanic. Blizzard’s own bug board today shows survivability complaints sitting alongside trading issues, progression blockers, and even reports of characters being unable to attack or cast spells. The pileup is part of the problem now.

Current status / what Blizzard said

Blizzard’s latest Diablo IV patch notes, version 2.6.1 from March 24, focused on Bloodsoaked Sigils and several Season 12 fixes, including various Season Rank and Capstone completion problems. Those notes do not specifically mention the current lag thread, the new Defiance Aura healing report, or the older paladin healing-and-fortify issue.

When survival starts to wobble

Season 12 can survive angry balance threads. What it handles worse is the feeling that core play is slipping. When players are questioning whether the game can track actions cleanly, heal correctly, or stay stable under normal play, that is a darker problem than tuning.

Read More

Diablo Immortal’s Equalized PvP Push Looks Smart — But Bugs Are Already Crowding the Conversation

Diablo Immortal may have just made its most interesting PvP move in a long time. With Challenge of Equals, Blizzard introduced a new Bout of Realms variant that normalizes player power and strips out many of the progression advantages that usually shape high-end PvP. In a game that has spent years fighting pay-to-win criticism, that is not a minor systems tweak. It is a real statement.

The problem is that the rollout is already picking up the wrong kind of attention. Fresh bug reports from March 25–26 show players complaining about missing Bout of Realms placement rewards and a “scaling anomaly” inside Challenge of Equals itself, which is exactly the kind of friction this mode could not afford on week one.

What is happening

Blizzard’s March 12 and March 16 update posts framed Challenge of Equals as a fairer competitive format. Legendary affixes and set bonuses stay active, but systems like Normal Gems, Charms, Resonance, Legacy of the Horadrim, and Ancestral Tableau do not apply. Five-Star Legendary Gems are also normalized down to Two-Star values, and Blizzard even added curated Elite Slayer Loadouts to lower the barrier to entry.

But while Blizzard was selling a cleaner battlefield, players were posting about messier reality. One March 26 bug report says a team entered Challenge of Equals expecting normalized stats, only to see a player with “significantly amplified” damage and survivability, despite the event’s equalized rules. Another March 25 report says a top-32 team reward could not be collected before the event closed, even after the player tried both PC and Android.

Why it matters

This matters because Challenge of Equals is not just another side event. It is Blizzard testing whether Diablo Immortal can make PvP feel more legitimate without tearing out the game’s existing progression structure. If that test works, it gives Blizzard a credible answer to years of criticism. If it launches with reward issues and stat-normalization doubts, the whole pitch gets weaker fast.

There is also a wider pattern here. Reward complaints tied to Bout of Realms were already showing up earlier in March, including reports that “1st in points” rewards were not handed out correctly and that server-first tournament rewards went to the wrong team. That does not prove every new report has the same cause, but it does suggest tournament reward confidence was already shaky before Challenge of Equals arrived.

Current status / what Blizzard said

Blizzard has said it will continue monitoring feedback around Challenge of Equals, and its earlier preview also confirmed a broader Battlegrounds seasonal refresh is coming in April 2026, with new visual themes and gameplay rhythm changes for both Classic and Convoy maps.

A strong idea with no room for a sloppy first impression

Equalized PvP is one of the smartest ideas Diablo Immortal has put on the table in a while. But a mode built around fairness has a very small margin for technical confusion. If players start questioning the scaling, the rewards, or both, Blizzard’s best PvP idea in years could end up buried under the same old distrust.

Read More

Diablo III Season 38 Starts Today — But Even the Launch Timing Had Players Double-Checking

Diablo III Season 38 is finally here on Friday, March 27, 2026, and Blizzard is bringing back Ethereal Memory as the season theme. That alone is enough to pull old players back into Sanctuary for another round of loot-chasing, especially with Ethereals still carrying more nostalgic weight than most of Diablo III’s maintenance-era seasonal rotations.

But before the season even properly opened, players were already stumbling over a smaller launch-day problem: figuring out exactly when it was supposed to begin. On Blizzard’s Diablo III forums, one player posted “No season 38 yet” after believing the season should already be live, then edited the post after realizing they had likely mixed up the date.

What is happening

Blizzard’s official preview says Season 38 begins on March 27 at 5 PM (PDT/CET/KST) and confirms the return of Ethereals, the rare seasonal weapons that roll with powerful affixes, a random class weapon Legendary Power, and a random class passive. The season also includes returning cosmetics, new Journey rewards, and Haedrig’s Gift set rotations.

On the player side, the build-up to launch was messy in a very Diablo III kind of way. One forum thread was dedicated entirely to converting the launch time for Europe, with players trying to pin down whether the start would land at 5 PM CET or be affected by daylight-saving confusion. Another launch-day thread showed at least one player thinking the season was already late before realizing the start was still tied to March 27.

Why it matters

This matters because Diablo III still lives on ritual. Seasonal starts are the whole event now. When the game is in maintenance mode, the launch window becomes the headline, and even minor confusion around timing stands out more than it would in a game flooded with new content every week.

It also says something useful about Diablo III in 2026: players still care enough to watch the clock. Forum traffic around Season 38 was active before launch, with players already discussing starter builds, Ethereal farming, and whether Blizzard had timed the season correctly. For a game this old, that is not nothing.

Current status / what Blizzard said

Blizzard’s position is straightforward. Season 38 starts on March 27 and is built around the return of Ethereals, including the long-term goal of collecting all 21 Ethereals to unlock their transmogs permanently through the Ethereal Recollection Feat of Strength.

The confusion, then, does not look like a Blizzard delay so much as a launch-day timezone tangle mixed with players staring at the calendar a little too hard. That is an inference based on the official start notice and the forum posts, not a formal Blizzard explanation.

The old machine still pulls people back

Season 38 does not need a surprise expansion or a dramatic system overhaul to get attention. It just needs a strong old loot hook, a fixed start time, and a community ready to obsess over both. Diablo III is old enough to be haunted, but on season day, it still knows how to wake up. 

Read More

Diablo 4 Season 12 Progression Bug Leaves Den of Blood Stuck on Part 6

Diablo 4 Season 12 keeps finding new ways to jam its own progression. A fresh PC bug report posted on March 26 says the Den of Blood, Part 6 objective can fail mid-run, even when players are killing the required Bloodied Lair Bosses inside the time limit.

That is not just another small annoyance. This one hits a named progression step directly, and the player report is specific enough to sting: the counter can fail to award credit, or worse, roll backward instead of forward.

What is happening

In the report, the player says they were stuck on the objective to defeat 6 Bloodied Lair Bosses within 10 minutes in Torment 3 or lower. According to the post, some kills gave no credit, while others caused the progress to drop from 3/6 back to 1/6.

A second player replied the same day saying they saw similar behavior. They wrote that the game warned them the objective was close to completion when they were at 4 of 6, but after two more kills the tracker had dropped to 2. That same player later said the objective finally completed only after doing six more kills in a fresh run, without understanding what caused the reset in the first place.

As of March 27, the thread was still listed in Blizzard’s PC Bug Report index among current Diablo IV issues, which at minimum shows the problem has not disappeared from the active bug-report flow overnight.

Why it matters

This matters because Part 6 is not some decorative side task. It is a named step in a Season 12 progression chain, so when the counter starts slipping backward, players are not just losing time. They are losing confidence that the season’s own objectives can be trusted to track correctly.

It also lands in the middle of a season Blizzard has already been patching aggressively. The March 24 2.6.1 patch fixed multiple Season of Slaughter issues and said it addressed “various instances” where Season Rank Objectives or Capstone Completions did not grant expected rewards or could not be completed correctly.

Current status / what Blizzard said

So far, Blizzard’s latest official patch notes do not call out Den of Blood Part 6 by name. What Blizzard has confirmed is a broader sweep of Season 12 fixes, including objective and completion issues, plus other Season of Slaughter bugs tied to Bloodied systems and Butcher content.

The problem is that this report arrived after that patch. So while Blizzard has clearly been fixing season blockers, this looks like at least one progression issue may still be slipping through. That is an inference based on the timing of the report and patch notes, not a formal Blizzard statement about Den of Blood itself.

When the tracker becomes the enemy

Season 12 can survive hard objectives. It struggles more when the tracker itself starts acting hostile. If Den of Blood Part 6 is going to keep resetting progress in live runs, that is the kind of bug players remember long after the patch notes move on. 

Read More