Diablo 4 Players Say the Black Screen Teleport Bug Still Refuses to Die

 

Sanctuary has plenty of horrors already. The loading screen does not need to become one of them.

Diablo 4 has a black screen bug making the rounds again, and this one sounds especially miserable because it tends to hit right after teleporting. According to Blizzard’s own main black screen thread, players are getting dumped into a blank screen while the HUD, cursor, chat, or even music can still keep going in the background. In other words, the game is not fully dead. It is just dead enough to ruin your session.

What players say is actually happening

The reports are pretty consistent. Players say the bug often shows up after teleporting to town or other overworld locations, and the usual fix is the least glamorous one possible: close the game and start over. Several posts in the thread describe the bug hitting multiple times in a single day, with one player saying it now happens every time they play and another saying the game has become “basically unplayable.”

That is what makes this a real story and not just one grumpy forum post. Blizzard’s current PC Bug Report board still lists the black screen teleport thread among the most active Diablo 4 bug topics on April 6, with hundreds of replies and well over 18,000 views. That is a lot of people staring into the void, and not in the philosophical Diablo sense.

Why this one matters more than a random visual bug

A weird animation glitch is funny once. A teleport bug is different, because teleporting is basic Diablo housekeeping. You sell junk, stash gear, hit the occultist, jump back out, and keep the run going. When that loop starts randomly bricking the game, it wrecks the rhythm of play more than a lot of flashier bugs do. Players in the thread say the issue kills momentum, ends runs, and in some cases makes them want to stop the season entirely.

There is also a hardware angle people keep circling. A number of affected players list AMD GPUs, though not every report does, and no official Blizzard post in the thread has pinned the problem on one vendor. So right now, that part stays in the “possible pattern, not confirmed cause” bucket.

Blizzard has at least acknowledged it, but not fixed it

That is the current state of play. In the same forum thread, Blizzard support rep Joynueer asked players to send in FenrisDebug.txt logs by email so the team could narrow the issue down. That is better than silence, but it is not a fix, and players in the thread are clearly past the point where “please send logs” feels comforting. They want the game to stop eating teleports. Fair enough.

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 4 Patch Notes Also Buff Killstreaks and Bloodstained Rewards in Season 12

 

Blizzard’s latest Diablo 4 patch notes have mostly been framed around bug fixes, Bloodsoaked Sigil tuning, and a handful of high-profile Season 12 pain points. But buried in the same update is another angle players may want to pay closer attention to: Season 12’s killstreak system and Bloodstained rewards just got noticeably stronger too.

That matters because some of the loudest early Season 12 discussion has focused on friction, bugs, and reward pacing. This patch does address several of those issues, but it also quietly improves the actual feel and value of the seasonal loop itself. Killstreaks are now easier to maintain across dungeon floors, several Massacre Affixes have been buffed, and Bloodstained rewards are better than before, including guaranteed Bloodied and Ancestral items from Bloodsoaked bosses.

In other words, this is not just a “fix what’s broken” patch. It is also a “make the season feel better to play” patch.

Killstreaks now carry between dungeon floors

One of the most useful changes is also one of the easiest to miss.

Blizzard’s patch notes say killstreaks no longer reset when going between floors in dungeons. That may sound like a small quality-of-life tweak, but for a season built around chaining momentum and stacking power through combat flow, it is actually pretty significant. Before this, moving between floors could break the rhythm in a way that made the seasonal mechanic feel less rewarding than intended. Now, that flow should be much more consistent.

Blizzard also notes that killstreak multipliers are now highlighted in the UI, which should make the system more readable at a glance. That is not a balance buff by itself, but it does make the mechanic easier to follow in the middle of a screen full of demons, explosions, and the usual Diablo visual modesty.

Several Massacre Affixes just got buffed

The patch also improves the actual rewards tied to killstreak tiers.

According to Blizzard, multiple Massacre Affixes were tuned upward. That includes Attack Speed per Killstreak Tier increasing from 6% to 8%, Cooldown Reduction from 3% to 6%, Critical Strike Chance from 5% to 8%, Movement Speed from 7% to 10%, and Resource Cost Reduction from 6% to 10%. Life on Hit and Maximum Life bonuses were also adjusted, and all classes can now encounter a Bloodied Affix that increases their Primary Core Stat by 3% per Killstreak Tier on Bloodied items of at least 750 Item Power.

That is a real shift in how rewarding the seasonal mechanic can feel. It is not just about making killstreaks easier to see or slightly less annoying to maintain. Blizzard is also making the payoff more meaningful once players get the system rolling.

Bloodstained rewards are getting better too

The other overlooked line in the patch notes is tied directly to loot value.

Blizzard says Bloodstained now grant better rewards, including guaranteed Bloodied and Ancestral items when defeating Bloodsoaked bosses. That is a pretty important adjustment because early Season 12 complaints were not just about bugs. They were also about whether the risk and time investment of the seasonal content felt worth it.

This change does not necessarily solve every economy complaint players have raised, especially around materials and progression pacing. But it does show Blizzard is not only trying to patch holes. It is also trying to improve the reward proposition of the seasonal loop itself.

Why this angle matters

This is exactly the kind of patch-note sub-angle that can get buried under bigger headlines.

Players see “Bloodsoaked Sigils nerfed” or “Obducite issue fixed” and move on. But for people actually playing Season 12, the more interesting long-term change may be that the season’s signature mechanic is now both smoother and more rewarding.

