Why the netcode issue exists, and why it cannot be fixed.

[Sinth]

When you hit spacebar (or whatever you mapped jump to) your character immediately jumps. If it was controlled by the server you would lag between when hit you space bar and when you jump. There's nothing unusual with the way your client renders any of the information. The only thing unusual about this game is that server gets to call all shots.

No. Your character jumps on your screen, but does not immediately jump on the server. Whereas, in the client live-state you hit the space bar, and when the command resolves with the server, you then jump on your screen.

Basically speaking, everything you see on your screen is a lie. None of it is real-time on your screen (except for maybe turning your camera angle, which is not negotiated by the server).

But there's no way this is true. That'd mean we'd have cases where you pop an invulnerability ability (say, Ice Block), have its CD charged, and still die. Can you imagine the amount of crying in a PvP forum if there's even a slightly chance that you use your 'save self' ability only to see it not only not work, but you're charged the CD for using it? So the only conclusion is that other games do not use the same kind of design.

You can test this on your own by saturating your connection (start a bunch of downloads). When you hit an ability, the animation instantly goes off, however, the cooldown is not proc'd until the server responds. You can sit and spam abilities that would normally have a 2 minute cooldown repeatedly (while seeing their animations) until the server receives the information and tells your client to pop the CD timer.

[Astarica]

No. Your character jumps on your screen, but does not immediately jump on the server. Whereas, in the client live-state you hit the space bar, and when the command resolves with the server, you then jump on your screen.

Basically speaking, everything you see on your screen is a lie. None of it is real-time on your screen (except for maybe turning your camera angle, which is not negotiated by the server).

Um no, because if there's a delay between your jump gets processed by the server, you'd not be able to reliably jump up across elevation, because there's a chance the server isn't aware you're 'jumping' yet and then you'd get bounced back because the server will decide you're not really jumping and thus not having enough altitude to clear the elevation. Even as laggy as this game is, I've never had a case where I tried to jump up elevation in a valid location and get bounced back by magic.

[Sinth]

I'm not going to debate what you believe vs. what I have been taught and have first hand professional experience with. Feel free to believe what you want.

Also, the fact that teleport bots exist should sway you to reconsider your hypothesis about location reporting. I could write a program today to teleport me anywhere I want in FFXIV. It is extremely simple, mainly because location reporting is not restricted.

[Sadebreth]

Um no, because if there's a delay between your jump gets processed by the server, you'd not be able to reliably jump up across elevation, because there's a chance the server isn't aware you're 'jumping' yet and then you'd get bounced back because the server will decide you're not really jumping and thus not having enough altitude to clear the elevation. Even as laggy as this game is, I've never had a case where I tried to jump up elevation in a valid location and get bounced back by magic.

A better explanation of this would be if you are running through an environment but you notice nothing else on the screen is moving. Your character is moving just fine and then you are dropped out of the game with a disconnect message. When you log back in you are way back from where you got dropped at because the server was not receiving new location information from your client. You were disconnected from the game but you did not know it until your client finally timed out. The same would happen if you jumped to the point you were talking about. If you are not sending information back to the server, you could jump to that point and see yourself in that point on your screen but when you disconnected and log back in you will be back on the ground because that was the last point your client sent new location information and was received successfully by the server. I have had this happen quite a few times. This raises the question however about why on some peoples machines the character completely stops for a few seconds and then shoots forward to a new position once the connection catches back up. You would think that if this is what was really happening then you wouldn't see this kind of stuff on the client side.