Movement packets arrive too late
The client queues actions that depend on the current move immediately, but waits until the update tick to queue the actual move. This means that the server receives and processes moves after actions that use that move. Can be problematic for internal bounds checking and for third party software (anticheat).
Solution: Insert moves into the queue before non-movement packets? (EDIT: would break digging downwards)
Linked Issues
is duplicated by3
Created Issue:
Movement packets arrive too late
The client queues actions that depend on the current move immediately, but waits until the update tick to queue the actual move. This means that the server processes moves after actions that use that move. Can be problematic for internal bounds checking and for third party software (anticheat).
Solution: Insert moves into the queue before non-movement packets?
The client queues actions that depend on the current move immediately, but waits until the update tick to queue the actual move. This means that the server receives and processes moves after actions that use that move. Can be problematic for internal bounds checking and for third party software (anticheat).
Solution: Insert moves into the queue before non-movement packets?
is duplicated by
is duplicated by
relates to
The client queues actions that depend on the current move immediately, but waits until the update tick to queue the actual move. This means that the server receives and processes moves after actions that use that move. Can be problematic for internal bounds checking and for third party software (anticheat).
Solution: Insert moves into the queue before non-movement packets? (EDIT: would break digging downwards)
is duplicated by
relates to
relates to
Marking fixed then (in some version between 15w31c and 15w44b), the bug you're experiencing now is probably caused by MC-90022.
Probably caused by MC-90022.
Done! By the way, you don't need to type out the entire link, just put "MC-90022" and it'll automatically link (and add the ticket title on hover).
Relates to MC-90022 (not a duplicate though since that one is about movement packets)
I swear I've seen this issue reported somewhere, probably on this tracker, in the last few days. Did you perhaps talk about it elsewhere?
I mentioned it in #mcdevs
Is this still an issue in the most recent versions (currently that is 1.10.2, or 16w43a) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time. If you are the owner/reporter of this ticket, you can modify the affected version(s) yourself.