Diablo 4 Players Say Spawn of the Damned Is Still One-Shotting Hardcore Characters

There are many respectable ways for a Hardcore Diablo 4 character to die.

A boss you underestimated.

A terrible pull.

That moment when confidence becomes stupidity approximately three seconds before the death screen appears.

Being instantly killed beside a Helltide Hellworm by something you never saw is considerably harder to accept.

But that is exactly what Diablo 4 players have been reporting for months.

A long-running bug report about Spawn of the Damned has resurfaced again this week, with another player reporting an apparently instantaneous death near a Hellworm despite having thousands of Life and Fortify.

Blizzard has not officially confirmed that Spawn of the Damned is bugged, so this remains a player-reported issue rather than an established game bug.

For Hardcore players, however, that distinction offers limited comfort when the character is already dead.

The Reports Started Back in May

The original report appeared on Blizzard's Diablo IV forums on May 2.

The player described repeatedly being killed during Helltides by something identified in the death message as Spawn of the Damned.

According to the report, their health remained above 90% before suddenly dropping to zero, without an obvious attack, ground effect or visible Spawn of the Damned appearing first.

Another player responded that the same thing had happened while approaching a Hellworm.

Then came another.

A tanky Druid with full Life, Fortify, Barrier and Damage Reduction reportedly died instantly near a worm.

Then a Warlock player reported a similar death while fully buffed.

By this point, a pattern was beginning to emerge.

Not proof.

But certainly enough to make Hardcore players look at Helltide worms with rather more suspicion than usual.

The Reports Never Completely Stopped

The thread continued receiving reports through May and into July.

On July 3, another Hardcore player said Spawn of the Damned had killed them instantly beside a Hellworm.

Four days later, a Necromancer player reported dying twice despite entering the encounters with full Life, Fortify and Barrier.

And now the issue has surfaced again.

In a new post added on August 14, a player reported losing a level 61 character on Hard difficulty after encountering a Hellworm during Helltide.

The character reportedly had more than 4,500 Life and partial Fortify.

The player ran away from the worm, stopped to open a chest and was then killed by Spawn of the Damned before the other nearby monsters had even reached them.

That death reportedly occurred on August 12.

What Exactly Is Killing Them?

That remains the problem.

The reports consistently associate the deaths with Spawn of the Damned and Hellworms, but players do not appear to agree on the exact mechanic responsible.

Some suspect the enemy may be spawning directly on top of the character.

Others wonder whether there is a spawn or death effect dealing damage before its visual warning becomes visible.

It is also possible that the creature simply has unexpectedly high damage under certain circumstances.

Until Blizzard investigates or explains what is happening, those possibilities remain speculation.

What makes the issue unusual is not simply that players are dying.

Diablo is quite committed to that part of the experience.

It is that several players describe being unable to see or react to whatever dealt the lethal damage.

Softcore Players Have Reported It Too

This is not exclusively a Hardcore complaint.

Players in the same thread have reported similar one-shot deaths on Softcore characters.

The difference is obvious.

On Softcore, an unexplained death costs some time and perhaps a few choice words directed toward the monitor.

On Hardcore, it costs the character.

That makes any potentially invisible or unavoidable burst of damage much more serious.

Hardcore Players May Want to Treat Hellworms Carefully

Without an official confirmation, we cannot tell players that every Hellworm is carrying a secret delete-character button.

Most Helltide encounters clearly do not end this way.

But the reports now span more than three months and multiple classes, and several explicitly involve Hardcore characters dying beside Hellworms with defensive layers active.

If you are playing Hardcore, there is therefore a reasonable argument for giving Hellworms some extra space until the situation becomes clearer.

Not because Spawn of the Damned has been officially confirmed as broken.

It has not.

But Hardcore has always rewarded unnecessary paranoia.

Sometimes the chest really can wait.

Blizzard Has Yet to Explain It

The most frustrating part is that the original bug report is now months old.

At the time of writing, the thread contains no official Blizzard response confirming the cause or stating that a fix is underway.

That does not necessarily mean Blizzard is ignoring it. Bug reports can be investigated without public replies.

