Guild Wars 2

So I’m not sure if there has already been a post on the dodge roll bug with some specifics, but here is one from me. As people who play a melee class might already be aware of, dodge roll has a bug where it will occasionally fail and cancel your dodge roll animation almost immediately, yet it drains your endurance.

So while learning how to play a guardian, I learned about a bug exploit sometimes referred to as “Ninja Skipping” for hammer. To accomplish this, the player immediately dodges after the second attack in his hammer autoattack chain. What this does is 2 things

1. Lowers the amount of frames required to cast Symbol of Protection therefore increasing dps. Some have reported its lowered the cast time of the 3rd attack in the chain by something close to 300 frames. This leads to better uptime on protection and increased overall damage output.

2. Skipping dodge roll to get the benefit of Selfless Daring (Heal at end of dodge roll) while also not losing any ground against the mob you are fighting. With Vigorous Precision, this means guardians can always remain at 1 bar of endurance while using the other bar to exploit the dodge roll bug to minimize cast times on Symbol of Protection and gain healing from Selfless Daring.

While these are exploits with positive connotations for the player, there are obvious negative connotations to it because this bug so far as I’ve tested it applies to every melee weapon. (Ranger, Guardian, Warrior, Thief) It is much easier to spot on slower weapons, but it can be done on any melee weapon of these classes that I’ve tested. I would imagine the same would be said of Mesmer sword mainhand and necro dagger (Can someone confirm this?). The obvious being that your dodge roll can fail if you do this bug unintentionally and get hit by whatever you were trying to dodge.

I’d really love to get some feedback from a dev on this. This is a long standing bug with the game and it’s baffling that this hasn’t been fixed. It’s a cornerstone of your unique combat system and it has persisted in the game since beta.

As a bug and an exploit, please fix this.