Inherent Design Flaw (imo) with Guard and Server Latency
I have recently decided to stop climb CC because I am seeing that when I press Guard too fast, I apply it and remove it, wasting the cooldown, and usually when I am a focus target. This usually looks like me standing on the point, I am not pressing any buttons trying to stall, and I see the animation happen and go away in a second.
Then I find if I am careful with my presses the button does not go off due to some issue with latency or whatever.
"It works for me"- as I am sure others will think, does not discredit my experience. My PC is plenty modern, and I do not have this issue in other games.
Guard does not have to dispel itself on a second press. It inherently dispels itself when you use another action. I want the developers to know that some of us need to press the button more than once to deal with server issues, and not inherent skill or PC issues.
100% the ability should just end the effect upon using another action or duration expires. If were going to do this for guard, then you should just make expediant, purify, primal scream, and everything that has a beneficial effect remove itself on second press.
I tried cheeky macro fix for this:
/statuson Guard
/pvpac "Guard"
/merror off
/micon "Guard" pvpaction
However, this macro did not work. Ironically if it ability didnt inherently dispel itself, I would just change "statuson" to "statusoff" and that would make the ability work as it does today (assuming they change it for the better in the future).
Or maybe the devs can allow us to using something like the macro above by adding additional macro tag to change guard to work in the way I am suggesting.
Edit: I understand the purpose of the button dispelling itself. It is for the occasions where you have successfully used guard to complete some objective and you do not want the movement penalty and you do not want to waste an action like heal or a target is not available for an offensive action, etc. I just think there should be an option to help with the lag. I would rather there be a macro or secondary form of guard to help assist with connection issues. Client side modifications or something.