But from the player's perspective, the uncertainty remains.

Maybe Spawn of the Damned has an overtuned attack.

Maybe something around the Hellworm is firing before its visuals appear.

Maybe there is another explanation entirely.

Until Blizzard tells us, we simply do not know.

What we do know is that Diablo 4 players are still reporting the same frightening sequence:

Full health.

Hellworm nearby.

Sudden death.

Slain by Spawn of the Damned.

For Softcore, that is annoying.

For Hardcore, that is the sort of sentence capable of ending an evening.

Source

Diablo IV Forums: One Shot Bug — Spawn of the Damned on HC

Read More

Diablo 4 Barbarians Can Apparently Kill Players Outside PvP Zones

Diablo 4 may currently contain a new form of open-world PvP.

Nobody opted into it.

Players are reporting that Barbarians can be killed by other players outside designated PvP zones, including Helltides and World Boss areas.

The current evidence points toward a bizarre interaction involving Rallying Cry, Fortify, Wyrdskin and another player using Thorns.

In some reported cases, activating the shout causes the Barbarian to die instantly.

Sanctuary has apparently decided that friendly buffs needed friendly fire.

Players Are Dying Outside PvP Zones

The original bug report describes a player being killed repeatedly while waiting in a World Boss area.

The attacking player did not appear to be using a visible skill, leaving the victim unsure whether the deaths were caused by a bug, cheating or some hidden interaction.

Other players quickly reported similar deaths outside PvP zones.

Several said the problem appeared when Barbarians or Paladins were nearby.

Others described being killed repeatedly during Helltides, sometimes by the same player standing close to a chest or event.

These are locations where players should normally be cooperating.

The demons are supposed to be the hostile part of the encounter.

Rallying Cry Appears To Trigger The Damage

Early reports initially blamed Challenging Shout.

Further testing by affected players pointed instead toward Rallying Cry.

One player tested the interaction with a friend and reported being killed immediately after activating Rallying Cry.

The fatal version appeared to require the Fortify-related Rallying Cry upgrade.

When the player removed that upgrade, the deaths reportedly stopped.

That suggests the skill may briefly interact with another player as though the two characters were hostile.

Nothing in Rallying Cry’s intended purpose suggests it should perform an informal execution of the caster.

The Other Player Needs Thorns

The second part of the reported interaction involves Thorns.

Affected Barbarians say the nearby player who caused the death was using Thorns equipment or a Thorns-focused build.

The theory is that Rallying Cry’s Fortify effect somehow touches or modifies the nearby player.

The game then treats that interaction as hostile damage.

Thorns responds by reflecting damage back to the Barbarian.

At high endgame values, that reflected damage may be large enough to kill the caster instantly.

The Barbarian shouts encouragement.

The Paladin’s armour interprets this as an assassination attempt.

The Barbarian dies.

Teamwork has had better patches.

Wyrdskin May Be The Missing Link

Players conducting further tests identified Wyrdskin as another likely requirement.

Wyrdskin can appear as a Unique Charm and provides a substantial part of certain Barbarian setups.

According to affected players, removing Wyrdskin stopped the unwanted deaths.

That does not prove the Charm is solely responsible.

The bug appears to depend on several systems interacting at once.

Current reports suggest the dangerous combination may include:

• A Barbarian using Rallying Cry
• The Fortify-related Rallying Cry upgrade
• Wyrdskin equipped
• A nearby player with significant Thorns

Not every player using these components has publicly reported the problem.

Blizzard has not confirmed the exact reproduction steps.

Still, the pattern across the current reports is consistent enough that Barbarians using Wyrdskin should pay attention.

Automated Shouts Make The Bug Worse

Some builds trigger shouts automatically through Runes or other effects.

That can make the bug significantly more dangerous.

A player manually casting Rallying Cry may notice the connection after one or two deaths.

A build that fires the skill automatically can kill itself whenever the wrong player walks into range.

One report describes a Barbarian being wiped four times in a Helltide after recently changing to a setup that triggered the shout through a Rune.

Another player said they could not safely stand near Paladins because their automated shouts caused immediate deaths.