That could matter a lot for perception. A season can survive some messy launch-week bugs if the core loop starts feeling better once the fixes land. If killstreaks are easier to maintain, clearer to read, and tied to stronger affixes and loot outcomes, then Season 12 may start to feel less like a pile of rough edges and more like a season with real momentum.

That is still partly an inference, of course. The patch notes tell us what changed, not how players will ultimately feel about it. But the design intent is pretty clear: Blizzard is trying to make the seasonal loop more rewarding, not just less broken.

This patch is doing more than damage control

That may be the biggest takeaway.

Blizzard’s latest Diablo 4 patch is easy to read as a reaction patch, and in many ways it is. It fixes progression problems, addresses reward inconsistencies, and tones down some of the worst friction. But it also contains meaningful buffs to Season 12’s core mechanics, and that makes it more than a cleanup pass.

If these changes land well, they could help reshape the conversation around Season 12 from “what’s broken now?” to “is the season finally becoming worth the effort?” That is a much better place for Blizzard to be.

And for players still deciding whether to keep pushing Bloodstained content, the answer after this patch might be a little more favorable than it was yesterday.

Read More

Diablo 4 Players Say a Forgotten Remains Nightmare Dungeon Event Can Soft-Lock in Season 12

 

Diablo 4 Season 12 has already produced no shortage of bug reports, and now another smaller but still nasty one is making the rounds on Blizzard’s own forums: a player says a Forgotten Remains Nightmare Dungeon event tied to Subo can get stuck because one enemy will not die.

The report showed up in Blizzard’s PC Bug Report section on March 21 under the very subtle title “Forgotten Remains NMD Event with Subo Bugged - Enemy Will NOT Die! Fix Your Broken Game Blizzard!” That thread is now also visible in the current bug-report listings, which is enough to treat it as a fresh live issue players are surfacing during the current Season 12 cycle.

What the player is reporting

The core complaint is simple: during a Forgotten Remains Nightmare Dungeon event involving Subo, one enemy allegedly becomes impossible to kill, which appears to trap or soft-lock the encounter. The thread itself frames this as another example of older unresolved bugs carrying over while new Season 12 problems pile on top.

At the moment, this should be treated as a player bug report, not as a fully confirmed Blizzard-wide incident. The public evidence here shows a fresh report in the official bug forum and current visibility in Blizzard’s listings, but not a blue-post confirmation explaining the cause or offering a fix timeline.

Why this kind of bug matters even if it looks small

On paper, one unkillable enemy in one dungeon event sounds like a niche problem. In practice, these are exactly the bugs players hate most in an ARPG.

A tuning issue can feel annoying. A soft-lock feels like theft. If a run stops because one enemy refuses to die, players do not just lose efficiency. They lose time, momentum, and trust that the content will actually resolve correctly once they engage with it. That is especially frustrating in seasonal content where players are repeatedly pushing dungeons for rewards, progress, or materials. This is an inference based on the reported behavior and the role dungeon events play in Diablo 4’s loop.

It fits an existing Season 12 pattern

This is also not landing in a vacuum.

Blizzard’s latest Diablo IV forum pages still show active player discussion around missing rewards, Rank progression failures, PvP problems, lag, and other bug reports. The Forgotten Remains/Subo complaint sits inside that broader environment, where even smaller encounter-level issues can feel bigger because players are already primed to expect friction.

There is also a separate community-maintained Season 12 List of Known Bugs thread that has become a gathering point for reports ranging from group-play problems to dungeon and encounter issues. The Forgotten Remains/Subo bug appears inside that discussion as well, which suggests it is at least getting noticed by the part of the player base already tracking Season 12 problems closely.

The bigger issue is reliability, not just one monster

That is what makes this article worth writing.

The real story is not “one monster bugged out.” The real story is that Season 12 keeps collecting reports where content does not complete the way players expect. Sometimes it is progression not counting. Sometimes it is rewards not being granted. Here, it is an encounter that reportedly cannot finish because one enemy will not die. They are different bugs, but they all point at the same broader player concern: can the season’s content be trusted to function cleanly? This last point is an inference based on the pattern of current reports.

No public fix yet, but it is the kind of report Blizzard will want to squash quickly

Based on the sources reviewed here, there is not yet a public Blizzard confirmation that this specific Forgotten Remains/Subo issue is fixed or formally recognized in patch notes. That means the cleanest framing is still cautious: this is a fresh official-forum player report about a Nightmare Dungeon event soft-lock in Season 12.

If it stays isolated, it may never become more than a minor footnote. But if more players run into the same event behavior, it becomes exactly the sort of bug that travels fast because the complaint is so easy to understand: I did the dungeon, but the game would not let the fight end. And in Diablo, that usually gets attention a lot faster than one more awkward tooltip.

Read More

Diablo 4 Players Are Still Asking for Better Obducite Drops Even After the Latest Fixes

Blizzard has already moved to address one Season 12 Obducite problem, but if the current player conversation is any guide, that fix did not settle the issue. Fresh Diablo 4 forum posts from March 22 show players still asking Blizzard to increase Obducite drops, even after the recent patch targeted Bloodied Nightmare Dungeon reward problems.

