Diablo 3 Season 38 Starts March 27, So Here’s What to Finish Before Ethereal Memory Goes Live

Diablo 3 Season 38 is almost here, and if you have been planning one more trip back to Sanctuary, now is the time to get your house in order. Blizzard has confirmed that Season 38: Ethereal Memory begins on March 27 at 5 PM PDT / CET / KST, bringing back Ethereals as the season theme.

You already covered the main Season 38 announcement. This angle is the practical follow-up: what players should actually do before the new season starts.

First, know what Season 38 is bringing back

The headline feature is the return of Ethereals, the Diablo II-inspired weapons that only drop in Seasonal play. Blizzard says each class gets 3 unique Ethereals, and each one rolls a random Class Weapon Legendary Power plus a random Class Passive Skill. Only one Ethereal can be equipped at a time, and they only drop from monsters, chests, and destructibles. They cannot be obtained from Kadala or Kanai’s Cube.

Blizzard also says Ethereals have a drop rate between Ancient and Primal items, and players who collect all 21 Ethereals during the season unlock the Ethereal Recollection Feat of Strength, which permanently grants the transmogrify appearances for future seasonal and non-seasonal play.

That matters because this is not just another short-lived power gimmick. For collectors, Season 38 has a real long-term cosmetic reward attached to it.

If you plan to play, decide your class now

Blizzard has already confirmed the Haedrig’s Gift sets for Season 38, and that should make class planning easier before launch. The available starter sets are:

• Barbarian: The Legacy of Raekor
• Crusader: Armor of Akkhan
• Demon Hunter: Embodiment of the Marauder
• Monk: Inna’s Reach
• Necromancer: Pestilence Master’s Shroud
• Witch Doctor: Zunimassa’s Haunt
• Wizard: Delsere’s Magnum Opus

If you want a smooth season start, this is the part to think about now instead of on launch night. Since players only get one Class Set per Season through Haedrig’s Gift across Hardcore and Non-Hardcore, opening those bags on the wrong character is still the classic self-inflicted Diablo 3 problem.

Clear out your stash before the season begins

This is the least glamorous advice and also probably the most useful.

If you are returning for Season 38, clean your stash now. Salvage old junk, decide what non-seasonal items you are actually keeping, and stop pretending those random legendaries from three eras ago are part of some future master plan. Blizzard confirms players who have not yet earned the maximum of five stash tabs through Seasonal Journey can still unlock an additional one by completing the required Conqueror objectives this season.

That gives you two reasons to tidy up early:

1. you will want room for a fresh seasonal grind
2. you may still be able to earn more stash space if you have not capped out yet

Know the Conquests before launch

Blizzard has also confirmed the Season 38 Conquests rotation, and this is one of the easiest places to save yourself time by planning ahead.

Returning Conquests include:

• Avarice / Avarita
• Speed Demon / Need for Speed
• On a Good Day / I Can’t Stop
• Divinity / Lionhearted
• Years of War / Dynasty

That matters because some of these are much easier depending on your class choice and season goals. If you are aiming for the stash tab or a deeper Journey push, it is smarter to decide early which Conquests you want to target instead of improvising halfway through the season.

Be realistic about your Season Journey goals

Blizzard’s preview also lays out the Conqueror-tier tasks tied to the extra stash tab reward, including:

• finishing a level 70 Nephalem Rift on Torment XIII within five minutes
• reaching Greater Rift 60 Solo
• killing Greed on Torment XIII
• killing the Butcher at level 70 on Torment XIII in under 30 seconds
• reforging a Legendary in Kanai’s Cube
• augmenting an Ancient Legendary with a level 50+ gem
• leveling three Legendary Gems to 55
• completing 2 Conquests

That gives you a pretty good preview of how serious you want to be. If your goal is just to mess around with Ethereals, great. If your goal is stash progress, cosmetics, and full Journey completion, then Season 38 asks for a bit more structure than “log in and see what happens.”

The collector angle may be the real reason to come back

For a lot of players, the most interesting part of Season 38 is not raw efficiency. It is nostalgia.

Blizzard is leaning hard into the return of Ethereals as a callback to Diablo II, complete with unique icons, names, item types, and sounds inspired by that era. Since Ethereals only drop in Seasonal play and do not transfer to non-seasonal characters when the season ends, the season has a built-in “play it while it lasts” appeal.

That makes this one of those Diablo 3 seasons where the vibe matters almost as much as the build meta. It is a chase season, a collector season, and a “one more run” season all at once.

The simple pre-launch checklist

If you are jumping into Season 38, the smart move right now is pretty straightforward:

Choose your starting class, clear stash space, look at the Conquests, decide whether you care about stash progress or cosmetics, and remember that the real prize for many players is collecting all 21 Ethereals before the season ends. Everything goes smoother when you decide that before launch instead of after your third bad reroll and a full inventory.

The big takeaway is simple: Diablo 3 Season 38 starts March 27, and Ethereal Memory looks like the kind of season that rewards players who go in with a plan.

Read More

Diablo 4 PS5 Players Say They Couldn’t Log In During a Fresh WS-114119-7 Error Wave

Diablo 4 players on PS5 are reporting a fresh round of login trouble, with multiple users saying they were unable to get past the game’s start screen and were hit with the PlayStation error code WS-114119-7 instead. The complaints surfaced on Blizzard’s official Diablo IV forums on March 21 and remained active into March 22, with players across multiple regions saying they ran into the same issue.

One of the clearest reports came from Blizzard’s Console Bug Report section, where a PS5 player said the game loaded to “press any button” but then failed to log in. The same player later updated the post to say they eventually received the WS-114119-7 error code. Other replies in that thread quickly piled on with variations of “same issue” and “can’t get on either,” which suggests this was not a one-user problem.

Players say the issue looked wider than one console

This did not stay limited to one forum thread. A separate Blizzard thread titled “Anybody ever have this issue loading the game before?” also filled with players reporting the same code around the same time, including posts from Texas and New Zealand. Another discussion in PC General Discussion said players were seeing WS-114119-7 during login there as well, which raises the possibility that this was not purely a single-console failure, even if PS5 players seemed to be the loudest group reporting it.

That point matters because several players were trying to figure out whether the problem was PlayStation Network, Diablo 4’s own online services, or something in between. In the page-two replies of the main thread, one player said they assumed it might be a PSN issue because they could still access the PC Battle.net version on the same account, while others argued it looked more like a Diablo-specific outage. Blizzard had not publicly clarified the cause in the forum threads reviewed here.

Reddit reports matched the forum complaints

The same login problem also showed up on Reddit, where a Diablo 4 player posted that they could not log in on PS5 and were getting WS-114119-7. A top visible reply in that thread said the same issue was happening elsewhere and suggested it could be tied to either Blizzard or PlayStation services. Reddit is not an official source for diagnosis, but it does help confirm that the complaints were not staying boxed inside Blizzard’s own forums.

