Thread: .3 Second Positional Update Delay (Requesting Dev Response)

I'm not sure where people even get the idea that you can force the client to update your position, as the ability to do this would completely negate the design of the game itself (check every 0.3s). If there was actually the ability to do this, this problem can be solved immediately by forcing the client to update whenever any AE is finished casting. It's more like if you have the time to actually jump, or cast, or spin around in a circle or any other thing after you cleared an AE you obviously cleared the AE with a rather comfortable margin so even with the lag, you'd still comfortably beat the AE. Given the client doesn't even get to interrupt a spell you cast while moving even though it's literally impossible to cast a spell while moving in this game, it's pretty safe to assume your client has no ability whatsoever to force anything to happen on the server.

Here's a super easy way to see the lag in this game is persistent. Take a spell that takes more than 1s to cast, and just put auto run on and keep on try to cast that spell while running and see how far the spell casts. I picked Foe's Requiem (3.00s), and I range between 1.80s to 2.40s left before it is interrupted. That means it takes 0.6-1.2s before my client realizes that I cannot cast a spell while running continously. That's how far behind your client is compared to what actually happens on the server. There's no skill involved in this particular action, since I'm just running in a straight line and seeing when the spell stops. There is certainly no in game mechanics that'd allow you to cast a spell while running. I tried jumping and mashing random other buttons and they've no discernible effect on the time before the spell gets interrupted.

Originally Posted by Jinko

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.

Originally Posted by Astarica

... it's pretty safe to assume your client has no ability whatsoever to force anything to happen on the server.

If that were completely and totally true, there wouldn't be mining/botany/farming bots teleporting around instantly. Seems the client has a lot of say in some things like character position/moving. Although, the hard-limit for the client to tell the server where the character is, is probably limited to once every .3 seconds at most like you were saying because that's as much as the server is set to care about.

Originally Posted by FinagleABagel

Where exactly did I say there was no problem? I listed three distinct problems and wrote off yours, because it deserves to be written off.

You've already proven that you have no interest in actual dialogue, you just need an avenue to vent frustration. That's fine, but don't confuse it with actually knowing anything about the problem or doing any sort of positive conversation to help fix it.



Source?

You want a source you go look for it, you can write off whoever you like and pretend to know it all, but at the end of the day you are the one who looks silly.

You can sit there and believe the nonsense SE tell you when they talk about server limitations and yes I will agree with you that nobody knows the ins and outs of their server infrastructure but as I say if other MMO's have minimal issues like these then the fault clearly lies with SE and the netcode.

You can defend them all you like but I don't' think that does anyone any good and it certainly won't get these issues resolved.

I can actually cast heals and run at the same time lol!

Originally Posted by APilgrim

If that were completely and totally true, there wouldn't be mining/botany/farming bots teleporting around instantly. Seems the client has a lot of say in some things like character position/moving. Although, the hard-limit for the client to tell the server where the character is, is probably limited to once every .3 seconds at most like you were saying because that's as much as the server is set to care about.

Teleport is impossible to stop preemptively in any modern MMORPG because it's not tractable for the server to verify every movement/position is valid. But unless you're planning on using a teleport hack to get out of AEs (which will absolutely work if you got the right coordinates programmed ahead of time), that's not exactly useful.

Originally Posted by Astarica

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.