Why do heavy attacks keep getting stuck when I hold the button?

October 31, 2026 5 answers
Asked by PatchPulse

I’m seeing a weird combat issue on controller where a staff heavy attack starts charging normally, but then it just keeps charging and never actually releases. It happens on different platforms and with different staves, so I’m trying to figure out if this is a controller thing, a game issue, or something I’m doing wrong.

I’m also running into another control bug where accepting a quest leaves me stuck until I switch input modes, so I’m not sure if these two problems are related.

Answers

SnareLoop

This sounds more like an input handling problem than a staff-specific mechanic. If it happens on both console and PC with a controller, I’d look at the controller itself first, especially trigger wear, sensitivity, or a button that is not fully releasing.

That said, games with held inputs can get weird if the system thinks the button is still down for a split second too long. A different controller, resetting bindings, or testing without any input remapping would help narrow it down fast.

8BitHush:

It does feel like the game sometimes misses the release signal. I’d probably test another controller just to rule out a sticky trigger before blaming the combat system entirely.

Reply to this answer
MageTinker

I’d treat the heavy attack thing as a game bug until proven otherwise, since it’s happening across different hardware setups. The fact that the same hold input also seems to hang after quest interactions makes me think the game is getting stuck in an animation or input state.

One workaround is to let go a little earlier than normal, then tap block or swap bars if it hangs. Not elegant, but if the game is failing to register the release cleanly, forcing a state change often clears it.

PatchPulse:

That makes sense. The quest one feels especially like the game is waiting on something in the background, so maybe it is the same kind of stuck state.

Reply to this answer
Loadout.Lime

There are a few things that can trigger this kind of weirdness with controller input. Heavy attacks, interaction prompts, and dialogue can all overlap in awkward ways if the game is still processing the previous action when you try to start the next one.

For the staff issue, try not to buffer the heavy immediately after another action, especially right after bar swaps, blocking, or casting. If it only happens in certain moments, that points to animation cancel timing or a control-state bug rather than a broken controller.

QuickKite:

The overlap angle is worth checking. If it only happens after other actions, then the fix may be more about timing than hardware.

StunWarden:

I’ve had games do this when an action queue gets jammed, so spacing inputs out a bit can help figure out whether it is timing or a deeper bug.

Reply to this answer
MellowRespawn

If the issue has been around for a long time, I would not expect a simple in-game setting to fix it. Best bet is to test a few variables one at a time, like turning off any controller software, using a wired connection, and resetting the control profile to default.

If none of that changes it, then it is probably just one of those long-running combat bugs you have to work around. In that case, the practical fix is learning the timing that avoids it, even if that is annoying.

PatchPulse:

That is basically where I’m at, trying to figure out whether I can fix it or just need to learn around it. I’ll try stripping out any controller software and see if it changes anything.

Reply to this answer
HotSwapZero

The separate quest lockup makes me think the game may be confusing controller and mouse input states. When that happens, some actions can stop cleanly while others stay half-registered until another input forces the engine to wake up.

What I would try is using one input method consistently for a while and seeing if the bug drops off. If you are swapping between controller and mouse a lot, that can sometimes make state bugs feel way worse than they really are.

CtrlNomad:

That is a good call. Mixed input can cause some really odd behavior, especially if the game is trying to decide which device is currently active.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions