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

Diablo 4 Season 12 Still Has a Journey Blocker — And Players Are Inventing Workarounds

 

Diablo 4 Season 12 has already burned through goodwill on tuning, rewards, and bug reports. Now one of its earlier Season Journey tasks is still causing problems deep into March: players say the Rank 2 objective “Equip a full set of Magic Bloodied Items” can fail to complete even when they appear to meet the requirement.

That would be annoying on its own. The uglier part is that players are no longer just reporting the issue — they are trading workaround advice, rerolling characters, and experimenting with different weapon setups just to make a basic Journey objective register.

What is happening

The complaints have been building since at least March 12, when players began posting that Bloodied Provisions was not completing properly, even while later item-rarity objectives were. In one thread, players reported that Legendary and Ancestral Bloodied objectives completed normally while the Magic version stayed stuck.

A newer bug report from March 18 shows the issue still hitting multiple classes, including Spiritborn and Paladin. One Spiritborn player said they had every slot filled but could not complete the objective, while another player later claimed they only got it to work after making a second character and gambling for the required gear there.

By March 24, fresh reports were still appearing, with one player saying the “gold one on page 3” had completed while the blue Magic objective had not. And as of March 27, the bug report thread was still active in Blizzard’s PC Bug Report index.

Why it matters

This matters because Season Journey objectives are supposed to give players direction, not force them into weird side rituals. When players are told to try a 1H weapon plus shield, make an alt, or farm low-level vendor gear just to trigger one objective, the system stops feeling demanding and starts feeling unreliable.

It also hits progression trust. Forum posts repeatedly frame the issue around a missing skill point, and at least one player said the bug appeared to interfere with unlocking the Pit, though another player disputed that and said the Magic objective only gated a skill point. That means the exact progression impact may vary by case, but the confusion itself has become part of the story.

Current status / what Blizzard said

Blizzard’s March 24 Patch 2.6.1 notes say the team fixed “various instances where Season Rank Objectives or Capstone Completions either did not grant the expected rewards or could not be completed as expected.” The patch notes also include other Season 12 fixes tied to Bloodied systems and Butcher content.

The problem is that player reports about Magic Bloodied Items did not disappear after that patch went live. Based on the continued forum activity through March 27, at least some cases either survived the fix or were not covered by it. That is an inference from the timing of the patch and the ongoing reports, not a formal Blizzard confirmation.

When a basic Journey task starts feeling cursed

Season 12 does not need every objective to be easy. It does need them to behave. When one of the simplest early Journey tasks still sends players into workaround mode two weeks later, that stops looking like bad luck and starts looking like another crack in the season.

Read More

Diablo 4 Season 12 Is Pushing Players Into Kill-Trading for a Butcher Objective

Diablo 4’s Season 12 was built around becoming the Butcher and turning Fields of Hatred into something uglier than normal PvP. But one of the season’s later Journey objectives now seems to be pushing players toward a different kind of gameplay entirely: arranged kill-trading.

On March 27, a fresh forum post openly offered to swap kills for the seasonal task to kill someone while transformed as the Butcher. That was not an isolated mood swing either. A nearly identical Looking for Group thread had already appeared on March 22, which suggests players were solving the same problem days earlier in a more organized way.

What is happening

The objective at the center of this is a Rank 6 seasonal task tied to killing another player as the Butcher on higher Torment difficulty. Players on the official forums have been arguing for days that the requirement feels awkward in practice, either because the Butcher gets erased too fast by geared players or because there simply are not enough natural opportunities for the kill to happen cleanly.

That helps explain why forum behavior has drifted from strategy discussion into matchmaking for reciprocal kills. Once players start posting “I’ll let you get your kill first,” the objective is no longer generating organic competition. It is generating admin work.

Why it matters

This matters because seasonal objectives are supposed to shape play, not quietly encourage players to bypass the intended experience. When the cleanest route becomes arranging a trade instead of engaging with the event naturally, it usually means the objective has landed in an awkward spot between rarity, balance, and player motivation.

