This is in response to the request for feedback on combat responsiveness in the recent dev post. My experience is mainly with Fire Staff and Ice Gauntlet. I have noticed that if you are hit during the first few animation frames on some spells, the spell will go on cooldown yet the spell does not trigger. Other spells however, do not have this issue (the spell does not trigger yet the spell does not go on cooldown and you can immediately cast it again).
The most obvious example of this is that Ice Storm can be put on cooldown if you are hit during the first few frames of casting, (the spell will not trigger yet it goes on cooldown). This is a huge deal for the Ice Gauntlet since it is so essential to the playstyle. Other spells, such as the Fire Staff’s Burnout can be canceled in a similar manner if you are hit, however they do not go on cooldown. I believe Ice Storm should behave more like Burnout, since it is very punishing to have a cooldown for a spell that did not go off.
This also happens with Life staff. Casting self heal & healing circle sometimes gets canceled & there is a split second delay before you can cast again. If it didn’t go on CD even though it wasn’t cast. I do experience the same thing with Gauntlet as well. Part of me thinks maybe some of it may be intentional like npc spell cancelation? But the majority of the time its from animations or knocks while casting. It makes for some serious frustration for a few sec while waiting for cooldowns or that brief unable to cast pause to go away.
This is the only other post I’ve seen addressing this issue. Its about life staff though.
This is happening with Riposte on the rapier aswell, if you get hit the first few frames, there’s no Riposte animation, you still get damage by the enemy, and the ability goes on cooldown. Really frustrating sometimes