.3 Second Positional Update Delay (Requesting Dev Response)

[Astarica]

Well according to the devs by pressing H to face target or by casting a spell it will update your position on the server, so there is indeed ways the client can update your position to the server.

If they said that it is absolutely wrong. Here's a simple test:

1. Turn auto-run on
2. Cast something with >1s casting time (say, Foe's Requieum)
3. Cast something else as soon as you cast the first spell (say, Swiftsong)
4. You'll see a message saying 'can't do that while casting' but your spell will not be interrupted, despite the fact you're attempting a 100% illegal action (casting while moving).

If you were actually able to force an update of your position, then the result of your impossible action (casting while moving) should also come in. It clearly does not.

[Jinko]

If they said that it is absolutely wrong. Here's a simple test:

1. Turn auto-run on
2. Cast something with >1s casting time (say, Foe's Requieum)
3. Cast something else as soon as you cast the first spell (say, Swiftsong)
4. You'll see a message saying 'can't do that while casting' but your spell will not be interrupted, despite the fact you're attempting a 100% illegal action (casting while moving).

If you were actually able to force an update of your position, then the result of your impossible action (casting while moving) should also come in. It clearly does not.

You can't cast whilst running no, because you are running before you cast the spell, the server already knows its an illegal action.

The latency and 300ms works both ways.

If you are running the server needs a position check to say player has stopped moving, that is why sometimes when you run forward and stop and then cast a spell the server gives you an error message, even though you have stopped moving on your screen you didn't on the server.

The opposite reaction is when you are standing still cast a spell and move half way through casting and slide across the floor and perform the action, because even though you still had time on your screen the server had already performed the action.

[Astarica]

You can't cast whilst running no, because you are running before you cast the spell, the server already knows its an illegal action.

And it takes at least 0.6s from my testing before the server acknowledged what I'm doing is illegal, for an action that is illegal 100% of the time. If it was possible to 'force an update', I'd expect to get the result of my illegal action back earlier, but this is clearly not the case. Try it yourself. Start with autorun and try to reliably stop your spell by doing anything you want. There's no skill factor because what you're doing is 100% illegal to begin with, so all you're doing is trying to tell the server 'hey look this is impossible!'. The time it takes you to interrupt the spell represents exactly how far behind the server you are.