The latest push is a new Blizzard forum thread titled “Increase Obducite Drop Rate!” In it, the poster calls Obducite a “choke point in season 12” and argues there is no real need for that kind of bottleneck in what they describe as a lighter, more fun seasonal setup. That is just one thread, but it lands on top of several similar March complaints about the same material economy.

Blizzard did fix one part of the problem

This is what makes the story interesting as a follow-up rather than a repeat.

In Blizzard’s latest Diablo 4 patch notes, the studio says it fixed an issue where Bloodied Nightmare Dungeons did not have the same chances for dropping Obducite as normal Nightmare Dungeons. That was a real, specific reward problem, and Blizzard clearly treated it as something worth correcting.

So in one sense, players already got movement on the Obducite front. But the fresh March 22 forum reaction suggests many do not see that fix as the whole answer. Instead, the complaint seems to be shifting from “this source is bugged” to “the overall Obducite economy still feels too stingy.” That distinction is not directly stated by Blizzard; it is an inference based on the timing and wording of the new forum posts.

The newer complaints are broader than one dungeon issue

That broader frustration has been building for days.

A March 15 thread titled “The obducite drop rate” asks whether the current drop rate reduction is permanent and questions why Blizzard did not instead add some form of material conversion. A March 13 thread, “Obducite please,” says farming it this season feels almost impossible, while another March 16 discussion argues that Obducite simply is not fun to farm in its current form and says Nightmare Dungeons no longer feel worth running for it.

That matters because it shows the March 22 thread is not some random new outburst from nowhere. It looks more like a continuation of a wider player mood: even after Blizzard fixed one reward inconsistency, some players still think the material pacing itself is off.

Why Obducite keeps turning into a flashpoint

Obducite complaints keep resurfacing because Masterworking materials are not optional fluff. They sit right in the middle of character progression.

If the flow feels bad, the whole season can start to feel sticky in the wrong way. Players do not just see fewer materials. They feel slower upgrades, less momentum, and more friction between “I finished the content” and “my build actually moved forward.” That is an inference based on how Obducite is discussed in the current forum threads, where players repeatedly frame it as a bottleneck rather than a bonus reward.

That is also why the newest March 22 thread matters more than its size might suggest. On its own, it is a modest forum post. In context, it reinforces the idea that Blizzard’s fix addressed a symptom, while at least part of the community still sees the underlying economy as the bigger issue.

Players are not all complaining about the exact same thing

It is worth keeping the nuance here.

Some players appear to be talking about bugged or inconsistent sources of Obducite. Others are talking about intentional drop rates that they simply dislike. Others still are comparing Season 12 unfavorably with earlier seasons where Obducite felt easier to stack in bulk. These are related complaints, but they are not identical.

That means the cleanest framing is not “Blizzard failed to fix Obducite.” The cleaner and more accurate angle is this: Blizzard fixed one documented Obducite-related issue, but players are still arguing that the resource economy feels too tight. That is a better fit for what the current public evidence actually shows.

This is turning into a pacing debate, not just a bug report

That may be the real story now.

Once a complaint moves beyond “this one thing is broken” and into “the season feels worse because of this material economy,” it becomes more of a design and pacing conversation than a straightforward technical issue. The March 22 call to increase Obducite drops fits that pattern exactly, especially when read alongside earlier threads asking how players are even supposed to farm the material efficiently this season.

For Blizzard, that is a trickier problem to solve. A bug can be patched. A progression economy players broadly find unfun usually needs a more judgment-heavy response. And right now, the forum traffic suggests the Obducite conversation is drifting into that second category. That last point is an inference based on the pattern of player complaints and the difference between Blizzard’s specific fix and the broader community reaction.

Why this follow-up matters

The reason this is worth a new article is simple: it is not the same as the earlier Obducite complaint story.

Before, the focus was on direct frustration with Season 12 farming. Now the angle is sharper: Blizzard has already responded to one Obducite issue, and players are still not satisfied. That turns the conversation from pure complaint into something more interesting — whether Season 12’s Obducite economy is merely bugged in places, or whether it is tuned in a way players fundamentally do not enjoy.

If the fresh March 22 thread stays small, this may just be one more grumble in a noisy season. If more players pile on, though, Obducite could stick around as one of those annoying Season 12 talking points that Blizzard technically addressed, but not enough to make the conversation go away.

---

SEO Package

Read More

Diablo 4 Players Say PvP Hostility Is Not Working Properly in Season 12

Diablo 4 Season 12 has generated plenty of discussion around progression bugs, dungeon tuning, and patch fixes, but another smaller issue is now showing up in the player conversation: some players say they cannot become hostile in PvP zones at all. That might sound niche compared with bigger seasonal complaints, but in the Fields of Hatred, hostility is not a minor extra. It is part of how the mode is meant to function.

The clearest current thread is Blizzard forum post “Because I can’t become hostile in PvP zones,” where the original poster says they are unable to set their status to hostile, which prevents access to certain PvP interactions and makes it impossible to take part in player-run PvP tournaments happening this season. The post first appeared on March 11, but it is still active and was surfaced again in the March 22 forum listings, which gives it enough current traction to treat as a live community issue rather than a forgotten one-post complaint.

What players are reporting