No visible Blizzard fix post in the threads reviewed

At the time of the sources reviewed here, Blizzard’s forum threads showed plenty of player reports but no clear visible staff response explaining the cause or confirming a fix in those same pages. That means the safest framing is this: players reported a fresh PS5 login issue tied to WS-114119-7, but Blizzard had not publicly explained the exact cause in the reviewed threads.

This also makes the story a little different from the other Season 12 articles you have already published. It is less about broken progression or Bloodied systems and more about players being unable to get into the game at all. For traffic mix, that gives you a cleaner platform-support angle without repeating the same reward bug rhythm again. That last sentence is editorial judgment based on the current Diablo 4 story mix, not a sourced Blizzard statement.

The practical takeaway

For now, the clean summary is simple: some Diablo 4 PS5 players say they were locked out by WS-114119-7 during a fresh login issue on March 21–22, and public player discussion suggests the problem may have affected more than one region. Whether this turns into a recurring support issue or ends up as a short-lived outage will depend on whether new reports keep appearing. 

Read More

Diablo 4 Players Say the Bloodied Gear Aspect Problem Is Still Not Fixed in Season 12

Diablo 4 players are still pushing the same complaint about Bloodied gear in Season 12: Aspects on Bloodied Legendary items do not appear to imprint correctly, and some players say the system is still forcing minimum rolls instead of using the higher values already unlocked in the Codex. A fresh March 24 General Discussion thread on Blizzard’s forums shows the issue is still active in player conversations, with one poster calling it a failure of one of Season 12’s headline features.

This is not a brand-new claim. A March 12 EU forum thread described the same issue in more specific terms, saying Bloodied items were always receiving the minimum possible Aspect value regardless of how high the Aspect had been upgraded in the Codex. That older thread included a concrete example: a player said an Aspect that should have imprinted at 67% instead landed at 50% every time on a Bloodied item.

Why players are bringing it up again

The newer March 24 complaint matters because it shows the issue has not faded out after the first wave of reports. Instead, players are still surfacing it as an unresolved Season 12 problem, and they are framing it as a system-level issue tied directly to Bloodied Legendary gear rather than a one-off oddity on a single item.

That also fits the broader mood around Bloodied content on Blizzard’s forums right now. The latest topics page shows multiple active Bloodied-related discussions on March 24, including threads about damage reduction, Bloodstained and Bloodsoaked content, and Season Journey Bloodied gear objectives. In other words, Bloodied systems are still generating friction across several angles at once.

What players say is actually happening

The core complaint is simple: players say they have already ranked up their Aspects in the Codex, but when those Aspects are imprinted onto Bloodied Legendary items, the finished item still takes the lowest possible roll. That would be a big problem for build power, because it effectively makes Bloodied gear less attractive at the exact moment Season 12 is trying to push players toward using it. The first sentence reflects player reports, not a Blizzard-confirmed diagnosis.

There are also signs the community has started treating this as common knowledge rather than an isolated edge case. Reddit’s community-made Season 12 known-bugs roundup from last week included Bloodied objective issues and workarounds, showing that Bloodied systems are being discussed in “known problems” terms across the player base rather than as one random forum post nobody noticed.

Why this matters for Season 12

Season 12 leans heavily on Bloodied mechanics, so repeated complaints like this hit harder than a random bug on old gear. If the seasonal item type is not interacting properly with Aspects, players are not just losing a bit of polish. They are questioning whether one of the season’s main progression hooks is reliable enough to invest in. That is an inference from the reports and the volume of Bloodied-related threads, not an official Blizzard statement.

It also gives you a cleaner follow-up than simply repeating the first imprinting article. The earlier story was about the original reports. This one is about the fact that players are still escalating the issue on March 24, which makes it a “not fixed yet” angle rather than a duplicate.

No public Blizzard fix is visible yet

Based on the sources reviewed here, there is still no public Blizzard post attached to these threads confirming a fix for Bloodied Legendary Aspect rolls. The complaint remains player-reported, but it is now supported by multiple forum threads across March rather than a single isolated post.

For now, the clean takeaway is this: Diablo 4 players are still saying Bloodied Legendary gear does not work properly with Aspects in Season 12, and public discussion around the issue is still active on March 24.

Read More

Diablo 4 Players Say DoT Builds Hit a Wall in High-Tier Pit and Tower Content

A new Diablo 4 Season 12 report suggests some Damage-over-Time builds may be running into unexpected scaling problems in high-tier endgame content, with one player claiming DoT damage starts falling off dramatically compared to direct damage builds.

The report appeared on Blizzard’s Diablo IV bug report forums on March 22, where a player described what they believe is a scaling issue affecting multiple classes once players push into higher Pit and Tower tiers.

Players claim DoT damage stops scaling properly

According to the report, the player tested DoT setups across multiple classes including Rogue, Barbarian, Necromancer, Sorcerer, and Spiritborn. After extensive endgame testing, they concluded DoT damage appears to scale far worse than direct damage once content difficulty increases.

Importantly, this is currently a player claim, not a confirmed Blizzard issue.

Still, reports like this tend to get attention because they affect build viability at the very top of the game, where small scaling differences can decide which builds can actually push endgame content.

Why this could matter for endgame players

For most players, this may never become noticeable. But for players pushing deep Pit tiers or high Tower difficulty, damage scaling is everything.

If DoT builds hit a damage ceiling earlier than expected, it could push players toward burst builds instead. That wouldn’t necessarily mean DoT builds are broken, but it could suggest a balance gap in how different damage types scale at extreme difficulty levels.

Right now, it’s too early to say whether this is:

• a real scaling bug
• intended balance behavior
• or a build optimization issue

No Blizzard confirmation yet

At the time of writing, Blizzard has not publicly responded to the report in the forum thread reviewed for this article.

That means this remains a player-reported concern, not an officially confirmed issue.

Still, Season 12 has already seen multiple player reports involving progression systems and Bloodied gear interactions, so players are paying closer attention to any potential mechanical inconsistencies.

One to watch if more reports appear

For now, this looks like an early warning rather than a confirmed widespread issue. But if more players begin reporting similar DoT scaling problems across different classes, this could turn into a bigger endgame balance discussion.

For now, the takeaway is simple:

Some Diablo 4 players believe DoT builds may be underperforming in very high-tier Pit and Tower content, but more reports would be needed to confirm whether this is a real systemic issue.

Read More

Diablo 4 Players Say the “Equip a Full Set of Magic Bloodied Items” Objective Still Isn’t Completing in Season 12

