Sorry SE, but endgame won't work if you don't fix something.

[Silverwalk]

...
What SHOULD happen is:
AOE cast initiates
AOE cast completes and server checks position of all players in vicinity
Players in the effect are damaged

What IS happening is:
AOE cast initiates
Server polls character locations
AOE cast completes
Server applies damage to all characters in effect range at the time of the poll, regardless of whether or not they moved

Thank you, your explanation is clearer than my attempt http://forum.square-enix.com/ffxiv/t...=1#post1267314

So in the worst case you have to be out of the red before the cast bar finishes by:
300ms + Your Latency + Server processing time

For example with 200ms latency that's more than 500ms or 1/2 second (we don't know how long the server processing time is).

edit: and what's worse is you get a double whammy with latency because you don't see the cast start until the server message arrives at your computer.

So 100ms of extra latency means you have 200ms less time to get out, nearly 1/4 of a second less!

To the next post: exactly! This is why videos show dead bodies sliding long the ground lol, the server says you're dead but is catching up with your movement data afterwards.

[SKYeXile]

Thank you, your explanation is clearer than my attempt http://forum.square-enix.com/ffxiv/t...=1#post1267314

So in the worst case you have to be out of the red before the cast bar finishes by:
300ms + Your Latency + Server processing time


For example with 200ms latency that's more than 500ms or 1/2 second (we don't know how long the server processing time is).

Well imagine this as a scenario. A 1 second cast attack. on 200ms ping, factor server ticks at every .333 seconds and client sending packets every .333 seconds.

[1]00000 Server tick sends packet data for AOE attack
0.100 AOE shows up on your client (remember 200ms is for a round trip)
0.300 You react and begin moving. (avg 200ms reaction time)
[2]0.333 server tick and your client sends data.
[3]0.666 server tick and your client sends data
0.700 You have cleared the AOE. your client holds onto this to go with the next packet due to be sent at "1".
0.766 server receives your new packet 3 location
[4]1 server tick, aoe explodes, server calculates based off your last known position(packet 3) your client also sends data that you have moved
1.100 you receive packet that you are now dead.
1.100 server receives your updated movement data.
[5]1.333 server process your new movement data, and sends you packet: "LOL, YOU ALREADY DEAD BRO!"