The main report is straightforward: the player says they cannot toggle hostile status in PvP zones, and that this blocks them from opening certain PvP chests and participating in competitive events built around the system. A reply in the thread asks whether they tried using the action wheel, which suggests at least some players may see this first as a usability problem rather than an obvious confirmed bug. That uncertainty is important, because it means the safest framing is still “active player report,” not “Blizzard has confirmed PvP hostility is broken for everyone.”

Even so, the topic matters because Blizzard’s own forum activity shows that PvP is not some forgotten side mode this season. A separate March 8 discussion titled “Season 12 PvP and the Butcher Ty Blizzard” shows players actively talking about PvP zones, hostile players, and how the season could push more traffic into the Fields of Hatred thanks to Butcher-related activity and rewards. If more players are being nudged toward PvP, even a limited hostility-toggle issue becomes more relevant than it would be in a quieter season.

Why this matters more than it might look

On paper, a hostility-toggle issue sounds smaller than a bricked progression system. In practice, it cuts directly into the logic of PvP zones.

The Fields of Hatred are built around risk, extraction, and the possibility of being hunted by other players. If someone cannot become hostile when the mode expects that option to exist, the result is not just inconvenience. It changes what content they can access and how they can participate. In the player’s own words, it affects both chest access and tournament participation. That makes it more than a random menu annoyance.

It also comes at an awkward time. Season 12 already has players keeping a closer eye on how reliably its systems work, and current March 22 forum listings still show a heavy mix of complaints about bugs, progression, and seasonal friction. In that context, even a narrower PvP complaint lands harder, because it feeds into the broader sense that players keep running into systems that do not behave as expected.

Is this a bug, or are players missing the correct input?

Right now, the honest answer is: it is not fully clear from public evidence alone.

The original report says the player cannot become hostile. One response immediately points to the action wheel, implying there may be confusion around how the feature is activated. But the thread remaining visible and active in current listings suggests the complaint was not instantly resolved by that answer, at least not in a way that made the issue disappear from discussion. So the article should stay careful here: there is a live player complaint about hostility not working, but there is not enough official confirmation in the sources reviewed to state that Blizzard has validated it as a widespread system bug.

That distinction matters because Diablo 4 forum stories can easily drift into fake certainty. What we can say is that the complaint exists on Blizzard’s own forums, that it ties directly to PvP functionality, and that it is surfacing during a season where PvP has been getting more player attention than usual. What we cannot cleanly say yet is that every affected player is definitely hitting the same confirmed bug for the same reason.

Why this could turn into a bigger story

PvP complaints do not need to affect the whole player base to become a talking point. They just need to hit the players who care about the mode most.

That is what makes this angle interesting. Diablo 4 has plenty of players who ignore PvP entirely, but the ones who do engage with the Fields of Hatred tend to care about systems like hostility much more intensely than the average player. And with streamers reportedly hosting PvP tournaments this season, as the thread claims, the inability to toggle hostile status becomes the kind of problem that can feel much bigger inside that part of the community than its raw forum size would suggest. The tournament point here is attributed to the player report, not Blizzard.

If Blizzard clarifies the intended behavior or if the issue turns out to be a simple activation misunderstanding, this may stay as a short-lived footnote. If not, it could grow into another one of those Season 12 side stories where a mode that should feel dangerous and competitive instead feels unreliable. And for PvP players, unreliable systems are usually worse than losing a fair fight.

Read More

Diablo 4 Players Say Some Season 12 Rewards Still Are Not Being Granted Correctly

 Diablo 4 Season 12 has already produced its share of bug reports, but one of the more frustrating fresh complaints is a simple one: some players say they are completing seasonal progression steps and not getting the rewards they expected.

A fresh March 21 technical support thread on Blizzard’s forums describes a player who says they completed a Seasonal quest on Rank V but did not receive the expected Paragon points. The current technical support forum listing also shows a newer March 22 topic titled “Season reward not given,” suggesting this may not be a completely isolated complaint.

That does not automatically prove a broad system-wide reward failure across all players. But it does give Diablo 4 another awkward Season 12 storyline: even when players are not arguing about balance or difficulty, some are still asking whether the reward loop itself can be trusted.

What players are reporting

The core complaint is straightforward. In the March 21 support thread, a player says they finished a seasonal objective at Rank V but did not receive the Paragon point reward they believed should have been granted. Blizzard’s technical support index for March 22 also surfaces a separate thread explicitly titled “Season reward not given,” which strengthens the case that reward delivery is becoming its own mini-theme in current Season 12 reporting.

At this stage, the evidence supports a careful framing: these are fresh player reports on Blizzard’s own forums, not a full official Blizzard confirmation that a specific reward system is universally broken. That distinction matters, especially with Diablo 4 right now, where many complaints are real as player experiences but not always fully acknowledged in a public fix note yet.

Why reward bugs hit harder than ordinary seasonal annoyances

A lot of seasonal frustration can be shrugged off if players still feel they are moving forward. Reward issues are different.

When players clear content and the game does not pay out correctly, it cuts directly into the loop that keeps a season feeling worthwhile. A challenge can be overtuned and still feel motivating. A reward that does not arrive feels more like the game is breaking its side of the bargain.

That is what makes this kind of complaint more dangerous than a minor UI error or a visual glitch. It creates hesitation. Players start wondering whether they should keep pushing seasonal tasks, whether the reward will pop late, or whether they are just burning time for nothing. That last point is an inference based on the type of complaint being reported.

This is not the same story as the Rank 6 blocker