Diablo 4 Season 12 has already piled up its share of player-reported issues, and another one is now getting more attention: some players say the Season Journey objective “Equip a full set of Magic Bloodied Items” still does not complete properly, even when they appear to meet the requirement. Fresh Blizzard forum posts on March 24, 2026 show players still running into the problem, with one report saying the later gold-tier objective unlocked while the earlier blue/magic one did not.

That detail is what makes this one sting. According to the March 24 report, the player says they could progress past the rare/gold bloodied gear requirement, but the magic/blue bloodied gear step remained stuck. Another reply in the same thread said the issue was still happening “2 weeks into season,” framing it as a bug that should have been easy to catch before launch.

What players are reporting

The fresh March 24 thread is not the only sign this has been lingering. A separate Blizzard bug-report thread from March 18 describes the same objective failing to complete for a Spiritborn player who said they had a full set of Magic Bloodied Items equipped in every available slot, noting that the class cannot equip an off-hand. That matters because it suggests the issue may not just be one person misunderstanding the requirement.

An even earlier March 12 Blizzard forum post also described a strange mismatch in the Season Journey logic. In that case, the player said the rare bloodied items objective completed using a mixture of rare and legendary bloodied gear, but the magic bloodied items objective still would not finish. If that reading is correct, the simpler requirement may actually be behaving less reliably than the one after it.

Why this is more than a tiny checklist annoyance

On paper, this looks like a small progression hiccup. In practice, it hits one of the most visible parts of the season: the Journey. The March 24 player report explicitly complains about Blizzard locking a skill point behind something they view as buggy, which raises the stakes beyond mere completionism. If players believe a seasonal reward is blocked by a broken objective, the frustration level goes up fast.

There is also a broader trust issue here. Season 12 is built heavily around Bloodied Items, so when one of the early Bloodied gear objectives does not reliably register, it undercuts the seasonal onboarding. Instead of teaching players how the new gear type works, the objective becomes another thing they have to troubleshoot. That last sentence is an editorial inference based on the bug reports and the season’s Bloodied focus.

The community is already trying workarounds

Reddit discussion shows players attempting to reverse-engineer what the objective really wants. Some replies say the description may be misleading and that a full set of bloodied gear “magic or higher” can sometimes work, while others describe cycling through multiple blue items or changing weapon setups until the objective finally triggers. At least one commenter specifically mentions Spiritborn and says using a two-handed weapon seemed to help in their case.

That does not prove there is a reliable fix. It does show the usual Diablo pattern kicking in: when the game stops explaining itself clearly, the community starts building folk remedies. Sometimes those workarounds help. Sometimes they just create more confusion around what is actually bugged. The second sentence there is an inference based on the mixed player responses.

This now looks like an ongoing issue, not a one-off report

One reason this article angle works is that the timeline is pretty clear. There are public Blizzard forum reports from March 12, March 18, and March 24, all circling the same Season Journey objective. Blizzard’s current bug-report index also shows the issue among the latest active topics, which suggests it has not simply vanished or been quietly forgotten by players.

That still does not mean Blizzard has officially confirmed the exact cause. In the sources reviewed here, the issue is best described as a player-reported Season 12 bug with repeated public reports, not a formally explained Blizzard-diagnosed problem.

Read More

Diablo 4 Players Say Crafted Mythic Uniques Can Come Out Non-Ancestral in Season 12

Another fresh Diablo 4 Season 12 complaint is starting to make the rounds, and this one hits a pretty painful part of the endgame loop: crafted Mythic gear. A new post on Blizzard’s official Diablo IV bug-report forum says crafted Mythic Uniques can come out as non-Ancestral, with the player claiming two crafted Shroud of False Death items both showed as item level 800, one-Greater-Affix Mythic Uniques, but not as Ancestral Mythic Unique items.

That would already be frustrating on its own, but the report adds a second problem: the player says those crafted items also did not grant credit for the Season Journey Rank 6 objective “Fabled Power.” In other words, the complaint is not just about item labeling or rarity presentation. It is also about progression potentially failing to recognize the crafted Mythic correctly.

What the current report actually says

The Blizzard forum post is very specific. The player says they crafted two copies of Shroud of False Death, and both were produced as Mythic Uniques that were still iLVL 800 and 1-star GA, but not flagged as Ancestral Mythic Unique. The same post says that because of that, the player was not getting credit for the Season Journey Rank 6 task.

That is the key reason this story is worth watching. If the issue is real and not just a weird tooltip quirk, then it potentially affects both gearing and seasonal progression at the same time. A player can spend rare materials crafting a top-tier item and still end up stuck on a Season Journey requirement that should, at least from their perspective, already be complete.

Why this matters even if the report count is still small

Right now, this does not look like a massive confirmed community-wide outbreak. In the public sources reviewed here, the strongest evidence is still a fresh single bug-report thread on Blizzard’s forum, not a giant pile of identical reports. The Diablo IV forum index does, however, show the thread as a current active bug report posted on March 22, 2026, which is enough to treat it as a real fresh player complaint worth tracking.

And because it involves crafted Mythic Uniques, even a smaller report can get attention quickly. Mythic crafting sits at the high-value end of Diablo 4 item progression, so players are naturally going to pay attention when someone says a crafted Mythic may not count the way it should. That last sentence is an inference based on the item’s role in Diablo 4 progression, not an official Blizzard statement.

The Season Journey angle is what makes this sting

The “non-Ancestral” wording is eye-catching, but the real sting may be the Fabled Power part. If a crafted Mythic fails to count for a Season Journey step, that changes the story from “weird item state” to “possible progress blocker.” Based on the current report, that appears to be exactly what the player is alleging.

That also makes this a cleaner article angle than a generic “players are unhappy” piece. There is a specific item, a specific crafting result, and a specific seasonal task that allegedly fails afterward. For Diablo 4 bug coverage, that level of detail usually makes a report more readable and more useful to other players trying to figure out whether the same thing just happened to them. This is an editorial inference based on the available report.

No public Blizzard fix is visible yet

In the sources reviewed here, there is no visible Blizzard reply in the thread and no indication on the forum index that the issue has already been officially resolved. The post appears as a current bug report, but not one with a public fix note attached.

That means the safest framing right now is straightforward: a Diablo 4 player has publicly reported that crafted Mythic Uniques can come out non-Ancestral and may fail to grant Season Journey credit, but Blizzard has not publicly confirmed the cause in the source reviewed here.

One to watch, not one to overstate

This is exactly the kind of Season 12 story that deserves attention without fake certainty. The report is fresh, specific, and tied to a high-value system, but it is still early. So for now, this should be treated as a player-reported issue, not a confirmed systemic Blizzard-documented bug hitting everyone.

