Diablo 4 Players Say Some Monsters Are Literally Not Killable

 

Diablo 4 has had its share of annoying bugs lately, but this one cuts right past irritation and into full gameplay paralysis. A fresh player report on Blizzard’s PC bug board used the bluntest possible headline: “I cannot commence because Monsters are actually not killable.” That is not a balance complaint. That is not a loot gripe. That is the game allegedly putting enemies on the field and then forgetting to let players finish the job.

The original thread on the official Diablo IV PC bug report forum was posted on April 19, 2026, but it was also quickly marked as deleted by author. That means the public evidence is thin, and nobody should pretend Blizzard has confirmed a broad new unkillable-monster plague. But the topic title is still visible in Blizzard’s latest PC bug listings, which is enough to make it a live story worth watching rather than some made-up ghost report.

Even one report like this gets attention fast

There is a reason a thread title like that hits harder than a lot of other bug posts. Diablo can survive ugly UI. It can survive busted wardrobe menus. It can even survive the occasional loot container deciding to become decorative. Combat is different. The second players start feeling like enemies cannot be killed properly, everything else in the game becomes secondary because the basic contract stops working.

That is also why this story still has value even with the deleted thread caveat. The public details are limited, yes. But “monsters are actually not killable” is not some fuzzy theorycrafting argument over damage math. It is a direct, ugly gameplay failure if true, and those are the kinds of reports players instantly understand.

Diablo 4 has already trained players to expect friction

The timing does not help. We recently covered how players said Ashava’s world boss cache gave no loot, how Season 12 reward complaints were still hitting Bloodied boss loot, and how Flay was reportedly double-casting with WASD input. Different bug families, same overall problem: Diablo 4 keeps producing little moments where players stop trusting whether the game will behave normally from one system to the next.

That broader mood matters because it changes how people read fresh reports. In a cleaner week, a deleted one-post thread might just vanish into the forum swamp. In Diablo 4 right now, even a half-glimpsed combat bug can catch attention because players are already primed to believe the game is capable of something this dumb.

Right now, this one is real but still thin

To be fair, this is not a slam-dunk “major issue confirmed” story. The thread is gone, the author pulled it, and there are no public replies expanding on what zone, quest, or enemy type triggered the complaint. That uncertainty should stay in the article because it matters. But the topic is real, fresh, and visible in Blizzard’s current bug index, which makes it fair game as a watchlist story rather than a fully proven outbreak.

At this point, Diablo 4 does not just need fewer bugs. It needs fewer moments where even the basic act of killing monsters starts sounding negotiable.

Read More

Diablo 4 Players Say Flay Can Double-Cast With WASD

 

Diablo 4 players have found another one of those bugs that sounds small until you imagine it happening inside an actual build. This time the complaint is about Flay, with players saying the skill can sometimes fire twice from a single input when using WASD movement. That is not just a weird animation hiccup. If true, it means a core attack is behaving inconsistently depending on how the player is moving, which is exactly the kind of thing that makes combat feel slippery in all the wrong ways.

The current report sits in a still-visible thread on the official Diablo IV PC bug report forum, where the original poster says Flay will occasionally attack twice off one click while using WASD movement and certain mouse positioning. They also note that Rend can show similar behavior, and that this is happening without the relevant “hit twice” temper being slotted. In other words, players are not describing a build doing what it is supposed to do. They are describing the game freelancing.

One extra swing sounds great right up until it is not

On paper, some people will look at this and say, “Well, free extra attack, what is the problem?” The problem is that bugs like this never stay cute for long. Once a skill starts duplicating inconsistently, you are suddenly in the murky swamp between broken damage, broken resource flow, and completely unreliable feel. A bug that helps one second can sabotage testing, build consistency, and player trust the next.

That is especially true for Barbarian players, because if there is one group in Diablo 4 that tends to notice when basic combat inputs start acting weird, it is the people counting every hit, stack, bleed tick, and timing window like their mortgage depends on it.

WASD is supposed to make combat cleaner, not stranger

Part of what makes this one interesting is the input angle. Diablo 4’s WASD movement is supposed to make the game feel tighter and more responsive for players who prefer direct control. If it is instead creating edge-case behavior where attacks can duplicate under certain input combinations, that is not some harmless little side effect. That is the sort of thing that makes players start wondering which parts of their build are real and which parts are held together by input spaghetti.

We have already covered how Diablo 4 players are dealing with another fake reward notification problem and how Mac players using CrossOver are getting a launch-to-nowhere experience. This Flay issue is a different beast, but it fits the same broader pattern: Season 12 keeps finding new little ways to make the game feel less dependable than it should.

The bigger problem is combat trust

That is what makes bugs like this more serious than they first appear. Diablo 4 can survive a messy tooltip. It can survive a dumb UI prompt. Combat bugs are trickier, because they attack the one thing the game really cannot afford to make slippery: whether your character is actually doing what you told it to do.

As of now, the original bug thread is still up and the topic is also visible in Blizzard’s latest PC bug listings. That does not prove some massive Barbarian crisis. But it does make this a fair live issue to watch, especially if more players start confirming the same behavior. Because once a basic attack starts feeling haunted, people tend to remember it.

Read More