That difference is worth underlining because Season 12 already has several progression-adjacent complaints floating around.

The Rank 6 Bloodied Lair Boss issue we covered earlier was about players saying progress was not counting correctly toward a specific Season Journey objective. This newer angle is slightly different. Here, the focus is on rewards not being granted properly after completion, including Paragon-related progression concerns. In other words, this is not just “the box didn’t check.” It is closer to “the game says the task is done, but the reward side still looks wrong.” That distinction is grounded in the separate thread titles and complaint framing visible on Blizzard’s technical support pages.

Why this could become a bigger problem fast

Reward issues have a way of spreading through community discussion faster than more technical niche bugs.

Not because every player is experiencing them, but because the fear of wasted effort is easy to understand. One person complaining about a class interaction may not matter to everyone. One person saying “I completed the seasonal thing and didn’t get my reward” immediately gets broader attention. That is especially true in a live seasonal ARPG where players are constantly measuring whether their time investment is paying off. This is an inference based on the nature of seasonal reward systems and the current forum chatter.

If Blizzard ends up confirming and fixing this quickly, it may stay as a smaller footnote in an already noisy Season 12 launch period. If not, it risks feeding into a wider player mood that the season is unreliable not just in difficulty tuning or bug frequency, but in its most basic promise: complete the content, get the reward.

The bigger issue is trust in the reward loop

That is the real reason this story matters.

Seasons live or die on momentum. Players log in, complete objectives, collect rewards, improve their character, and push further. When any part of that chain becomes uncertain, the season starts to feel less sticky. And when the uncertain part is the reward itself, that is a much bigger problem than one awkward dungeon modifier or one annoying encounter.

Right now, the safest conclusion is not that Diablo 4 has a confirmed universal Season 12 reward collapse. It is that fresh Blizzard forum reports show at least some players believe rewards are not being granted correctly, and that is exactly the kind of issue Blizzard will want to get ahead of before it becomes the next major Season 12 talking point.

Read More

Diablo 4 Players Say Season 12 Still Feels Unstable as Lag and Input Issues Keep Piling Up

Diablo 4 Season 12 has already given players plenty to argue about, but not every complaint is about balance, progression, or dungeon tuning. Some of the most persistent frustration right now is much simpler than that: the game just feels unstable.

Over the last few days, fresh player reports on Blizzard’s forums have described a messy mix of freezes, rubber banding, stuck animations, delayed attacks, pop-in, disconnects, and high latency spikes. None of that automatically proves one single root cause, and Blizzard has not publicly pinned this to one confirmed server-wide issue in the sources reviewed here. But the volume and consistency of the complaints are enough to make this feel like more than one random bad night.

What players are actually describing

One of the clearest current forum reports is titled “Extreme lag and instability season 12.” In that March 19 PC bug thread, the original poster says they are seeing freezes, stuck animations, rubber banding, enemy pop-in, queued attacks and damage, and even menus or interactables that require multiple tries to work. They add that it happens roughly every few seconds and makes the game “simply not playable in this state.” Other players in the same thread reply that they are seeing the same problem, including stutters from the menu onward and network disconnect errors despite no obvious internet issue on their side.

That wording matters, because this is not just “my FPS dipped in town.” The complaints describe a full stack of instability symptoms that affect combat, movement, interaction, and survival. In an ARPG, that turns routine gameplay into something much closer to gambling with your own character, which is probably not the kind of risk Blizzard was aiming for.

It is not just one thread

The bigger reason this story has substance is that the lag thread is not sitting in isolation.

Blizzard’s Diablo IV forum indexes from March 20–21 show multiple current technical and bug-report topics that fit the same broader instability picture, including “Lag and high ms,” “Dead to loading screen,” “Latest Patch Black Screen with GUI still showing after Teleporting,” and “Lag and crashed during pit and hordes.” The forum listings do not prove all of these issues share one cause, but they do show that performance and connection complaints are still actively surfacing across different categories and platforms during the current Season 12 window.

That is an important distinction. This article is not claiming Blizzard confirmed one giant all-purpose server meltdown. It is pointing out that players are reporting a cluster of live problems that all contribute to the same feeling: Diablo 4 does not feel reliably stable right now for everyone.

Why this kind of instability hits harder than a normal bug

Seasonal bugs can be annoying without ruining a session. Instability bugs are different.

A broken tooltip wastes your time. Rubber banding can waste your run. Delayed attacks, stuck animations, or interaction failures are not just cosmetic annoyances when they happen in Nightmare Dungeons, Pit runs, or Hordes. They directly affect whether players can react, survive, loot, or finish what they started. That becomes even more frustrating when players are not sure whether the problem is their machine, their connection, or something happening on Blizzard’s side. The forum posts reviewed here show that uncertainty very clearly.

That uncertainty is often what makes performance complaints spiral so fast. Once players start saying “my internet is fine” and “this started recently,” the conversation quickly shifts from troubleshooting to trust. Not trust in the story or the season theme, but trust that the game will behave consistently from one session to the next.

The timing makes it worse

If these reports were appearing in a quiet mid-season lull, they would still matter. Showing up during an already rough Season 12 launch period makes them land harder.

