Guild Wars 2

apparently the bounding dodger trait’s activation is longer than the dodge. Consequently I’ve found myself being interrupted multiple times mid dodge. Please fix this.

This is actually a common occurance with even the normal dodge if you’re hitting a lag spike.

Unlike most skills, which don’t fire their effects on your client until they’ve been reported to the server and then sent back to you, dodging, like movement, is exectued immediately on the client, and you’ll only notice inconsistancies if your ping is high enough that what you send the server is significantly different than what you performed on the client.

In cases where you’re getting interrupted mid-dodge, what’s happenning is that you dodge on the client, but the ability that is hitting you is actually recieved before the server recieves your dodge command. So, when you get those packets back from the server to sync, you end up interrupted because you were actually cc’s before you dodged according to what’s happening “for real” on the server.

If you have “x happens on dodge” traits that trigger at the beginning of a dodge (like caltrops, or swiftness from dash/acrobatics) you’ll notice when you’re experiencing this kind of latency pretty easily. Those traits should trigger the moment you dodge, but if your latency is bad you’ll dodge and they’ll trigger a little after.

Yep, lag. Lag kills this class as it relies heavily on precision of the operator.