Guild Wars 2 has a bug in its measuring of the duration of key presses. Most of the time, the duration error is at most about 100 milliseconds, I estimate. So, if I press a key (such as the 'move forward' key) for 300 milliseconds, GW2 might interpret that as a keypress lasting anywhere from 200 ms to 400 ms.One place this is obvious is in jumping puzzles. I've played a lot of platformers on my current computer with my current keyboard, and I'm quite good at them. My personal timing is good enough that I can generally hold a key down with an uncertainty of no more than 10 ms, I estimate. But, when I do jumping puzzles in GW2, I find my character often moving too far forward or too little forward, not matching the duration that I actually hold the 'move forward' key down. To my timing instincts, it is obvious that my keypress times are being randomized.But this problem is not unique to jumping puzzles; it happens everywhere in GW2, all the time. It's usually subtle, but it happens for every keypress.One situation where it is not subtle is when playing in a high-lag map instance. There, the maximum duration error grows, and I've seen it as high as two seconds. Yesterday, playing in a very laggy instance of Verdant Brink, I watched my character continue moving forward a good two seconds after I released the 'move forward' key on five or so different occasions, and smaller but still large timing errors were common. I've seen this happen in other laggy map instances too, generally instances with lots of players.Of course, this is not necessarily a single bug. It may be that GW2 has several bugs, some related to input event handling and others related to network communication, that together or individually cause keypress duration errors. Fixing one such bug may not fix the overall problem.