Guild Wars 2

I noticed during this update, something seems to have broken the ability dodge Tequtal’s waves.

Normally when Tequatal creates the wave, you can dodge it to evade the wave during the dodge animation. With it broken, the character is getting hit in the middle of the dodge animation as it doesn’t say evaded. Even thou if it does say “evaded” once, in the wave, I would still get hit by wave anyway which should of been “evaded”.

This needs to be fixed because other players have noticed this as well.

Yes, I noticed this too recently, just thought it was me momentarily losing my ‘knack’ for timing it.

Seems it works 50% of the time, so I’d guess they’ve made some server code changes, and so we’ll prob now just simply have to relearn the precise timing again.

I created and posted a YouTube video of the bug with annotations when I dodged.

When observing the video, the first 2 dodges fail when it should of been evade. The 3rd time I dodged, it was successful.

https://youtu.be/2ormjK6HGfE

I also found another related bug and it’s with the fish heads.

https://youtu.be/kPZ_96rK2fM

I was going to start a topic on this, but I’ll just add to this one.

This is still happening, and it goes beyond Tequatl and fish heads. Those attacks just make it much more apparent and more difficult to dismiss as a poorly timed dodged because you can see the dodge animation being interrupted. There appears to have been a significant change in how a successful dodge is determined, or at least how that interacts with network latency and server-side delays.

When the dodge key is pressed, the animation begins pretty much immediately, but there is a delay (almost imperceptible under good network conditions) before the endurance bar drains and your evade timeframe begins. It becomes very obvious sometimes during full-map world bosses or large wvw battles (those times when your skills won’t even cast), but it’s always there and always has been. This means that even after your dodge animation has started, there is a window where you can still be hit before your endurance is spent.

How this has worked from launch up till recently, is that the lag damage window ended the instant the endurance bar began draining. Any time you thought your dodge was done in time but you still got hit, you would not have lost any endurance. Even if you already saw the dodge animation on the character. Far from ideal, but easily explained by network latency and the server waiting to confirm a legit dodge before allowing the evade window to start.

After the recent changes, the lag damage window is extending beyond the start of the endurance bar drain. This means you can dodge in time, have your endurance spent, and still get hit. This is apparent in the videos posted above. From what I have noticed, the timing is very unpredictable and doesn’t seem to be completely tied to network latency. With a ping of 50ms (1/20th of a second) there shouldn’t be a discernible delay in the evade time frame’s start, as there is no delay between keypress and endurance loss.

Another thing I’ve noticed with Tequatl’s wave attack, and is also in the video posted previously, is that successfully dodging the wave no longer gives an “evade” text popup or combat log entry.

I just jump over the waves rather than dodge them and that seems to work just fine. The timing for jumping over hasn’t changed at all.

This is still happening, and I keep noticing more and more instances where I’m being hit by attacks I know should have been dodged. Combined with the animation/hit sync issues that have been around for over a year, dodging is just as much RNG/luck as it is player skill.

The more of it I see, the more I’m convinced it’s something Anet has done for server load/efficiency. The desync issues with some world bosses (Jungle Wurm and Golem Mk II’s slam attacks are the most obvious) started being common right along with them making changes to how the game server queues and processes actions. I get that managing server load efficiently is important, but when your optimizations rely on negating players’ ability to react and utilize the primary survival mechanic of the game, it’s time to find somewhere else to optimize or just upgrade the hardware.

The support team has confirmed that this is a bug since I have an existing ticket open with them since the end of March. I assume it would of been fixed already but still has not.

Here is the first response.
"
…
Thanks for contacting the Guild Wars 2 Support Team!

I appreciate your report on this issue you’re experiencing! The dodge should very much negate the damage endured and I see from your video you still take damage. I’ve gone ahead and submitted a formal bug report and the team should be looking into this soon. Please don’t hesitate to let us know if you run into any other issues, we do appreciate the information you provided!

Have a great day! Happy Gaming! ?(o???o)?
Regards,

GM Stinky Ghost
Guild Wars 2 Support Team
"

2nd response when I informed them about the fish head.
“Thanks for the update!

That’s so weird! I’m sorry for any inconvenience this may be causing you! Please do let us know if you have any further updates on this bug! Thanks again! (o´?`o)

Regards,

GM Stinky Ghost
Guild Wars 2 Support Team
"

I haven’t played in a while and started playing again. I still notice this still has not been fixed yet.

Any updates?