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

Originally Posted by FinagleABagel

Simple because A does not equal B logically does not mean that A is somehow less than B. Your oversimplifications simply reinforce your total ignorance on the subject. Feel free to voice an opinion, but don't attack when you know far less than me, or in particular, SE.

Like I said before, you can't just compare games without full knowledge of the backend systems. None of us have that. Your suggestions are utterly out of the realm of reality because they ignore what we already know. It's not SE's job to explain every little piece of their process. They very well may be alright with losing a smallish minority of players (face it, people with this problem *ARE* a minority).

Yea keep telling yourself that, you are like one of those people from 1.0 that didn't think there was an issue until SE came out and said they were remaking the game.

There is no problem here guys... nothing to see here.

As for me being ignorant whatever, I didn't come here to start a name calling session, how about you grow up and have an intellectual conversation instead, without resorting to name calling.

Good day to you !

Originally Posted by Astarica

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.

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, I assume jumping is one of those skills which updates your position also.

As for the highlighted part, the client is "supposed" to interrupt your casting but because of the 300ms positional checks and latency issues it rarely does.

For example start a cast then half way through move and you will slide across the floor and execute the spell, this isn't supposed to happen this way it just does because the client can't update the server fast enough.