Blizzard’s latest forum activity on March 21 shows the mood around Season 12 is already tense, with high-engagement posts like “Season 12 Feedback - 1 week into the season (Pretty Bad)” and “This season is just awful” sitting alongside the active bug and support threads. That does not mean every complaint is about lag, and it definitely does not mean every player is having the same experience. But it does suggest the current performance complaints are arriving in an environment where patience is already running thin.

In other words, instability is not happening in a vacuum. It is stacking on top of a season that many players already feel is too rough around the edges.

Has Blizzard publicly confirmed a fix?

Not clearly, based on the sources reviewed here.

The current forum threads and index pages show active reports, but they do not provide a clear Blizzard post that says, in plain terms, “we have identified the source of the Season 12 lag and here is the fix timeline.” That means the safest framing is still the right one: these are current player-reported lag and instability issues, not a fully explained or officially resolved problem.

That may sound like a small wording difference, but it matters. Right now, the evidence supports “players are reporting widespread-feeling instability symptoms” much more strongly than “Blizzard has confirmed exactly what is broken.”

Why this story is worth watching

The reason this is more than filler forum drama is simple: performance complaints are one of the fastest ways to sour a live-service season.

Players can argue endlessly about class balance or dungeon tuning and still keep playing. But when the game starts to feel unreliable at the level of movement, combat response, loading, and connection stability, it chips away at the basic contract between player and game. You press the button, the thing should happen. You load the dungeon, your character should still be where the game left it. That is the bare minimum stuff, and the current forum reports suggest some players do not feel they are getting it consistently right now.

If Blizzard pushes a clear stability fix soon, this could fade into one more ugly launch-week memory. If not, it is exactly the kind of problem that can turn “Season 12 has issues” into “I do not even want to log in tonight.”

And once players hit that point, the rest of the patch notes start looking a lot less important.

Read More

Diablo 4 Co-Op Players Say Season 12 Bugs Are Making Party Play Worse Than It Should Be

Diablo 4 Season 12 has no shortage of bug complaints already, but some of the more frustrating reports are coming from players who are doing exactly what Blizzard would probably like them to do more of: playing together.

A growing chunk of the Season 12 frustration is not just about solo progression or dungeon tuning. It is about co-op and party play, with players reporting that some seasonal systems and class interactions feel unreliable once another person is on screen. The result is a specific kind of annoyance that hits harder in a multiplayer ARPG, because it does not just slow one player down. It can make the whole group feel out of sync.

The Auradin group-play complaint is getting attention

One of the clearest examples comes straight from Blizzard’s own Season 12 known bugs thread. In replies to that post, a player reports that “Auradin seems to stop working in group play when the party is on the same screen.” That does not read like a tiny edge-case visual bug. If accurate, it points to a build interaction losing effectiveness specifically in party conditions.

That matters because class and build bugs always feel worse when they are conditional. If something is broken all the time, players at least know where they stand. If it seems to break only when grouped up, it creates a messier kind of confusion. Suddenly the question is not just “is my build bad?” but “is my build only bad when I try to play with friends?”

Killstreak complaints suggest the seasonal mechanic may feel uneven in groups

The other co-op issue getting traction is tied to kill streaks in party play. A Blizzard forum thread posted on March 12 describes two players leveling together from character creation, only to find that one party member was regularly building kill streaks above 100 while the other struggled to get above 20, despite running the same content together. The poster argued that the seasonal mechanic was creating a visible disparity inside the same party.

That thread alone does not prove a confirmed system-wide bug, but it lines up with reactions inside the known-bugs discussion, where one player called the group killstreak issue a “huge bummer” and said half the reason they play is to co-op with friends. That is a useful detail because it shows this is not just a theorycrafted numbers complaint. Players are framing it as something that actively hurts the social side of the season.

Why co-op bugs tend to feel bigger than they look on paper

A lot of seasonal issues can be brushed off as temporary irritation. Co-op problems are harder to shrug away.

When party play works badly, players do not just lose efficiency. They lose momentum. One person gets progress, another does not. One build performs correctly solo, then behaves strangely in a group. One player gets the satisfying seasonal mechanic, while another feels like they are tagging along in their own session. Even if Blizzard eventually fixes the underlying problem, the immediate impression is that grouping up feels less rewarding than it should.

That is especially awkward in a live seasonal environment where the game is supposed to encourage repeated runs, experimentation, and shared grinding. If party play introduces inconsistent seasonal behavior, players are naturally going to ask whether they are better off splitting up rather than sticking together. That is not a great look for a multiplayer ARPG. This last point is an inference based on the player reports and the type of mechanics involved.

Blizzard has public reports, but not a clean public resolution yet

The most important line to hold here is the difference between player reports and officially confirmed fixes.

The Auradin complaint appears in Blizzard’s known-bugs discussion, which means Blizzard has a visible public thread where the report exists. The killstreak disparity also has its own forum thread. But based on the sources reviewed here, there is not yet a clean public post saying these exact co-op issues have been fully fixed or precisely explained. So the safest framing is that these are active player-reported Season 12 co-op issues, not fully resolved problems with a confirmed public timeline.

That distinction matters because Season 12 discourse is already crowded with complaints. The last thing worth doing is flattening all of them into “Blizzard confirmed everything is broken.” What the evidence supports is more specific: players are reporting co-op-specific problems, those reports are visible on Blizzard’s forums, and frustration around party play is clearly part of the broader Season 12 mood.

This is the kind of bug story that can grow fast

