If you can’t use skills in Diablo 4, you should know that this serious bug is currently affecting many players. Diablo IV early access is now live for players who have purchased the Ultimate Edition. However, the experience is plagued by numerous bugs at the moment. One particularly problematic glitch prevents players from using abilities, emotes, and dash in Diablo 4. Here’s what we know about it.
Diablo 4 Can’t Use Abilities, Skills Not Working Bug
In a game such as Diablo 4, your skills are basically the only buttons you will be pressing on your keyboard. Thus, being unable to use skills in Diablo 4 is a game-breaking experience. Unfortunately, that’s exactly what many players are experiencing on the early access launch day. Specifically, there is a bug currently which prevents players to use abilities, emotes, or dash and other movement skills. For now, it doesn’t seems obvious what triggers this bug. “Can’t fight at all. All I can do is use potions and walk around”, says Reddit user Lanur.
Reddit user Mykevelli goes into more detail. He explains that he can use potions, pick up loot and interact with clickable objects. However, he can not use any abilities, activate an emote or use Dash. Many other players confirmed they suffer from the same game-breaking bug, where they can’t use skills, attack, or teleport in Diablo 4.
What’s common for all these issues is that it seemingly only happens to players in dungeons. Some players speculate that this bug has to do with teleporting to another player or after using a waypoint. However, we can not confirm that. Unfortunately, at the time of writing, there doesn’t seem to be a solution for this. The only thing you can do is leave the game and log in again in order for it to start working. If we come up with a more elegant solution, we’ll be sure to share it with you. If you know a solution, share it with us in the comments!
Can’t Attack or Use Skills in Diablo 4
Unfortunately, this bug is well known to Diablo 4 players from Early access. We hopped that the Day 1 Patch will fix this issue, but it was not the case. So far, the only workaround is to restart the game. If the problem persists your only option is to contact Blizzard support.