That turns ordinary public events into social distancing exercises.

See another heavily armoured character?

Back away slowly before your own build attacks you.

Some Players Suspect Deliberate Exploitation

At least one player suspects that others may already be using the interaction deliberately.

They described returning to the same Helltide chest after an unexplained death and being killed again while the same nearby player remained in the area.

That does not prove intentional exploitation.

The other player may not have understood what was happening.

Thorns builds can deal reflected damage passively, and the person wearing the equipment may receive little indication that another player has triggered it.

Still, repeated deaths around the same individual naturally raise suspicion.

If the interaction can be reproduced reliably, it gives hostile players a way to kill others in zones where PvP should be disabled.

That is no longer merely an annoying build bug.

It becomes a potential griefing tool.

Helltide Deaths Carry A Real Cost

Dying in a normal open-world area is irritating.

Dying in a Helltide can cost resources.

Players may lose Aberrant Cinders or other activity progress depending on the current seasonal rules and event state.

Several affected players specifically mention losing Helltide currency after being killed by the interaction.

That makes the bug financially useful to nobody except whichever Blacksmith is handling the repair bill.

The victim is not losing a fair PvP fight.

They are pressing a defensive support skill and being deleted by someone who may not even realise they participated.

World Boss Areas Are Also Affected

The first report happened while players were waiting for a World Boss.

That is especially strange because World Boss zones gather many characters into one small area.

Barbarians use shouts to prepare themselves and nearby allies.

Thorns characters stand among them.

The conditions needed for the reported bug may therefore occur naturally without anyone attempting to reproduce it.

A crowded World Boss spawn becomes a perfect laboratory.

Twenty players arrive to fight one giant demon.

The Barbarians begin killing themselves before the boss appears.

The demon receives credit for excellent time management.

The Current Workarounds Hurt The Build

Players have identified several possible ways to avoid the interaction.

The most commonly reported workaround is removing Wyrdskin.

Another is dropping the Fortify upgrade from Rallying Cry.

Players using automated shouts may also disable the Rune or effect responsible for triggering the skill.

Those solutions can prevent deaths.

They also weaken the build.

Rallying Cry provides movement speed and resource generation, while its upgrades can contribute valuable Fortify.

Wyrdskin may be central to the character’s Charm setup and damage output.

The player is therefore asked to choose between using the intended build and safely standing near other people.

That is not build diversity.

That is a restraining order disguised as balance.

Players Should Test The Setup Carefully

Barbarians using Rallying Cry and Wyrdskin should watch for sudden unexplained deaths around other players.

If the character dies immediately after Rallying Cry activates, note whether a Thorns Barbarian or Paladin was standing nearby.

Players can temporarily remove Wyrdskin or the Fortify upgrade to see whether the issue stops.

Testing should be done carefully.

Do not repeatedly reproduce the interaction around unsuspecting players or use it to interfere with public events.

Anyone able to reproduce the bug should submit details to Blizzard, including:

• The exact Rallying Cry upgrade used
• Whether Wyrdskin was equipped
• How the shout was triggered
• The nearby player’s class and Thorns value
• The activity and location
• A video or combat log if available

The more precise the reproduction data becomes, the faster Blizzard can isolate the interaction.

This Is Not Confirmed As A Cheat

Players should avoid automatically accusing nearby Thorns characters of cheating.

The current reports indicate that the damage may happen passively.

A Paladin or Barbarian wearing Thorns equipment may not be pressing any skill or deliberately targeting anyone.

The victim’s Rallying Cry appears to trigger the interaction.

That means both players may be surprised by the result.

Repeatedly remaining near affected players after discovering the bug would be different.

But until intention is clear, this should be treated primarily as a technical problem rather than proof that every nearby Thorns player is an open-world murderer.

Sometimes the armour is guilty.

Blizzard Has Not Publicly Confirmed A Fix

At the time of writing, Blizzard has not publicly confirmed the reported outside-PvP deaths.

The current Diablo IV patch notes contain several fixes involving Rallying Cry, Barbarian skills, Wyrdskin visuals and other player-effect bugs.

