Diablo 4 Duriel Death Bug Has Players Baffled

 

Diablo 4 has another fresh bug report on the board, and this one hits a boss fight that is supposed to feel brutal, not paranormal. A new Diablo IV PC bug report says the player is dying instantly during the Duriel fight with nothing visibly hitting them, nothing appearing under them, and no obvious attack crossing the room. That already sounds miserable. The extra kick in the teeth is that the player says it is reliably reproducible, which moves this out of random bad-luck territory and into proper bug-watch territory.

What the report actually says

The details are specific enough to be worth taking seriously. The player says they were trying to finish the last part of the Season Journey, fighting Duriel in a group of two, with both players using the same Hydra Sorcerer build and the same gear. Yet only one of them kept getting instantly deleted “to nothing,” including after being resurrected. The same report also says the player has noticed hitbox issues elsewhere this season, but believes this Duriel problem is worse because they were clearly not standing in anything visible when the deaths happened.

Duriel has had visibility problems before

That does not prove this is a long-running Duriel bug with the exact same cause, but it does add context. Back in June 2023, players were already filing official forum complaints about the Duriel fight saying the camera could get blocked by arena geometry and that bad hitboxes around ground hazards made the encounter harder to read than it should have been. So while today’s report is not the same bug, it fits an old Diablo 4 pattern: when players cannot clearly see what killed them, the fight stops feeling deadly and starts feeling dirty.

This is exactly the kind of death that makes players stop trusting the game

That is the real issue here. Diablo players will tolerate hard bosses. They will even tolerate getting flattened when they know why it happened. What they do not tolerate for long is a death that looks like the game forgot to show its work. We have seen that frustration before in broader Diablo 4 complaints, including a January 2025 “Unknown Killer” thread where Hardcore players reported sudden one-shots with no clear source. That does not mean Duriel is caused by the same thing, but it does show how quickly invisible or unreadable deaths poison confidence in the game.

For now, this one stays in bug-watch territory

At the time of writing, the April 22 Duriel thread is live in Blizzard’s PC Bug Report section and does not show a visible Blizzard reply yet. So no, this is not proof that Duriel is broadly broken for everyone. But it is a very usable warning sign, especially in a season where Diabloz has already covered issues like quest steps soft-locking progression and world boss rewards going missing. Sanctuary is at its best when it feels cruel on purpose. “You died to absolutely nothing” is a different flavor, and it is a lot less charming.

Read More

Diablo Immortal Players Say Battlegrounds Were Super Laggy

 

Diablo Immortal players are complaining about another rough night in Battlegrounds, and this one sounds less like normal PvP salt and more like the servers briefly forgetting what a fight is. A fresh bug report says Battlegrounds were “super laggy” on April 19, with heavy stuttering, delayed reactions, and moments where attacks appeared to land while everyone’s health bars stayed full for five to ten seconds. That is not just annoying. That is the kind of lag that makes a match feel fake.

The report comes from a fresh thread on the official Diablo Immortal bug report forum, where a PC player says all six Battleground matches they played that night were unusually laggy. In a follow-up post, the same player says there were moments where six or seven players were visibly dashing around and attacking, but nobody’s HP moved for several seconds. According to that report, the desync was bad enough that idol progress kept moving in situations where players probably should have died much earlier.

That is not ordinary Battleground frustration

Anyone who has spent time around Diablo Immortal PvP knows players can blame lag for just about anything, usually five seconds after getting deleted by a whale. But this report has a more specific smell to it. It is not just “I lost and therefore the servers are cursed.” It is “the combat state looked visibly wrong, attacks seemed to connect, and the match logic stopped lining up with what was on screen.” That is a much uglier category of complaint.

And it matters because Battlegrounds already live on a fragile little edge where fairness is debated constantly. The second server behavior starts looking unreliable on top of the usual class balance and matchmaking arguments, the mode goes from frustrating to clownish very quickly. If players cannot trust whether hits are registering in real time, then the whole PvP experience starts feeling like an expensive argument being held underwater.

The timing is bad because Blizzard just tried to refresh Battlegrounds

This also lands awkwardly because we recently covered how Blizzard rolled out a much bigger Battlegrounds refresh to calm some of the long-running PvP complaints. That update was supposed to make the mode feel more stable, more readable, and less miserable. A fresh “Battlegrounds are super laggy tonight” report does not automatically mean the refresh failed. But it absolutely undercuts the mood around it.

It also fits a broader recent pattern where Diablo Immortal keeps stumbling into stories about systems not behaving the way players expect. We have already covered how players said 10 Legendary Crests vanished with no refund mail and how a legendary gem reportedly disappeared after a Rift. Different systems, same broad issue: the game keeps producing moments where trust takes a hit.

Fresh report, small thread, ugly symptom

To be fair, this is still one fresh public report with limited follow-up, not proof that every Battleground in every region turned into slideshow PvP overnight. Nobody should oversell it. But the symptom is bad enough to matter. When players describe a fight where attacks are flying, movement is happening, and health bars simply refuse to update for several seconds, that is not normal latency grumbling. That is the kind of thing that makes a competitive mode look broken in the most visible possible way.

At this point, Diablo Immortal does not just need Battlegrounds to be balanced. It needs them to feel like the server and the screen are participating in the same match.

Read More