There is also a design tension here. Blizzard’s Season of Slaughter overview presents Ceremony of Slaughter as a race where kills build Savagery and the top contender becomes the Butcher, turning the zone into a personal hunting ground. On paper, that sounds brutal and dynamic. In practice, at least for some players, it is ending in forum posts looking for scheduled mercy kills.

Current status / what Blizzard said

Blizzard has clearly explained how Ceremony of Slaughter works and has already pushed Patch 2.6.1 to address several Season 12 issues, including Bloodsoaked tuning and other bug fixes. But the latest official patch notes do not mention a change to this Butcher player-kill objective, and the March 27 forum traffic shows the workaround culture is still alive.

When the objective starts writing its own workaround

Not every awkward objective becomes a real problem. This one might, because the community has already started inventing its own fix. And when a seasonal challenge is easier to coordinate than to actually play, something in the design probably needs another look. 

Read More

Diablo Immortal’s The Taking Update Brings Back Andariel — But Equalized PvP May Be the Bigger Story

Diablo Immortal’s latest major update, The Taking, arrived with a familiar Diablo hook: Andariel is back in the picture, Sanctuary is unraveling again, and Blizzard is laying the groundwork for a longer new story arc. But buried under the usual patch spectacle is the more interesting move: Diablo Immortal is experimenting with a PvP format that cuts back progression-based advantages and pushes player skill closer to the center.

That matters because Diablo Immortal has spent years dragging around the weight of pay-to-win arguments, especially whenever PvP enters the conversation. So when Blizzard launches a mode built around normalized power, it is not just another feature bullet. It is a signal.

What is happening

Patch 4.3 introduces The Taking, a new main quest that follows the trail of Andariel, the Maiden of Anguish, through disappearances in Sanctuary’s port cities, disturbances at Eastgate Monastery, and fresh danger gathering outside Lut Gholein. The update also adds the Rocky Waste subzone, new Legendary Gems, refreshed Battleground content through Siege of Corvus, and multiple limited-time events.

The standout feature is Challenge of Equals, a new Bout of Realms PvP variant where player power is normalized to emphasize “moment-to-moment combat and mechanical skill.” Blizzard says Legendary affixes and set bonuses remain 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.

Why it matters

This is the kind of system change that gets attention beyond the Diablo Immortal player base. Blizzard is not removing monetization or rewriting the game’s core economy, but it is openly testing a competitive mode where the usual investment advantages are sharply reduced. In a game long criticized for how progression and spending shape PvP, that is a meaningful shift.

The early reaction also shows the usual Diablo Immortal split. In Blizzard’s forum thread, some players praised parts of the update like the versatile ring socket system and set-item socket improvements, while also asking why those quality-of-life gains are only temporary. At the same time, forum traffic around Battleground matchmaking and camera frustration has not gone away, which means one smart PvP experiment will not instantly clean up the game’s wider reputation.

Current status / what Blizzard said

Blizzard says The Taking is live now, and it has already committed to monitoring feedback around Challenge of Equals. The studio also says Battlegrounds will get a broader seasonal refresh in April 2026, with additional visual and gameplay adjustments aimed at making combat flow feel clearer and more impactful.

A smarter move than it first looked

Andariel gives The Taking its headline threat, but the more revealing part of this update is Blizzard testing how far Diablo Immortal can move toward fairer-feeling competition without breaking its own structure. That experiment may end up mattering more than the demons. 

Read More

Diablo III Season 38 Starts March 27 — And Ethereals Are Coming Back

 Diablo III is about to drag players back into old habits. Blizzard has confirmed that Season 38: Ethereal Memory begins on March 27 at 5 PM (PDT/CET/KST), bringing one of the game’s most popular seasonal loot hooks back into rotation.

The headline feature is the return of Ethereals, a special weapon type that only drops in Seasonal play and comes loaded with powerful affixes, a random class weapon Legendary Power, and a random class passive. In other words, Season 38 is built around a loot chase Diablo III players already know can get dangerously addictive.

What is happening

