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)
Related issues
is duplicated by
relates to
Comments
migrated
migrated
I mentioned it in #mcdevs 😛
wobst.michael
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.
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?