Sometimes I try to fire a spell too quickly after releasing the spell menu and nothing happens. Then I'm left standing there for a beat until I realize it didn't fire and must release the trigger and fire again. This is the worst with Lightning because it takes a moment to see if it is charging, so when it doesn't fire you usually lose up to a second in wasted time. This may not sound like a big problem, but in my experience this small window of time is often the difference between doing damage and getting dodged/blocked.
So what is happening?
There are a few frames of animation after the spell menu is released but before the menu is completely gone where pressing the fire button does nothing.
How do I know I'm not just pressing fire a millisecond before the spell menu is released?
This is certainly possible, but still a usability problem since I haven't been able to correct it in all of the time I've been playing.
What is the solution?
A small tweak that I feel will correct this problem is to add a test at the moment the spell menu is released for if the fire button is currently pressed. If it is, initiate firing per usual. This would handle both cases (where the player either presses the fire button during a "dead zone" where no button presses are being registered AND if the fire button is pressed before the spell menu is actually released).
Obviously it would be good to remove any dead zone, but i like that this solution also elegantly handles the case of a pre-fire.
I should note that if you fully press and release the fire button before releasing the spell menu, nothing would happen since this tweak only cares if the button is CURRENTLY being pressed at the moment when the spell menu goes away.
Fixing this would eliminate one of the biggest feelings of non-responsiveness from the game that I experience on a regular basis.