Blizzard’s preview lays out Ethereals as rare, account-bound drops that can come from monsters, chests, and destructibles. Each class gets three unique Ethereals, only one can be equipped at a time, and they sit in a rarity band between Ancient and Primal items. They also cannot be traded, reforged, or pulled from Kanai’s Cube or Kadala, which keeps the hunt old-fashioned: go kill things and hope Sanctuary finally pays out.

There is also a long-tail reward attached to the chase. Players who collect all 21 Ethereals during the season earn the Ethereal Recollection Feat of Strength, which permanently unlocks all Ethereal transmogrify options for future Seasonal and non-Seasonal play. That gives Season 38 a cleaner hook than a lot of maintenance-era refreshes: this is not just borrowed power, it is collectible power with a cosmetic payoff attached.

Why it matters

Season 38 matters because Diablo III still works best when it has a simple, readable obsession at its center. Ethereals do that. They add rarity, build experimentation, and a clear collecting goal without asking players to learn a pile of new systems first.

The community reaction also suggests Blizzard picked a theme players still care about, even if not everyone is thrilled with recycled seasonal structure. In the official forum thread, some players said they were already looking forward to Season 38 and called Ethereals one of Diablo III’s most fun themes, while others complained that the season feels too familiar and wanted more new cosmetic rewards. That is not universal praise, but it is real engagement.

What Blizzard said

Blizzard says Season 38 will also bring back cosmetic rewards originally tied to Season 14 and Season 26, plus new end-of-journey rewards including the Rakkis’ Remembrance portrait and the Toothsome Trooper pet. Haedrig’s Gift sets are also locked in, with options such as Inna’s Reach for Monk, Embodiment of the Marauder for Demon Hunter, and The Legacy of Raekor for Barbarian.

The old ritual still works

Season 38 is not pretending to reinvent Diablo III. It is doing something simpler and probably smarter: bringing back a loot hunt players still remember, attaching a clean reward loop to it, and opening the gates on a fixed date. For a game this old, that is sometimes all it takes to raise the dead one more time.

Read More

Diablo 4 Trading Looks Shaky Right Now — And That Is a Bigger Problem Than It Sounds

Diablo 4 has spent most of the last week dealing with Season 12 complaints around difficulty, rewards, and progression. But another issue is starting to creep up through the forums, and this one cuts into something more basic: trading. On March 26, fresh PC bug reports described players being unable to place items into the trade window at all, even while gold trading still worked.

That may sound niche compared to a broken season mechanic, but it is not. Once trading starts behaving unpredictably, the damage spreads beyond one transaction. It hits player trust, item circulation, and the small economy Diablo 4 still has left.

What is happening

The clearest report came from a March 26 PC Bug Report thread titled “Unable to trade items,” where a player said they tested multiple non-account-bound items and could not add any of them to the trade window. Another active thread the same day, “I cannot add items to trade window PC, only gold,” described the same behavior: items would not enter the trade window, but gold could still be offered.

What makes the story stronger is that this does not look like one isolated bad click. Forum activity shows related trading problems hanging around beyond a single thread, including reports of the trade option being greyed out, players being stuck with trade chat issues, and one PlayStation report asking whether Season 12 trade chat was “working…BUT is it?”

One player in the March 26 item-trade thread said they ended up dropping the item on the ground and trusting the other player to pay gold afterward. That is a workaround, not a system. In a loot game, forcing players into honor-system trading is the kind of detail that makes the whole setup feel shakier than Blizzard probably wants.

Why it matters

Diablo 4 does not have a huge freewheeling player economy like some ARPG rivals, and players already debate how limited trading feels in general. That is exactly why system friction matters here. When the trade window itself stops behaving, even a modest economy can start to feel half-broken.

It also lands at a bad time. March 26 forum traffic was already crowded with Season 12 bug reports, known-bug discussion, and fresh complaints across multiple systems. Trading issues arriving in that environment do not look like a small side problem. They look like another crack in a season that is already under pressure.

What Blizzard has said