Still, if more players begin reporting the same crafted Mythic behavior, or if Blizzard acknowledges it in a follow-up reply or patch note, this could turn into a much bigger endgame problem very quickly. And for anyone sitting on materials and planning a big Mythic craft, that is enough to make the current report hard to ignore. 

Read More

Diablo Immortal Players Are Still Trying to Figure Out What Versatile Rings Actually Changes

Diablo Immortal Patch 4.3 added a limited-time event called Versatile Rings, and on paper it sounds simple enough: certain rings can temporarily gain a socket that accepts Normal Gems of any color. In practice, though, the wording has already sparked confusion across the community, with players debating whether Blizzard is adding an extra socket, changing an existing one, or quietly reshaping ring optimization in a much bigger way than the short event description suggests.

Blizzard’s official wording is very specific. Between March 19, 2026 and May 13, 2026 server time, all 3+2 and 3+3 quality Rings obtained through any means will feature a versatile socket, allowing Gems of any color to be socketed into them. Blizzard also describes the effect as a temporary enhancement meant to offer more flexibility for build customization and experimenting with gem combinations.

Why players are confused

The confusion starts with one basic question: does “a versatile socket” mean a brand-new additional socket, or does it mean one of the ring’s sockets becomes universal? Blizzard’s event description does not spell that part out in a step-by-step way, and that gap is exactly where community debate has taken off.

Reddit discussion around the Patch 4.3 notes shows players immediately trying to interpret the practical impact. Some commenters framed the change as a major quality-of-life boost for set item optimization, while others warned that players might be misunderstanding it and expecting more than the event actually provides. In other words, this is not a case where the community is arguing over whether the event exists. It is a case of players trying to pin down what the event really means once it hits actual gear.

What Blizzard has actually confirmed

The official details Blizzard has published are narrower than some of the early player speculation. Blizzard has confirmed three important things: the event is temporary, it only applies during the March 19 to May 13 event window, and it affects 3+2 and 3+3 quality rings obtained during that period. Blizzard has also confirmed that the relevant socket can accept Normal Gems of any color.

What Blizzard has not clearly explained in the source text reviewed here is the exact visual or mechanical presentation beyond that. The official post does not walk players through before-and-after examples, does not include a detailed socket diagram in the search result text, and does not directly address the biggest community misunderstanding: whether ring owners are gaining a true extra slot or gaining more freedom within an existing socket structure. That is why players are still parsing the wording so closely.

Why this matters more than it sounds

This is not just one of those patch-note nitpicks where players are arguing over grammar for sport. Rings are one of the more annoying gear slots to optimize in Diablo Immortal because players want the right quality, the right affixes, and the right gem setup at the same time. Blizzard’s own forum post even calls out the idea that rings are especially difficult to roll “correctly,” which helps explain why this event is getting more attention than a minor seasonal gimmick normally would.

That is also why the event has sparked so much interest from creators and community theorycrafters. Several recent videos have highlighted Versatile Rings as one of the most important takeaways from the March update, specifically because they may change how players think about ring farming, gem placement, and set-item flexibility. Those creator reactions do not settle the exact mechanics by themselves, but they do show that the feature has landed as more than just background patch-note filler.

The likely takeaway, at least for now

Based on Blizzard’s wording, the safest reading is that eligible rings gained during the event receive one socket with universal gem-color flexibility, not that the event is secretly showering players with permanent bonus slots. That interpretation matches the phrase “a versatile socket” much more naturally than “extra sockets everywhere,” but it is still an inference from Blizzard’s wording rather than a direct explicit line saying “this does not add a new total socket count.”

That distinction matters because the hype changes depending on which version players imagine. If it is flexibility, the event is a strong quality-of-life feature and build experiment tool. If it were extra socket count, it would be much closer to a mini gear revolution. Right now, the community appears to be stuck somewhere between those two expectations.

A smart event, even if the wording could be cleaner

Even with the confusion, Versatile Rings still looks like one of the more interesting official features in Patch 4.3. It gives players a reason to farm rings during the event window, encourages build experimentation, and lightly reduces some of the gear frustration tied to socket color restrictions. That is an inference based on Blizzard’s event description and the early community reaction, not a formal Blizzard promise about long-term balance impact.

For now, the cleanest summary is this: Blizzard has introduced a temporary Versatile Rings event in Diablo Immortal, but players are still debating exactly how transformative it is because the wording leaves room for interpretation. In a loot-heavy game where tiny wording differences can mean the difference between “nice bonus” and “drop everything and farm now,” that kind of ambiguity gets noticed fast.

Read More

Diablo Immortal’s Challenge of Equals Is Live, and It Might Be Patch 4.3’s Most Interesting Feature

Diablo Immortal’s latest major update has a lot going on, from the new The Taking story content to temporary boss events and ring changes. But as of March 23, the most interesting part of the update may be the one aimed squarely at PvP: Challenge of Equals, a new Bout of Realms variant that normalizes player power and shifts the focus toward execution, team play, and build choices instead of raw account advantage.

That alone makes it stand out. Blizzard describes Challenge of Equals as a new 8v8 PvP tournament where player power is normalized to emphasize “moment-to-moment combat and mechanical skill.” Sign-ups began on March 19, and the tournament itself runs March 23–27.

What Challenge of Equals actually changes

Blizzard is not just tweaking numbers around the edges here. The official rules for Challenge of Equals cut away a big chunk of progression-based power while still keeping some of the class and build identity intact. According to Blizzard, Legendary affixes and set bonuses remain active, while Legendary Gem affixes are standardized to Rank 10 effects and Five-Star Legendary Gems are normalized to Two-Star values.

At the same time, Blizzard says several major systems are disabled for the event, including Runes, Normal Gems, Charms, and Resonance. Bonuses from Deeds of Valor, Legacy of the Horadrim, and Ancestral Tableau also do not apply. In plain English, that means the mode is built to strip away a lot of the long-tail stat layering that normally defines Diablo Immortal PvP. That last sentence is an inference based on Blizzard’s listed rules, not a direct Blizzard quote.

Why this feels different from a normal Immortal PvP update

The key word here is not just “tournament.” It is equalized. Blizzard says the mode is designed for “all players, old and new,” and the official preview frames it as a response to demand by opening with “You asked for it, and now it’s here!”

That matters because it gives Diablo Immortal something a little different from its usual PvP updates. Instead of another mode that mostly rewards account depth and long-term optimization, Challenge of Equals appears intended to create a cleaner test of rotations, positioning, target focus, and coordination. That is an inference from the normalization rules Blizzard published, but it is also the clearest reason this mode feels more interesting than a routine event calendar item.

Blizzard is also giving players ready-made competitive builds

