Guild Wars 2

Actually this happens with any weapon/class, it’s just that the guardian’s hammer attack is so long that it is more likely to happen there.

I what’s going on is that movement and dodging happens client side to be more responsive, while attacks are entirely server side. So if you try to dodge just before the next auto attack, your client will try to dodge (and play the animation/ reduce endurance accordingly) and the server will interrupt the dodge to make the attack.

PS – The hammer’s 3rd attack is that long because of the symbol, which does additional dps and reduces incoming damage by 33%, thus the longer wind up to balance this. I do agree it could be a little faster, but that’s an argument for another thread

Well, the simplest way to do it would be to have a dodge able to interrupt an auto attack. In fact, dodging should be able to interrupt pretty much anything else, since when you need to dodge, you need usually need to do it fast and on very short notice. That way the dodge always goes through.

Since each class can only use one type of armor, it seems kinda silly to bunch all three types into one category with no way to filter them.

It’s also a very fun weapon for dungeons. The blast finisher on 2 lets you set off all kinds of powerful combos, 3 and 4 let you control mobs to keep them off your allies and 5 is good for (among many other things) slowing down large pulls at choke points.

This happens to me all the time, very frustrating to dodge an ettin and get face planted anyway >.<

Fixing this bug would be a huge quality of life improvement for melee classes!

Just got killed by lag. I ran up to a bandit and tried to use my number 4 skill. The skill started pulsing as if it were about to activate but did not, in the meantime the bandit started attacking me. Tried to use number 1 and 6 skills and they also began pulsing. When I ran away, the bandit followed and I also discovered that I could still dodge, though eventually I was killed. When downed, both 1 and 4 were pulsing but not going off and eventually I died. Trying to map to a waypoint had no response, though I got the message “A kind soul is trying to revive you.” By the time I got out of the map screen no one was around, though my health had gone up slightly and then stopped. At that point I exited the game.

I won’t try to guess the specific causes of what was happening, but overall it felt as though the game were playing normally except my skills just weren’t going off. This has happened before, where I could see mobs/other players acting in real time and be able to move around myself but not use skills for extended periods of time (10 to 30 seconds). One time this started in the middle of a fight and my auto attack was still cycling, allowing me to survive. In other words, not your usual latency. Only one time when I was running across queensdale did it result in a disconnect.

I only started noticing this as a repeating problem last night after the patch, if it’s happened to me before that I don’t remember, though I have had some ‘normal’ latency problems the last few days where the game just doesn’t respond at all.

Came across this when I tried to play in the plains of ashford, though it seems others in the thread have had it much worse. The latency itself wasn’t so bad (less than a second) but it’s effect on combat was. Timing was a mess, skills didn’t go off correctly or at all (sometimes the animation would play but the skill itself wouldn’t activate) and the auto-attack seemed to be tripping over itself with weird pauses or stopping entirely. Thought the problem was on my end until I went back to queensdale, then everything was snappy and perfect again!