Blizzard’s latest Diablo 4 patch notes, updated March 24 for version 2.6.1, addressed Bloodsoaked Sigils and several season-related bugs. They did not list a fix for current item-trading problems. The most recent official trading-related fix visible in earlier patch notes was for PlayStation players being unable to use Trade Chat, which was addressed in January’s 2.5.3 notes, not in the current 2.6.1 update.

When the system starts to wobble

Trading bugs rarely become the biggest headline in Diablo 4. But when players cannot reliably move items through the game’s own trade window, the issue stops being cosmetic fast. It starts to make Sanctuary feel less stable than it should. 

Read More

Diablo 4 Season 12 Has a Reward Problem — And Some Players Say They Are Still Missing Paragon Points

Diablo 4 Season 12 has already taken hits over balance, pacing, and Bloodsoaked tuning. Now another problem is cutting closer to the bone: players say they are finishing seasonal objectives, seeing them marked as claimed, and still not receiving the Paragon Points tied to those rewards.

That matters more than a cosmetic glitch or a broken tooltip. Paragon Points are character power. When those go missing, the problem stops being annoying and starts feeling like lost progression.

What is happening

One of the clearest reports came from players who completed Season 12 Journey objectives and counted their total Paragon Points afterward. In one forum thread, a player at level 167 said they should have had 203 total Paragon Points after Season Journey rewards, but only had 199. Multiple replies described the same missing four-point gap, with several players specifically pointing to the Rank V “Filet-o-Flesh” reward chain.

The complaints are not isolated to one platform or one day. Similar reports appeared on both the US and EU Diablo IV forums, including players saying Rank 6 rewards were partially missing and others saying Rank V Capstone rewards granted everything except the four Paragon Points. Fresh reports were still being posted on March 25, including a new “Turned in capstone tier V and no paragon points” thread.

Why it matters

Seasonal reward bugs are dangerous because they undermine the one thing a live-service action RPG cannot afford to make players doubt: whether the grind is actually paying out. A missing stash tab is irritating. Missing power is something else.

It also lands at a bad time for Season 12. Diablo 4 is already dealing with a pile of bug traffic around progression, Slaughterhouse behavior, item systems, and seasonal quest flow. When reward bugs keep surfacing inside that wider mess, the season starts to look less unstable around the edges and more unstable at the core.

Current status / what Blizzard said

Blizzard did address reward problems in Patch 2.6.1. In the official patch notes, the studio said it fixed “various instances where Season Rank Objectives or Capstone Completions either did not grant the expected rewards or could not be completed as expected.”

The issue is that player reports did not suddenly vanish after that line went live. As of March 25 and March 26, forum threads about missing Paragon Points were still active, which suggests at least some reward cases either survived the patch or were not covered by the fix players expected. That is an inference from the timing of Blizzard’s patch notes and continued forum reports, not a formal Blizzard confirmation of an unresolved bug.

A Reward System Players Do Not Trust

Blizzard has already admitted Season 12 reward logic needed repair. The problem now is credibility. If players cannot trust that claimed rewards actually land, every seasonal objective starts to feel a little more cursed than it should. 

Read More

Diablo 4 Tried to Fix Bloodsoaked Sigils — Players Say Season 12 Still Feels Broken

Blizzard moved fast this week to address one of Diablo 4 Season 12’s biggest pain points. Patch 2.6.1, released on March 24, reduced the difficulty of Bloodsoaked Sigils “significantly” after Blizzard said many players could not reasonably complete the content once they unlocked it.

The problem is that the patch did not end the argument. By March 26, Diablo 4’s official forums were still filling up with threads like “Bloodsoaked is still BS,” “How to get fresh meat if bricked by bloodsoaked?” and broader Season 12 bug reports, suggesting the fix may have lowered the ceiling without fixing the underlying frustration.

What is happening

Blizzard’s patch notes framed the change as a direct response to feedback, saying Bloodsoaked content had become unreasonable for too many players after unlocking it. The update also included fixes for several Season of Slaughter issues, including objectives that were not progressing correctly, missing UI behavior, and problems tied to Bloodied activities.

