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 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