They do not list a fix for Rallying Cry causing Thorns damage between players outside PvP zones.

That means the issue may still be active.

It also means the community’s proposed reproduction steps remain unofficial.

The cause could involve Wyrdskin, Fortify, Rallying Cry, Thorns or another hidden effect attached to one of those systems.

Only Blizzard can confirm the exact technical chain.

Diablo 4 Has Had Other Friendly-Fire Bugs

The current patch notes show that unintended interactions between allies are not unprecedented.

Blizzard has previously fixed effects that slowed allies, froze allied players or applied skill effects to NPCs and vendors.

Complex builds create enormous numbers of interactions between buffs, debuffs, reflected damage and shared public spaces.

One incorrect hostility flag can turn a support ability into an attack.

That appears to be the basic shape of the current problem.

Rallying Cry affects nearby players.

Wyrdskin or Fortify may cause part of that effect to be treated incorrectly.

Thorns then responds exactly as designed to damage that was never supposed to exist.

The final result is technically complicated and visually simple.

The Barbarian falls over.

Outside-PvP Damage Needs An Emergency Fix

This issue deserves faster attention than an ordinary damage-calculation bug.

It affects shared public areas.

It can cause resource loss.

It may disrupt World Bosses and Helltides.

Most importantly, it appears capable of enabling unwanted player kills outside the zones specifically designed for PvP.

Blizzard could temporarily disable the problematic interaction while investigating the full cause.

If Wyrdskin is responsible, its interaction with Rallying Cry could be suspended.

If the Fortify upgrade is incorrectly flagging damage, that portion could be disabled around other players.

A temporary reduction in build power would still be frustrating.

It would be better than allowing random executions during cooperative events.

Cooperative Skills Should Not Start PvP

Rallying Cry is supposed to help the Barbarian and nearby allies.

It increases mobility, supports resource generation and can provide Fortify.

The entire identity of the skill is cooperative.

That makes the reported bug especially absurd.

A Barbarian presses a group buff.

A nearby player’s Thorns reacts.

The Barbarian dies outside a PvP zone.

Diablo 4 already contains dedicated Fields of Hatred for players who want to murder each other.

The rest of Sanctuary should remain focused on murdering demons.

For more coverage of current bugs, builds and seasonal problems, visit our Diablo 4 archive.

Until Blizzard fixes the interaction, Barbarians using Wyrdskin and Rallying Cry should be careful around Thorns characters.

The Paladin standing beside you may be perfectly friendly.

His armour apparently has other plans.

Sources

• Diablo IV Forums: Players report being killed outside PvP zones
• Diablo IV Forums: Additional discussion of Wyrdskin and Rallying Cry
• Blizzard: Official Diablo IV patch notes