But the community response since then has been rough. In one of the most active threads after the patch, players argued that Bloodsoaked boss sigils still feel overtuned, that some classes are effectively boxed out of efficient farming, and that once a character crosses into Bloodsoaked progression, rolling that decision back is not simple. Another thread focused on how farming Fresh Meat becomes a slog if your normal loop is no longer efficient.

Why it matters

This matters because Bloodsoaked content is not just optional bragging-rights territory. It sits inside the season’s reward loop, progression pacing, and item chase. If the content still feels punishing after Blizzard already issued a direct nerf, then the story stops being about one tuning mistake and starts becoming a wider confidence problem for Season 12.

That tension is showing up alongside a still-growing known-bugs list. Blizzard forum tracking for Season 12 continues to include issues with Slaughterhouse transformation behavior, certain season objectives, item imprinting problems, and invisible furnace fire during a Bloodied Lair Boss fight.

Current status / what Blizzard said

Right now, Blizzard has clearly acknowledged the Bloodsoaked tuning issue and already pushed one significant nerf. What it has not said yet is whether another balance pass is coming, or whether the current state is considered close enough.

For now, the message from the forums is fairly blunt: players noticed the patch, but many still do not think the problem is solved. If that sentiment keeps spreading, Season 12’s hardest content may remain a liability instead of an endgame prize. 

Read More

Diablo 4 Players Say “Hide Weapons” Still Does Not Work After the Latest Patch

Another smaller but very readable Diablo 4 Season 12 complaint is making the rounds: players say the Hide Weapons option still is not actually working, even after the latest patch. A fresh March 24 Blizzard bug-report thread puts it bluntly: “Fix it. Button does nothing.” Another player replied a few hours later confirming that after the most recent patch, it was still not functioning.

That makes this a cleaner story than some of the more complicated Season 12 bugs. Players are not arguing over hidden math, unclear tooltips, or progression edge cases here. They are saying a cosmetic toggle exists, players click it, and nothing happens.

Fresh reports suggest the setting is still broken

The March 24 thread is not floating out there alone. Blizzard’s current PC bug-report listings also show another recent topic titled “Hiding the sheathed weapons feature does not save the setting and does not work,” which points to the same general complaint from a slightly different angle. That matters because it suggests players are not just upset about a one-off glitch on one character. The feature appears to be drawing multiple fresh reports on Blizzard’s own forums.

Blizzard’s broader Diablo IV latest-topics page also shows Hide weapons STILL NOT WORKING among the active March 25 bug discussions, which gives the article a fresh-news hook instead of making it feel like recycled patch annoyance.

Why players care about something this “small”

On paper, this is obviously not the biggest Diablo 4 issue in the world. Missing Paragon Points, broken progression, and lair bugs hit gameplay harder. But cosmetic options matter more than they used to, especially in a game where armor presentation, class silhouette, and paid cosmetics are a big part of how players interact with their characters. That second sentence is an editorial inference based on Diablo 4’s cosmetic-heavy player culture, not a Blizzard statement.

And that is why this kind of issue travels. It is easy to understand, easy to reproduce if it is happening to you, and easy to get annoyed by. If a feature says it hides weapons, players expect hidden weapons, not another dead toggle in the menu.

This fits the wider Season 12 mood

The bigger context here is that Season 12 already has players watching for anything that feels unfinished, unstable, or half-fixed. So even a cosmetic bug can get more attention than usual when it lands in the middle of a season already carrying a long list of player complaints. That is an editorial observation based on the volume of fresh bug-report activity on Blizzard’s Diablo IV boards.

In other words, this is not really about hidden weapons alone. It is about players seeing yet another feature they say is still not working when the season is already full of friction points. That framing is an inference from the current bug-board pattern, not an official Blizzard explanation.

No visible fix note yet

Based on the Blizzard forum threads reviewed here, there is no visible Blizzard reply attached to the fresh Hide Weapons thread confirming a fix or explaining why the feature is still failing. So the safest framing remains the same as with the other Season 12 coverage: players are reporting the issue, but Blizzard has not publicly confirmed the cause in the reviewed sources.