The reason this angle matters is not that every Diablo 4 player suddenly became a co-op specialist overnight. It is that multiplayer bugs tend to spread through perception quickly.

A solo player can sometimes work around a broken interaction and move on. A group of friends tends to notice immediately when the season mechanic feels unfair, inconsistent, or weaker in party play. That creates the kind of complaint that travels fast because it is easy to explain: we were playing together, and the game did not treat us the same. That is not hard for other players to understand. This is an inference based on the kinds of complaints visible in the forum threads.

If Blizzard addresses these party-play issues quickly, this probably stays as a short-lived launch-week frustration. If not, it risks becoming part of a larger Season 12 narrative where players start to feel that grouping up is more trouble than it is worth. And for Diablo, that is a much bigger problem than one bugged screen effect or one weird tooltip.

Read More

Diablo 4’s New Season 12 Patch Targets Bloodsoaked Sigils, but Players Say the Problem List Is Longer

Blizzard has now lined up another Diablo 4 Season 12 patch, and on paper it hits several of the pressure points players have been complaining about since launch week.

According to the latest official patch notes, Blizzard is significantly reducing the difficulty of Bloodsoaked Sigils, fixing an issue where Bloodied Nightmare Dungeons did not have the same Obducite drop chances as normal Nightmare Dungeons, and addressing multiple cases where Season Rank objectives or Capstone completions either failed to grant rewards or could not be completed properly.

That is the good news.

The more complicated news is that player reaction suggests the patch is being received less as a full rescue package and more as a necessary first step.

What Blizzard is actually changing

The official patch notes make three Season 12 changes stand out immediately.

First, Blizzard says it has reduced the difficulty of Bloodsoaked Sigils significantly. Second, it fixed a problem where Bloodied Nightmare Dungeons were not matching normal Nightmare Dungeons for Obducite drop chances. Third, it fixed various instances of Season Rank Objectives or Capstone Completions not working as expected.

There are also a few convenience and class-related fixes in the same patch, including quality-of-life changes around Kael Rills’ Butcher shop and some visual or gameplay fixes for specific setups. But for most Season 12 players, the real headline is obvious: Blizzard is making changes in exactly the areas that generated the most early frustration.

Why Bloodsoaked Sigils became a flashpoint

Before these notes went up, players had already been arguing that Bloodsoaked Sigils felt overtuned to the point of being more exhausting than exciting.

On Blizzard’s forums, one player described the current Bloodstained and Bloodsoaked setup as something that was simply not fun even with near-perfect gear, saying the content was making them want to quit sooner rather than play longer. That is only one thread, not a universal player vote, but it captures the tone of the backlash pretty well.

That context matters because Blizzard did not randomly choose Bloodsoaked Sigils for a nerf. The system had already become one of the clearest symbols of the “Season 12 sounded cool on paper but feels rough in practice” conversation.

Obducite was part of the problem too

The patch also directly addresses Obducite drops in Bloodied Nightmare Dungeons, which is notable because players had been complaining that the seasonal endgame economy felt uneven.

Blizzard’s notes say Bloodied Nightmare Dungeons did not have the same chance to drop Obducite as normal Nightmare Dungeons, and that issue is now being fixed.

That lines up with community complaints from the past week, including Reddit discussion where players described Obducite gain as discouraging and specifically pointed to Bloodsoaked or Bloodied dungeon runs as unrewarding compared with what the difficulty suggested. Those reactions are community reports, not official balance verdicts, but they help explain why this line in the patch notes landed as one of the biggest takeaways.

The progression fix may be just as important

One of the most important lines in the patch notes is also one of the easiest to overlook.

Blizzard says 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.

That is broad wording, but it matters because players have been actively reporting progression failures around Season Journey objectives. Blizzard’s known-bugs listing shared on Reddit also references multiple Season objective issues, including one objective that does not work correctly unless players use a workaround. Again, that Reddit thread is relaying the known-bugs list rather than creating official policy, but it shows these progression problems were not exactly invisible.

In plain English, this patch is not just shaving off difficulty spikes. It is also trying to repair the trust problem that shows up when players complete content and the season system acts like they did not.

Players are already asking the obvious question

The reaction to the patch notes has not been purely negative. In Blizzard’s forum thread discussing the notes, some players immediately highlighted the Bloodsoaked Sigil difficulty reduction and the Obducite fix as the standout improvements.

But there is also a clear undercurrent of “okay, but what about the rest?”

In that same forum discussion, players were already debating timing, scope, and whether these fixes arrive soon enough to matter. Separate forum threads from the last several days also show players still frustrated about unresolved issues and, just as importantly, Blizzard’s communication cadence around them. One player bluntly said that even a simple acknowledgment of a problem would go a long way.

That is probably the most honest read on the mood right now. The patch addresses real complaints. It just does not instantly erase the sense that Season 12 launched with too many friction points at once.

This looks like a correction patch, not a clean victory lap

The tone of this update matters almost as much as the contents.

This does not read like Blizzard confidently polishing a smooth season. It reads more like Blizzard responding to a launch window where several major systems needed adjustment quickly. The fact that one patch touches difficulty, crafting materials, and seasonal progression reliability all at once says a lot on its own.

That does not mean the patch is bad. Quite the opposite. These are sensible fixes, and in at least a few areas they appear to be directly aligned with what players were actually complaining about.