One smart part of the rollout is Elite Slayer Loadouts. Blizzard says these loadouts are based on real builds from top contributors in Cross-Server Bout of Realms and Battlegrounds, and all participants can choose from that curated roster. The goal is pretty obvious: let newer or less PvP-focused players enter the mode without first spending ages theorycrafting or assembling a perfect setup from scratch.

That does not magically guarantee perfect balance, of course. But it does lower one of the usual barriers to trying competitive PvP in the first place. Instead of “good luck, hope your build is ready,” Blizzard is offering an on-ramp. In a game that can look intimidating from the outside, that is not nothing. The first and third sentences here are interpretation based on Blizzard’s stated loadout system.

It is part of a much bigger March update

Challenge of Equals is arriving as part of The Taking, Diablo Immortal’s March 2026 update. Blizzard’s official preview ties the patch to a new main quest, the Rocky Waste area, Horrid Transformations for select zone bosses, and other limited-time systems like Versatile Rings and Suffering’s Rebirth. A Battlegrounds seasonal refresh is also scheduled for April 2026, with Blizzard teasing gameplay rhythm changes and new visual themes for both Classic and Convoy maps.

That wider context is important. This is not a one-off PvP experiment dropped into a quiet week. It is part of Blizzard’s broader push to make Patch 4.3 feel like a meaningful content beat rather than just another maintenance-cycle update. Third-party MMO coverage of the patch also highlighted Challenge of Equals as one of the headline additions alongside the new quest content and enhanced zone bosses.

Why this may be the official angle worth watching

If you have been looking for a Diablo Immortal story that is not just another bug report, shop issue, or technical problem, this is probably it. On paper, Challenge of Equals gives Blizzard a chance to show that PvP in Diablo Immortal can be exciting when the playing field is tightened and the match itself matters more than everything built around it. That is an interpretation based on Blizzard’s published format and rules, not a confirmed outcome.

Whether it actually lands that way will depend on how players respond once matches are underway between March 23 and March 27. Blizzard has already said it will continue monitoring feedback and encouraged players to share their thoughts on the official Diablo Immortal Discord. So even if this mode starts as a limited event, it feels like the kind of feature Blizzard will be watching closely for future PvP direction.

For now, though, the headline is simple: Challenge of Equals is live, it is power-equalized, and it may be the most interesting official Diablo Immortal angle in Patch 4.3 right now.

Read More

Diablo 4 Players Say Activated Lair Locations Are Not Always Showing on the Map in Season 12

Diablo 4 Season 12 already has no shortage of player-reported headaches, and now some players are saying the game is sometimes failing at one of the most basic jobs possible: showing them where the activity actually is. A fresh Blizzard forum report says an activated Lair-related activity did not appear on the map at all, leaving the player hunting for the entrance manually for around ten minutes.

The wording in that thread gets a little messy, which honestly feels very Diablo 4 Season 12. One reply assumed the player meant a fixed boss lair such as Lord Zir, while the original poster later clarified that it was “not a boss” but “a key,” suggesting this may be tied to an activated key or sigil-based activity rather than a permanent boss marker. Even so, the core complaint is simple: the player activated content and the map did not clearly show where to go next.

Why this matters more in Season 12

This is not just a minor navigation annoyance. Blizzard’s 2.6.0 patch made Lair Bosses and Bloodstained Sigils a much bigger part of the current seasonal loop, with the official patch notes highlighting stronger Lair Bosses, Bloodstained versions of activities, and new rewards tied to that endgame structure. When the season pushes players toward sigil-driven content and boss runs, map clarity matters a lot more than usual.

That is what gives this story some weight. If a player consumes or activates an item and the activity does not properly point them to its location, the problem is not just inconvenience. It risks wasting time, breaking momentum, and making seasonal systems feel more confusing than they should.

Players are already trying to guess the workaround

The first forum replies immediately turned into troubleshooting. One player suggested the issue might actually be Lord Zir’s Ancient’s Seat entrance, which can be easy to miss if you are expecting a more obvious marker. Another reply tried to narrow down whether the original report was really about a Nightmare Dungeon key rather than a true boss lair. In other words, the community response was less “here is the confirmed fix” and more “hold on, what exactly vanished from the map?”

That uncertainty is part of the problem. If players cannot quickly tell whether they are dealing with a hidden entrance, a filter issue, a UI problem, or an outright bug, the game is creating friction where it should be giving direction. A good endgame loop can be hard. Figuring out whether the map is lying to you is not the fun kind of difficulty.

There is some history here with Diablo 4 map visibility issues

This is also not the first time Diablo 4 players have reported map markers behaving strangely. Older forum discussions about world bosses not showing on the map pointed to a mix of possible causes, including map filters, needing to teleport once after logging in, stronghold unlock status, or zoom level quirks. Those older posts are not proof that the current Season 12 issue is the same bug, but they do show that map visibility problems are not exactly a brand-new genre in Sanctuary.

Reddit discussions from earlier this year show similar confusion around Lair Boss markers, with some players saying the issue turned out to be map filters rather than the activity truly disappearing. Again, that does not confirm the current report is just user error. It does, however, suggest that Diablo 4 still has enough map and filter weirdness that players often have to troubleshoot the interface before they can trust what they are seeing.

Blizzard has fixed at least one related map issue, but not this one

Blizzard’s latest patch notes do show at least one relevant user interface fix: the developer says it fixed an issue where clicking the View on Map button from Season Rank did not work while inside a dungeon. That is not the same as the current player report, but it does show Blizzard has already been patching map-navigation problems around seasonal UI flows.

What the current public patch notes do not show is a specific listed fix for activated Lair locations, keys, or sigil-based map targets failing to appear after activation. So for now, this stays in the “player-reported issue” category rather than the “officially acknowledged and fixed” bucket.

The real issue may be clarity as much as the bug itself

Even if this turns out to be a mix of edge cases rather than one single defect, it still points to the same design problem: Season 12 is asking players to engage with more layered activity types, but the game is not always making those pathways obvious. When a player activates something and immediately has to wonder whether the marker is hidden, filtered, bugged, or just tucked inside a weird sub-zone, that is a usability problem whether or not Blizzard classifies it as a formal bug. That last part is an inference based on the reports and the current patch notes, not an official Blizzard statement.

For now, the safest summary is this: at least some Diablo 4 players say activated Lair-related content is not always showing up clearly on the map in Season 12, and there is no specific public fix listed for that exact issue yet. In a season built around chaining high-end activities efficiently, that is the kind of problem players notice fast. 

Read More

Diablo 4 Players Say Imprinting Is Downgrading Aspect Rolls in Season 12

Diablo 4 players are reporting what looks like one more nasty itemization problem in Season 12, and this time the frustration is hitting right at the Occultist. According to several player reports on Blizzard’s forums, some imprinted Aspects are not carrying over at their expected values, even when the Codex entry is already upgraded to a higher roll.