For now, the clean takeaway is simple: some Diablo 4 players say the Hide Weapons option still does not work after the latest patch, and fresh March 24–25 forum reports suggest the problem has not been resolved yet.

Read More

Diablo 4 Patch 2.6.1 Nerfs Bloodsoaked Sigils After Players Said They Were Too Much

Blizzard has now officially stepped in on one of Diablo 4 Season 12’s rougher pain points. In Patch 2.6.1, released on March 24, 2026, Blizzard says it has “reduced the difficulty of Bloodsoaked sigils significantly” after player feedback made it clear that many people simply were not getting through them.

That is one of the clearest official walk-backs in the current Season 12 cycle. Blizzard’s own developer note says the team received feedback that many players “cannot reasonably complete Bloodsoakeded Sigils after unlocking them” and that the goal of the nerf is to give players who earned access to Bloodsoaked content “a better chance of success.”

Blizzard is admitting the difficulty was too high

That wording matters because Blizzard is not just nudging a number in the background and hoping nobody notices. The patch note directly acknowledges that the difficulty had overshot the point where many players could complete the content in a reasonable way.

For Season 12, that is a pretty important adjustment. Bloodsoaked Sigils were supposed to be one of the season’s big endgame tests, but instead they quickly became part of a growing list of player complaints about seasonal pacing, Bloodied systems, and whether some of the new content was overtuned or simply frustrating. The second sentence is an editorial inference based on Blizzard’s patch note and the broader Season 12 complaint cycle.

This is the most official version of “yes, we heard you”

Blizzard’s March 24 patch note is useful because it gives you a cleaner article than another player-forum bug story. This time the source is Blizzard itself, and the message is straightforward: Bloodsoaked Sigils were too hard for too many players, so Blizzard hit them with a significant difficulty reduction.

That makes this less of a debate piece and more of a concrete follow-up on how the developer is reacting to Season 12 feedback. Not every seasonal frustration gets that kind of direct note.

Patch 2.6.1 also touched other Season 12 pain points

The Bloodsoaked Sigil nerf was not the only Season 12 change in Patch 2.6.1. Blizzard also added a stash and blacksmith to Kael Rills’ Butcher shop to reduce the amount of running back and forth in Gea Kul, and it fixed a long list of Season of Slaughter issues, including some reward, party, tooltip, and Bloodied-content bugs.

That wider context makes the patch feel like a mid-season correction pass rather than a tiny hotfix. Blizzard is clearly still tuning and stabilizing Season 12 in real time. That last sentence is an inference based on the scope of the patch notes.

The funny part is that difficulty was only one problem

Even with the official nerf, Bloodsoaked content is still carrying a messy reputation right now. Players have been reporting issues around Bloodied items, boss lairs, objectives, progression rewards, and map visibility, so reducing sigil difficulty does not magically erase the rest of the season’s friction. That is not stated by Blizzard in the patch note; it is an editorial observation based on the wider public discussion around Season 12.

Still, this change matters because it hits one of the most obvious player-facing problems: content that people unlocked, but then could not realistically clear.

What Blizzard actually changed

Blizzard did not provide exact before-and-after values in the public note. The wording simply says the difficulty was reduced significantly, and the developer note makes clear the reason was accessibility and completion rate, not a minor balance polish pass.

So if you are writing this cleanly for readers, the takeaway is simple: Blizzard has officially nerfed Bloodsoaked Sigils because players were struggling to complete them at a reasonable level after unlocking them.

The bigger Season 12 takeaway

This is probably the most straightforward example yet of Blizzard softening Season 12 after launch pressure. It does not mean the season’s problems are solved, but it does mean one of its most punishing systems has now been officially toned down.

For now, the headline version writes itself: Diablo 4 Patch 2.6.1 significantly nerfs Bloodsoaked Sigils after Blizzard says many players could not reasonably complete them.

Read More