"Unable to use ____ at this time"

[Nixius]

Hello people!

I have been partying yesterday and today and I am getting increasingly frustrated as an archer with the message "Unable to use <abiliity> at this time" coming up. For example, my friend has taken too much hate and is on red HP, I go to bust out a raging strikes WS but raging strikes comes up with that message 3/4 times then too late he is dead; I have left 2s gaps in-between to no avail. What is causing this?

Sometimes I have noticed it on TP moves as well, I spammed shadowbind like 7 times in a row with varying gaps from 1-4seconds and it just wouldn't let me use it with that message - is this perhaps the bug in the UI they mentioned in 'known issues'? Does the cool-down between ranged attacks apply to your next WS also? I.e I do a ranged attack, try to do WS but the delay hasn't processed (4.2s), then because I am hammering it constantly it's messing up?

Any explanations into this would be appreciated, even if I am just being down right dopey for whatever reason =D.

Thanks for reading~~

[Yoohre_WildRiver]

this has happened to me also some times the skill is not on CD, and i have TP and get this message.

[Nixius]

An explanation to how this happens would be very helpful. Even if it is not some kind of bug, I would like to know how to avoid it occurring.

[Hartigan]

I've had this various times as well and found out what was going on. Not sure if it's the case with you guys but a lot of skills for certain classes are context sensitive. For example there are a few PGL skills that can only be performed after you have evaded an attack. Or in the case of a MRD there are coupe skills that can only be performed once you have entered the steadfast stance. Look in the actions info or just hold your mouse over the icon on the action bar and it will say at the end of the description the conditions that need to be met to use the action.

[Nixius]

Since playing this evening after the maintenance it seems to be much better, maybe it was something they fixed but didn't announce. Who knows.