But the community reaction also makes clear that many players do not see this as the end of the conversation. They see it as Blizzard finally getting to the first pile of urgent stuff while a second pile is still sitting nearby, looking extremely Diablo.

The real test is what feels different after the patch

Patch notes can calm people down for a day. Actual gameplay improvements are what calm them down for longer.

If Bloodsoaked Sigils now feel difficult without feeling miserable, if Obducite income becomes more consistent, and if Season Rank progress starts tracking reliably again, this patch could end up being remembered as the moment Season 12 started recovering its footing.

If not, the player conversation is probably going to shift from “when is Blizzard fixing this?” to “why did Blizzard only fix part of it?”

And that is why this patch matters. Not because it solves everything, but because it is the first strong sign that Blizzard knows Season 12 needed more than a polite nudge.

Read More

Diablo 4 Players Say Season 12 Rank 6 Progress Can Fail Even After Clearing the Right Bosses

Diablo 4 Season 12 has already generated plenty of bug reports, but one newer complaint stands out because it can hit a core progression track rather than just make a build feel annoying.

Players on Blizzard’s forums are reporting that Season Journey Rank 6 is sometimes failing to update even after they complete what appears to be the correct objective: defeating Bloodied Lair Bosses in Torment III or higher. The Rank 6 objective list includes “Den of Blood,” which requires players to defeat 6 Bloodied Lair Bosses within 10 minutes in Torment III or higher.

That sounds simple on paper. In practice, some players say the game is not giving them credit.

What players are reporting

The clearest reports are showing up on Blizzard’s own Diablo IV forums. In one PC bug thread, players describe clearing the Bloodied version of the encounter, looting the correct chest, and still being unable to complete Season Rank 6. One reply specifically says they defeated a T3 Bloodied Lair Boss, looted the Doom chest, and still did not receive progression credit.

This does not appear to be limited to a single isolated post, either. Blizzard’s EU forum index also shows multiple fresh threads with titles like “Season 12 - Season Journey Capstone Rank 6 Bugged” and “Season 12 – Season Journey Capstone Rank 6 not progressing,” suggesting the issue is being reported by more than one player across regions.

There is also similar chatter on Reddit, where one player said they had defeated Bloodied Lair Bosses and Greater Bloodied Lair Bosses on T4, but their Season Journey tabs still were not completing. In that same thread, another player said it worked for them, while a different reply suggested a specific boss might be bugged rather than the entire objective chain. That does not prove the cause, but it does suggest the issue may be inconsistent rather than universal.

Why this one matters more than a minor bug

Not every seasonal bug hits the same way.

A visual glitch is annoying. A balance hiccup is frustrating. But a Season Journey issue feels worse because it messes with the game’s reward structure and the sense of progression that keeps a season moving. When players complete the content and the UI still refuses to acknowledge it, that lands differently.

It is also the kind of bug that creates confusion fast. Some players may think they ran the wrong version of the boss, misunderstood the requirement, or missed some hidden condition. Others may have done everything correctly and still got nothing. The result is the same: uncertainty, wasted time, and a lot of second-guessing. That is never a great combo in a live seasonal system.

Is Blizzard officially calling it a known bug?

At the moment, the safest read is no confirmed public fix yet based on the sources reviewed here.

Players are clearly reporting the issue on official forums, but that is not the same thing as Blizzard formally confirming the exact bug or publishing a fix timeline. So this should be framed as an active player-reported progression issue, not as a fully confirmed Blizzard-side defect with an official ETA.

That distinction matters, especially with Diablo 4 stories right now. A lot of Season 12 complaints are real in the sense that players are posting about them, but not every complaint has been acknowledged in patch notes or blue posts yet.

Could it be tied to specific bosses or party conditions?

Possibly, but that is still speculative.

Forum and Reddit reports hint that the problem may not affect every player or every run the same way. One Reddit reply claimed a different Bloodied boss gave them credit after earlier attempts failed, while forum listings also show a separate fresh topic asking whether Greater Bloodied Lair Boss completion in Torment IV is not working while in a party. That suggests there may be edge cases or encounter-specific conditions involved, but there is not enough official confirmation yet to state that as fact.

In other words: players are connecting dots, but Blizzard has not publicly drawn the map for them.

What players should take from this for now

If you are working through Season Journey Rank 6, this is one of those moments where blindly assuming the system will track everything correctly may be optimistic in the most Diablo way possible.

The reports so far suggest a few practical takeaways:

• Make sure you are doing the Bloodied version of the Lair Boss objective, not a normal one.
• Pay attention to whether the run awards progress immediately.
• If it does not count, document the boss, difficulty, and whether you were solo or grouped.
• Check the Blizzard bug forums before burning too much time repeating the same route over and over.

That is not a fix, obviously. But until Blizzard confirms the cause or pushes a patch, it is probably the most sensible way to avoid turning one seasonal objective into a full evening of confusion.

A small bug with big seasonal consequences

What makes this story worth watching is not just the bug itself. It is what it represents.

Season 12 already has players keeping a closer eye on progression reliability, and when a Season Journey rank stops updating properly, that immediately becomes more than just another forum complaint. It becomes a trust issue between the player and the season’s reward loop.

If Blizzard addresses it quickly, this may end up as a short-lived headache. If not, expect more players to start running into the same wall and asking the same question: if the objective is done, why is the game still acting like it is not?

Read More