```

Read More

Diablo 4’s War Plans Helltide Change Quietly Removes a Dumb Chore

Diablo 4 Patch 3.1.0 has plenty of big, loud changes fighting for attention.

Mephisto’s mid-fight cutscene can finally be skipped. Unique items can be enchanted. Chromatic Tuning Prisms got nerfed. Ruptures got tuned. Echoing Hatred now has a wave cap, because even hatred apparently needs a ceiling.

But one of the best changes may be hiding in the War Plans section.

Helltide War Plan objectives no longer require players to open a set number of chests. Instead, they now require a flat Cinder spend amount.

That sounds tiny.

It is not.

That is the kind of small friction fix that makes Diablo 4 feel less like it was designed by a demon with a clipboard.

Opening Chests Was Always the Awkward Part

Helltides already have a natural rhythm.

Kill monsters. Collect Cinders. Chase events. Dodge nonsense. Try not to die with a pocket full of currency like an overconfident loot gremlin. Then spend those Cinders before the whole thing resets and Sanctuary laughs at you.

That loop works because it is simple.

The problem with “open X chests” objectives is that they can push players into awkward behavior. Instead of spending naturally, players start hunting specific chest counts. They may avoid better options, split spending weirdly, or make choices based on checklist efficiency rather than what actually feels good in the moment.

That is not difficulty.

That is chore design wearing horns.

A Flat Cinder Spend Just Makes More Sense

Changing the objective to a flat Cinder spend amount is cleaner.

Players are already earning Cinders. Players are already spending Cinders. The objective now tracks what the activity is actually about, rather than forcing everyone into a specific chest-opening ritual.

That is better design.

It lets players engage with Helltide more naturally. Want to save for a bigger chest? Fine. Want to spend across several smaller options? Also fine. Want to just play the event, gather Cinders, and stop feeling like your War Plan was written by an accountant trapped in Hell?

Beautiful.

Sometimes the best patch notes are not the ones that add more systems.

Sometimes they just remove the stupid little bump everyone kept tripping over.

War Plans Needed Less Paperwork

War Plans are an interesting idea, but they walk a dangerous line.

At their best, they give players direction, structure, and extra reward hooks. At their worst, they can feel like seasonal homework taped onto activities players were already doing.

That is why this Helltide change matters.

Diablo 4 already has enough checklists. Seasonal objectives, dungeon goals, boss mats, crafting materials, reward tracks, glyph upgrades, War Plans, Whispers, Helltides, Ruptures, Deathtoll Chambers, Superior Lair Keys, and whatever else Sanctuary has hidden behind another skull-shaped menu.

The game does not need objectives that make familiar activities feel more awkward.

It needs objectives that reward players for playing well, playing efficiently, and actually staying in the flow.

A flat Cinder spend does that better than a chest count.

The Reward Buffs Help Too

Patch 3.1.0 also increases War Plan experience rewards in Torment 8 and above, boosts Infernal Hordes rewards, and adds more War Plan options for Helltide and Nightmare Escalations.

That is important because War Plans cannot just be cleaner.

They also need to be worth caring about.

If players are going to route activities around War Plans, the rewards have to justify the extra attention. Otherwise, the system becomes another little menu that players check because they feel they should, not because they actually want to.

Better rewards and less annoying objectives are a good combination.

Not glamorous. Not trailer material. But useful.

Shared Party Boards Are Another Step in the Right Direction

Blizzard also says parties can now generate fully shared War Plans boards with synchronized progression and objectives.

That should make group play less clumsy.

Before, War Plans could create the kind of party awkwardness where everyone technically wanted to play together, but their objectives were quietly pulling them in different directions like cursed shopping lists.

Shared boards help fix that.

If a group is farming Helltides, Nightmare Escalations, Infernal Hordes, or other War Plan activities together, their progress should not feel like four separate demons arguing over the itinerary.

One board. Shared progress. Less nonsense.

Again, not flashy.

But very welcome.

Small Fixes Make the Grind Less Cursed

The Helltide Cinder change is not going to define Season 14 by itself.

Players will spend more time talking about Mythic Uniques, Pandemonium Ruptures, Corrupted Reaper farming, Solo Self Found leaderboards, Tower rewards, and whether the season’s loot loop actually holds up after the first week.

Fair enough.

But Diablo 4 lives in the small details too.

A slightly better objective. A cleaner reward path. A smoother party system. One less reason to sigh while looking at a checklist.

Those things matter because players repeat this content constantly.

One annoying objective is tolerable once.

After twenty runs, it becomes a personal enemy.

So yes, changing Helltide War Plans from chest counts to flat Cinder spending is a small patch note.

It is also a smart one.

Hell can keep the demons.

It does not need the dumb chores.

Source: Blizzard’s Diablo IV Patch Notes.

Read More

Diablo 4 Players Say Town Portal Gets Cancelled By Every Angry Fly In Sanctuary

Diablo 4 players are used to danger.

Demons. Explosions. Poison puddles. Lightning storms. Bosses with the social manners of a burning dumpster.

Fine. That is Sanctuary.

But some players are now complaining about something much smaller and much dumber:

Trying to teleport out, only for the tiniest hit in the world to cancel the whole thing.

A new Diablo 4 forum thread argues that town portal cancels too easily, especially in dense areas where small enemies, stray projectiles, or random spawns can interrupt the cast before the player escapes.

In other words, the Wanderer can face Hell itself.

But one angry mosquito with a dagger can stop fast travel.

Teleport Should Not Feel Like A Boss Mechanic

The basic complaint is simple: teleporting to town is supposed to be a utility action.

It is not supposed to feel like channeling an ancient ritual while every skeleton in a ten-mile radius suddenly develops abandonment issues.

Players use town portal when their bags are full, when they need to salvage, when they want to repair, when they need to step away, or when the game has once again filled their inventory with seventeen bad boots and a sword that looks promising until it personally insults their build.

If the teleport gets cancelled by every tiny hit, that convenience turns into friction.

And Diablo 4 already has enough friction hiding in its systems like goblins in office chairs.

Helltides Make The Problem Worse

The issue becomes more annoying in content where monsters keep spawning or where the player is surrounded by small hazards.

Helltides are a perfect example.

You finish a fight. You try to leave. Something respawns. Something sneezes on you. Something off-screen throws a tiny fireball with the emotional weight of a tax letter.

Portal cancelled.

Try again.

Cancelled.

Try again.

Congratulations, you are now playing Diablo 4: Airport Security Edition.

There Is A Difference Between Danger And Annoyance

To be fair, teleporting should not be completely free in every situation.

If a player is actively being murdered by a boss, surrounded by elite enemies, or standing in the middle of obvious danger, interrupting the portal makes sense.

That is not the problem.

The problem is when tiny incidental damage cancels the cast so often that the system feels fussy rather than dangerous.

Meaningful danger asks players to make smart decisions.

Annoying danger asks players to stand in a corner and hope the nearest skeleton respects their travel plans.

Diablo 4 Needs Fewer Tiny Flow Breakers

This complaint fits into a much larger Diablo 4 pattern.

Players are not only asking for bigger features. They are asking for smoother flow.

Inventory salvage. Better stash handling. Clearer visual effects. Less town-trip friction. Fewer little interruptions that chip away at the fun between actual combat moments.

The best version of Diablo 4 is simple at the core:

Kill monsters. Get loot. Make choices. Keep moving.

Every time the game interrupts that rhythm for something trivial, the dungeon loses momentum.

And momentum is everything in an ARPG.

A Short Grace Window Could Help

There are obvious ways Blizzard could soften the pain without letting players abuse town portal as a panic button.

For example, small damage could be ignored after combat ends. Or portal interruption could depend on damage amount, enemy type, or whether the player has recently taken meaningful combat damage.

Another option would be a short grace period once nearby enemies are cleared, so players are not punished by a random late spawn or a tiny projectile that arrives like a bureaucrat from Hell.

The exact solution is less important than the principle:

Town portal should not feel fragile for the wrong reasons.

Let The Wanderer Leave Without A Formal Hearing

This is not the biggest Diablo 4 issue in the world.

It is not class balance. It is not Mythic Uniques. It is not Season 14’s grand identity crisis. It will not decide the future of Sanctuary.

But it is exactly the kind of small quality-of-life problem that makes players tired.

When teleporting to town feels unreliable, everything around it gets more irritating. Full inventory. Salvage trips. Helltide pacing. Dungeon resets. Real-life interruptions. All of it becomes slightly worse.

Hell should be dangerous.

Leaving Hell for two minutes to empty your backpack should not require negotiating with every angry fly in Sanctuary.

For more Diablo 4 coverage, check our latest posts on Diablo 4 and Lord of Hatred.

Read More

Diablo 4 Players Say War Plan Upgrades Still Aren’t Working Right

 

Diablo 4: Lord of Hatred has already had a hotfix aimed at making War Plans feel less miserable in parties, but the system may not be done causing headaches yet. Because apparently Sanctuary’s newest endgame paperwork has layers.

A fresh Diablo IV forum thread has players questioning whether some War Plan upgrades are actually working as advertised. The main complaint focuses on a Tier 3 Infernal Hordes upgrade that says players should get a challenge at the start of an Infernal Horde, with +200 Aether awarded if that challenge is completed.

The challenge allegedly never appeared

The player says no challenge appeared, no notification showed up, and no +200 Aether was awarded. They also say they earned plenty of Aether during the run, so if a challenge had quietly existed in the background, it should probably have been completed naturally.

That is exactly the kind of vague system behavior that makes players suspicious. If an upgrade is supposed to trigger a challenge, players need to see the challenge. Diablo 4 already has enough invisible math running under the floorboards. Reward mechanics do not need to join the witness protection program.

The 50 million gold refund cost makes it worse

The sharper complaint is not just that the node may be bugged. It is that refunding War Plan nodes reportedly costs 50 million gold. That turns a possible broken upgrade from “annoying” into “why am I paying a dungeon mortgage to fix this?”

War Plans are supposed to give players meaningful choices. But if a node does not work, and changing away from it is expensive, the system starts feeling less like strategy and more like being fined for trusting the tooltip.

Helltide nodes are getting questioned too

The same thread also raises concern about a Helltide node that says ambushes can spawn up to four additional Hellborne. The player says they only saw one Hellborne and expected more from the upgrade.

Replies push back on the wording, pointing out that “up to” can technically mean fewer than four. That may be true, but it also highlights the bigger issue: War Plan language needs to feel clear, especially when players are investing time, gold, and seasonal progression into it. “Technically correct” is not always the same thing as satisfying.

War Plans need clarity as much as fixes

Diabloz recently covered how Hotfix 3 fixed War Plans party rewards, including helper caches and meta progression XP. That was a good step. But this newer discussion suggests the system still has rough edges, whether through actual bugs, unclear language, or rewards that do not feel reliable.

For now, this is a player-report debate, not an official Blizzard-confirmed known issue. Still, War Plans are one of Lord of Hatred’s big new seasonal systems. If players cannot tell whether upgrades are broken or just badly explained, that is a problem by itself.

Endgame planning should feel like strategy. It should not feel like arguing with a tooltip while 50 million gold watches from the corner.

Read More

Diablo 4 Players Say Blood Maiden Is Not Giving Grim Favors

Diablo 4’s Season 12 bug pile is still growing, and the latest complaint hits a system players touch constantly during Helltide farming. A new PC bug report posted on March 30 says killing the Blood Maiden is not awarding Grim Favors at all, even after multiple kills across two different characters. The report is short, but the problem it describes is not. If a Helltide boss stops feeding Whisper progress, one of Diablo 4’s most routine reward loops starts breaking down.

What is happening

According to the report, the player killed Blood Maiden four times total — twice on one character and twice on another — and still got no Grim Favors. One character was already sitting at 9 Grim Favors, while the other had none, which makes the complaint a little more useful than a vague “something felt off” post. The report also says it happened on version 2.6.1.71172. As of March 31, the thread was still visible in the live PC bug-report index, which means it is part of the current Season 12 complaint flow and not some buried old post dragged back up later.

Why it matters

This one matters because Grim Favors are not side fluff. They are tied directly to Tree of Whispers progression and the broader reward loop that keeps Helltide and related activities feeling worth the time. Blizzard has previously treated Grim Favor pacing and Helltide reward structure as important enough to tune in patches and PTR notes, including changes meant to make it easier to earn 10 Grim Favors within a Helltide window. If Blood Maiden kills are now failing to grant that progress, the issue lands right in the middle of a system Blizzard has already spent time refining.

There is also some history here. Blizzard has fixed Blood Maiden-related Helltide issues before, including a past bug where defeating the Blood Maiden after a Helltide ended would not progress an associated quest objective. That does not prove this is the same bug returning, but it does show Blood Maiden progression problems are not entirely new territory for the game.

Current status / what Blizzard said

So far, Blizzard’s public Season 12 List of Known Bugs does not appear to mention Blood Maiden failing to grant Grim Favors. The official list covers issues like Slaughterhouse problems, missing NPC text, Paladin bugs, and Bloodsoaked aspect roll problems, but not this specific Helltide/Whisper complaint. That means there is no public workaround or official acknowledgment for it in the main roundup yet.

When routine farming stops paying out

A missing spark is dramatic. A broken boss fight is obvious. But a farm target quietly failing to give Grim Favors may be worse in a different way: players can lose progress without realizing the loop is broken until they have already wasted the run.

Read More