The most specific fresh report comes from a Druid player who said a maxed Retaliation Aspect showing 75% in the Codex was being applied as 65% on a regular Legendary ring. The same post claimed the situation was even worse on Bloodied Legendary items, where the Aspect allegedly dropped all the way to its minimum roll.

What players say is happening

The broader pattern across forum posts is pretty consistent: players say they unlock or upgrade an Aspect in the Codex, go to imprint it onto gear, and then see a lower value than expected on the finished item. In several reports, the problem appears especially tied to Bloodied items, one of Season 12’s headline gear features.

One Blizzard forum thread from March 12 described Bloodied items receiving the lowest possible version of an Aspect even when the player’s stored version in the Codex was much higher. Another poster in the same thread said they were also seeing incorrect values on some non-Bloodied items, which lines up with the newer March 22–23 complaint about normal Legendaries also being affected.

That matters because this is not just a cosmetic annoyance. For many builds, a downgraded Aspect is a direct power loss. If players are burning materials and imprinting onto gear only to end up with weaker values than their Codex suggests, that can turn gearing into a very expensive guessing game. That concern is also showing up in community discussion on Reddit, where players have been talking about Bloodied gear imprinting at minimum values rather than the expected upgraded numbers.

Why Bloodied items are at the center of this

Bloodied items are not some side mechanic buried in a patch note footnote. Blizzard positioned them as one of the key parts of Season 12, with the official season blog highlighting Bloodied Items alongside Killstreaks and Bloodied Sigils as major features of Season of Slaughter. Blizzard’s public patch notes also call out a new Bloodied affix for all classes on Bloodied items of at least item power 750.

That is exactly why this issue is getting attention. When a season is built around a featured item type, anything that makes those items feel risky, weak, or unreliable lands harder than a random edge-case bug. Several forum posts even suggest some players are avoiding imprinting on Bloodied gear entirely until the behavior is clarified or fixed.

Is it only visual, or actually broken?

Right now, that part is still unclear. Some players have speculated that the displayed values might be wrong while the hidden effect is working properly, but others are treating it like a real mechanical downgrade because the resulting item visibly shows the lower roll after imprinting. At least from the public reports, there is no clear consensus yet.

That distinction matters. A display bug is annoying. A real value-loss bug is much worse, because it changes actual player power and can waste materials on gear that should have been an upgrade. Based on the current reports, players clearly believe the issue is more than just weird tooltip math, but Blizzard has not publicly confirmed the cause in the sources reviewed here.

No clear fix in the current public patch notes

Blizzard’s current public Diablo IV patch notes include recent Season 12 updates such as reduced Bloodsoaked Sigil difficulty, improved Bloodstained rewards, and a fix for Kurast Undercity Tributes dropping as Bloodied. In the patch notes reviewed, there is no listed fix specifically for Bloodied or normal Legendary Aspect imprinting applying lower-than-expected values.

That does not prove a fix is not coming, of course. It just means players dealing with this right now do not have an official note they can point to yet saying the problem is resolved. Until that changes, this is likely to stay one of those quietly painful Season 12 issues that hits build crafting harder than it first sounds.

What to watch next

For now, the safest framing is simple: players are reporting that Aspect imprinting can downgrade rolls in Season 12, especially on Bloodied items, and Blizzard’s public patch notes do not yet show a named fix for it. That makes this a player-reported problem, not a confirmed official Blizzard diagnosis.

If more reports keep stacking up, or if Blizzard acknowledges it in a forum reply or future hotfix, this one could quickly move from “annoying gearing issue” to one of the more important Season 12 itemization stories. For a season built around Bloodied loot, that is not exactly ideal.

Read More

Diablo 4 Players Say Bloodmarking Still Is Not Working Properly in Season 12

 

Another Diablo 4 Season 12 PvP complaint is picking up traction on Blizzard’s own forums, and this one goes straight to the core of how the Fields of Hatred are supposed to work. A fresh technical support thread titled “Cannot Bloodmark” says Bloodmarking works normally in Eternal, but in Seasonal play it is greyed out and marked “Not available” on the emote wheel.

That matters because Bloodmarking is not just a cosmetic toggle or side curiosity. It is tied directly to Diablo 4’s PvP structure in the Fields of Hatred, and current Blizzard forum activity suggests players are still actively running into problems around it in Season 12. Blizzard’s latest topic pages for March 22–23 continue surfacing “Cannot Bloodmark” alongside another thread titled “PvP Unavalble - cannot enable bloodmarked state.”

What players are reporting

The clearest current report comes from the March 22 thread itself. The player says Bloodmark works fine on Eternal characters, but on Seasonal characters the option is unavailable and appears greyed out on the emote wheel. They also say reinstalling the game made no difference.

That alone would be enough for a small story, but it does not appear completely isolated. Blizzard’s latest topics page also lists a separate PvP-related bug thread explicitly saying players cannot enable bloodmarked state, and the general forum top page still shows Cannot Bloodmark among the newer Diablo 4 issues getting attention.

This is not the first time players have raised it

What makes this more interesting is that it seems to fit a broader Season 12 PvP complaint pattern rather than appearing from nowhere.

A separate thread from a few days earlier, “Why Bloodmarker PvP Unavailable?”, shows players already discussing Bloodmark being unavailable in Seasonal while still available in Eternal. In that discussion, one player explicitly says “Bloodmark is still available for Eternal players”, while others argue Season 12 PvP feels altered or effectively disabled in practice. That is all player discussion, not Blizzard confirmation, but it shows this issue has been circulating for several days now.

Why this matters more than it sounds

On paper, a Bloodmark toggle issue might sound smaller than missing Paragon Points or broken seasonal rewards. In practice, it hits one of the few systems that defines how Diablo 4’s PvP spaces are supposed to function.

The Fields of Hatred are built around risk, hostility, and the possibility of direct player confrontation. If Bloodmarking is unavailable in Seasonal, then players are not just losing one optional button. They may be losing access to an important part of the PvP rule set and, depending on the intended behavior, part of the mode’s identity. That is an inference based on the role Bloodmarking plays in PvP and the player reports above.

It also lands at an awkward time. Season 12 already has players questioning reward reliability, progression tracking, and general system stability. A PvP-state issue feeds neatly into that larger mood, especially because it touches a mode that is already more niche and easier for frustrated players to abandon.

Is this a confirmed bug or an intentional change?

Right now, the honest answer is: it is still unclear from public evidence alone.

The forum threads clearly show that players are experiencing Seasonal Bloodmark as unavailable while Eternal still works, but the sources reviewed here do not show a Blizzard explanation saying whether this is a confirmed bug, an intentional temporary restriction, or a behavior tied to another Season 12 PvP rule change. So the safest framing remains: active player reports suggest Bloodmarking is not working properly in Seasonal play.

