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

[Knosis]

Pinging 199.91.189.59 with 32 bytes of data:
Reply from 199.91.189.59: bytes=32 time=95ms TTL=24
Reply from 199.91.189.59: bytes=32 time=89ms TTL=24
Reply from 199.91.189.59: bytes=32 time=93ms TTL=24
Reply from 199.91.189.59: bytes=32 time=96ms TTL=24

Ping statistics for 199.91.189.59:
Packets: Sent = 4, Received = 4, Lost = 0 (0% l
Approximate round trip times in milli-seconds:
Minimum = 89ms, Maximum = 96ms, Average = 93ms

- But still players do this 'stop go, stop go' motion like their positions are being refreshed every other second and they rush to their new position. Also they are running in place a lot. 93ms ping isn't going to cause that.

[Naginata_Nayos]

Bump.
The problem is : when you try to avoid an aoe, you never NEVER know if you made it or not. This is unbearable, how are we suppose to enjoy pve with that handicap ? I insist, this is just not fun and stressful.

[Grailer]

Minimum = 89ms, Maximum = 96ms, Average = 93ms

- But still players do this 'stop go, stop go' motion like their positions are being refreshed every other second and they rush to their new position. Also they are running in place a lot. 93ms ping isn't going to cause that.

Yep game is not very nice for NZ/AUS players , any word on when this will be fixed ? Or should I just zoom out so I can watch myself get hit by ghost AOE ?

C:\ping 199.91.189.59

Pinging 199.91.189.59 with 32 bytes of data:
Reply from 199.91.189.59: bytes=32 time=267ms TTL=230
Reply from 199.91.189.59: bytes=32 time=267ms TTL=230
Reply from 199.91.189.59: bytes=32 time=267ms TTL=230
Reply from 199.91.189.59: bytes=32 time=267ms TTL=230

Ping statistics for 199.91.189.59:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 267ms, Maximum = 267ms, Average = 267ms