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.
