Quote:
Not really an issue, it's the consequence of allowing keyboard movement... Yes, it can be avoided easily if you understand how it works, sadly most people don't and they keep on calling it a bug/whining.
|
You also have no idea what you're talking about.
Getting bodyblocked because of a 250ms lag is not to be unexpected in an online game. The problem is that when bodyblocked there's a bug which frequently causes either:
a) the client to not properly update your display with your real position from the server
b) the server to not calculate and/or send down your real position
A slight snap-back is normal in an online game from time to time, but this bug causes you to just run and run and run forever like you're in the clear while you see damage numbers flying off you. The only "fix" I know of is to stop and c-space so you attack whatever the closest body-blocking MOB is which will cause you to get a new position and snap all the way back to the proper location.
It's a known bug that causes your proper position to not be updated unless you stop and force it to happen.
I believe ANET has even acknowledged it and may have been the ones that offered clipping caused by an oversized hitbox for armor graphics as an explanation for it.