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.