That distinction matters. There is enough here for a solid player-report story, but not enough to claim Blizzard has already confirmed the exact cause.

Why this is worth covering now

This makes a strong quick-hit article because the complaint is easy to grasp and it adds a fresh PvP angle to a Season 12 conversation that has otherwise been dominated by rewards, bugs, and progression headaches.

Players do not need a long theorycrafting breakdown to care about Bloodmarking being unavailable. They just need to know whether PvP is working the way it is supposed to in Seasonal mode. Right now, Blizzard’s own forum pages suggest the answer is still shaky enough that players are posting fresh reports about it on March 22–23.

If Blizzard clarifies or fixes it soon, this may end up as one more strange Season 12 side note. If not, it could become part of a broader complaint that even Diablo 4’s more niche systems are feeling unreliable this season. 

Read More

Diablo 4 Players Say Chapter 7 Gilded Laurels Can Disappear After Claiming in Season 12

 

Diablo 4 Season 12 keeps piling up reward-related complaints, and one of the newest ones is especially awkward because it hits a cosmetic-style progression reward that players expected to be safely unlocked once claimed. A fresh Blizzard forum bug report from March 23, 2026 says Gilded Laurels from Chapter 7 disappeared after claiming.

According to the report, the game’s UI continues to show unclaimed rewards even though nothing is there, and the player also says they cannot see the Laurels on other players either. That has led them to suspect the issue may be a broader display or UI problem rather than a simple one-character glitch. At this stage, that is still a player theory, not an official Blizzard diagnosis.

What the player is reporting

The current report is fairly direct. The player says the Chapter 7 Gilded Laurels disappeared after being claimed, while the UI still behaves as if something remains unclaimed. They also note that they cannot see the Laurels on other players, which is why the report speculates about a possible wider display issue.

The bug report is now visible across Blizzard’s current Diablo IV forum listings, including the PC Bug Report page, the broader latest topics feed, and the current pc tag index. That gives the story a little more weight than a buried one-off complaint, even if it is still just one main thread for now.

Why this matters more than “just cosmetics”

On paper, Laurels disappearing might sound smaller than missing Paragon Points or broken progression objectives. But reward-visibility bugs still matter because they hit the same underlying problem: players stop trusting whether the season is correctly tracking and preserving what they earned.

That is especially true in Season 12, where Blizzard’s current forum pages are already crowded with bug reports about missing rewards, missing Paragon Points, and other progression irregularities. A cosmetic or title-adjacent reward issue lands differently when it appears inside that wider pattern. It starts to feel less like “one visual oddity” and more like another example of reward reliability being shaky.

There may already be a related Laurels display issue

This is where the story gets a little more interesting.

A separate Blizzard forum thread from five days ago says Golden Laurel wings stop displaying correctly after changing Torment levels. In that report, the player says the golden upgraded laurel visuals reverted after switching tiers and would not return. That is not the same complaint as Laurels disappearing entirely after Chapter 7 claiming, so it would be wrong to say Blizzard has confirmed both are one bug. But it does suggest Laurels-related display issues may not be completely new to current Season 12 forum traffic.

The safest read is that there are now multiple public player reports involving Laurel visuals or Laurel reward display behavior, which makes the newest Chapter 7 disappearance thread feel less isolated than it would on its own.

This fits a wider reward-reliability pattern in Season 12

The bigger Diablo 4 story here is not just one vanished Laurel reward. It is that Season 12 keeps producing reports where rewards are claimed, completed, or supposedly granted, but players still feel something is missing on the back end.

Blizzard’s current forum listings around March 22–23 show threads about missing Paragon Points, season rewards not being granted, and now Gilded Laurels from Chapter 7 disappearing after claiming. Those are not all the same issue, and Blizzard has not publicly tied them together in one official known-bugs list from the sources checked here. But from a player perspective, they all feed the same impression: reward tracking feels unreliable.

No clear public fix yet

Based on the sources reviewed here, there is no visible Blizzard post or patch-note entry that specifically says the Chapter 7 Gilded Laurels disappearance issue has been acknowledged or fixed. That means the cleanest framing remains a cautious one: this is a fresh player-reported Season 12 reward/display bug on Blizzard’s own forums, with some related Laurels display chatter also visible in recent days.

That is enough for a story, but not enough to claim Blizzard has confirmed a universal Season 12 Laurel failure.

Why this is worth covering now

This makes a solid quick-hit article because the complaint is easy to understand and it plugs directly into an already active Season 12 conversation. Players do not need a giant systems explainer to care about a reward disappearing after claiming. They just need to know whether one more part of the season’s reward track may be acting weird.

Right now, the answer appears to be yes: the thread is fresh, visible in Blizzard’s latest pages, and it lands in a week where Diablo 4 reward-related complaints clearly are not going away on their own.

Read More

Diablo 4 Players Say Season 12 Journey Rewards Are Still Missing Paragon Points

Diablo 4 Season 12 has already produced a steady stream of reward and progression complaints, and one of the clearest fresh examples is now showing up again on Blizzard’s own forums: some players say they are still missing 4 Paragon Points from Season Journey rewards.

What makes this worth covering is that it no longer looks like one random post from one unlucky account. Blizzard’s current Diablo IV forum pages on March 23, 2026 list a fresh PC bug report titled “Missing 4 Paragon Points from Season 12 Journey Rewards,” while older but closely related reports from March 14–15 describe the same missing 4-point deficit after Chapter 5 or other Season Journey progress.

In other words, this is starting to look less like a one-off miscount and more like a recurring Season 12 reward problem players keep running into.

What players are reporting

The basic complaint is very consistent across multiple Blizzard forum threads.

In one March 14 report, a player says Chapter 5 correctly awarded the pet, reward caches, and Smoldering Ashes, but the +4 Paragon Points reward never appeared. Another March 14–15 thread says the player expected 203 total points based on character level plus Season Journey rewards, but only had 199. A third report from March 15 describes an even bigger 8-point deficit, suggesting at least some players believe the issue may be happening more than once or across multiple reward steps.

The newest wrinkle is that this has not vanished. Blizzard’s current March 23 bug-report pages still show a fresh PC report with the same missing-Paragon-points theme, which makes it feel like an active problem rather than a complaint that faded out last week.

Why this matters more than a small numbers bug

A missing tooltip is annoying. Missing Paragon Points hits much harder.

Paragon Points are not cosmetic fluff. They feed directly into player power, progression planning, and the feeling that seasonal effort is actually paying off. When players complete the Season Journey and the game appears to skip a stat-power reward, it creates exactly the kind of uncertainty that live-service seasons do not want. This is an inference based on what Paragon Points represent in Diablo 4 progression and the specific forum complaints.

