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

[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.