That is also why a “missing 4 points” story travels better than some niche mechanical bug. Players instantly understand the stakes. If the reward is listed and the points are not there, the whole seasonal reward loop starts to feel less trustworthy.

This fits a wider Season 12 reward pattern

The Paragon-point issue does not exist in isolation.

Blizzard’s latest Diablo IV forum pages also show related reward-loss or non-reward threads, including “Gilded Laurels from Chapter 7 disappeared after claiming” and older support-style posts where players say seasonal quest rewards were not granted correctly. There are also continuing Rank VI complaint threads where players specifically mention concern over missing Paragon Point rewards tied to seasonal advancement.

That broader context matters because it suggests the real story is not just one number being off. The broader story is that Season 12 reward reliability is still under pressure, and Paragon Points are simply one of the clearest examples players can point to.

Blizzard forum traffic suggests this is not just one platform problem

Another reason this has enough weight for an article is that it is not limited to a single forum lane.

Relevant reports appear across PC, console, and even forum index pages that surface multiple similar complaint threads. Blizzard’s Xbox-tagged pages still show “Season Journey – Missing 4 Paragon Points from Chapter 5 Reward (Season 12)”, while the current PC bug report page has the newer March 23 thread carrying the same theme.

That does not prove every affected player is hitting the same exact cause, or that Blizzard has confirmed a universal bug across all platforms. But it does support the idea that this is a broader player-reported issue rather than one isolated regional mishap.

No clear public fix yet

Based on the sources reviewed here, there is no clean Blizzard patch-note line or official acknowledgment explicitly saying this missing-Paragon-points problem has been fixed.

That means the safest framing is still the cautious one: these are current player reports on Blizzard’s own forums, backed by multiple similar threads, but not yet matched by a visible official resolution in the public sources checked here.

That distinction matters. It is enough to justify a news story. It is not enough to claim Blizzard has already confirmed every version of the problem or promised a repair timeline.

Why this is worth watching tonight

The reason this makes a good late-night Diablo story is that it is both fresh and easy to understand.

Players do not need a ten-paragraph systems explainer to care about missing Paragon Points. They just need to know whether Season Journey rewards are still behaving oddly. Right now, the answer appears to be yes: the latest Blizzard forum pages still show fresh reports, and they line up with a pattern of similar complaints from the last week.

If Blizzard fixes it soon, this will probably become one more ugly Season 12 footnote. If not, it risks becoming part of a much larger player takeaway: that even when Season 12 rewards say they are granted, players may still feel the game owes them something. 

Read More

Diablo Immortal Players Are Still Reporting Shop and Gem Issues After Patch 4.3

Diablo Immortal Patch 4.3 brought in The Taking, a new story chapter, PvP updates, Rocky Waste, new Legendary Gems, and a long list of feature changes. But while the official spotlight is all about content, Blizzard’s current support and bug-report forums suggest some players are still dealing with a more frustrating side of the update: missing gems and shop-loading problems that have not gone away yet.

The reason this is worth a fresh follow-up is simple. This is no longer just a “post-patch hiccup” angle from launch day. Blizzard’s Diablo Immortal forum listings on March 22, 2026 are still showing active threads like “Lost at least 4 legendary gems after patch,” “Shop tab won't load,” and “Shop still will not load please help.” That makes this feel less like one isolated complaint and more like a continuing support-cluster story.

What players are reporting right now

The current Android-tagged Blizzard forum page is a pretty blunt snapshot of the problem. On the same March 22 listing, it shows “Lost at least 4 legendary gems after patch” under Technical Support, “Shop tab won’t load” under Bug Report, and “Shop still will not load please help” with activity from March 21. It also shows another related gem complaint, “Gem disappeared after gem power transfer,” which suggests the gem side of the problem is not limited to one exact scenario.

That does not prove all of these reports share one cause. It also does not prove every affected player is experiencing the same issue in the same way. But it does support one careful conclusion: fresh, current Blizzard forum traffic is still surfacing gem-loss and shop-access complaints after Patch 4.3 went live.

Why this matters more than a normal support thread

Some support stories stay small because the underlying issue feels minor. Gem complaints usually do not.

Legendary Gems are one of Diablo Immortal’s most important progression layers, and Patch 4.3 itself added new Legendary Gems like Leviathan Tomb, reinforcing how central gem systems remain to the game’s current design. That means a player report about gems vanishing after the patch naturally lands harder than something like a misaligned tooltip or a cosmetic glitch.

The shop complaints matter for a different reason. Even players who are not actively trying to buy something tend to read a broken or non-loading shop tab as a sign that the client is unstable in visible, user-facing ways. When those complaints sit next to gem-loss reports on the same current support pages, the overall picture starts to look rougher than “one unlucky bug post.” This is an inference based on the forum pattern and the types of systems involved.

Patch 4.3 is clearly live, but so are the complaints

Blizzard’s official Patch 4.3 article confirms the update is now live and frames it as a major 2026 content step, centered on The Taking, the Rocky Waste, PvP refreshes like Siege of Corvus and Challenge of Equals, new Legendary Gems, and multiple events and quality-of-life updates.

That is what makes the support angle more interesting, not less. On paper, Patch 4.3 is a big content push. In practice, at least some current forum users seem more focused on whether their gems are still there and whether the shop loads at all. That disconnect is often what defines a rough patch rollout: the official headline says “look at all this new stuff,” while parts of the player base are stuck asking why core interfaces and progression items feel unreliable. This is an inference based on the official patch scope versus the current support listings.

This still looks like a support-cluster story, not a confirmed universal failure

It is important to keep the framing clean.

The evidence here supports multiple fresh player reports on Blizzard’s own forums. It does not support saying Blizzard has confirmed a universal gem-loss issue across all players, nor that every shop-loading problem is tied to one single verified root cause. The right read is narrower: the complaints are still visible and current after Patch 4.3, and they span both gem-related progression concerns and storefront access.

That is still enough for a useful article, especially because readers care about whether the issue is still active. In this case, the answer appears to be yes: these threads are still sitting in Blizzard’s March 22 forum listings, which is a stronger signal than a one-day flare-up that vanished immediately.

Why this is worth a late-night follow-up

This kind of follow-up works because it answers a practical question players often have after a patch story: did those issues fade out, or are they still happening?

Based on Blizzard’s current support pages, at least some of the gem and shop complaints are still there right now. That makes the angle timely and useful without overstating what Blizzard has or has not formally acknowledged.

If Blizzard resolves these quickly, they may end up as short-lived Patch 4.3 footnotes. If not, they risk becoming part of the update’s reputation, especially because gems and shop access are exactly the kind of high-visibility systems players notice immediately when something feels off. 

Read More