-
Bug
-
Resolution: Unresolved
-
None
-
1.16.5, 21w20a, 1.17.1, 1.18.1, 1.18.2, 1.19, 1.19.2, 1.19.3, 1.19.4, 1.20.1, 1.21
-
Confirmed
-
Items, Networking
The Bug:
When attempting to lock a compass to a lodestone in spawn protection, the action succeeds client-side but fails server-side, causing a desync.
Steps to Reproduce:
- Start a server, join it, give operator permissions to yourself, and switch into creative mode.
- Set the world spawn to your current location and summon a lodestone nearby by using the commands provided below.
/setworldspawn ~ ~ ~
/setblock ~2 ~ ~ minecraft:lodestone
- Obtain a compass.
- Switch into survival mode, remove your operator permissions, and grant anyone else with them in order to activate spawn protection.
- Attempt to lock the compass to the lodestone, and once you've done this, reload into the world to see if this action was successful.
- Take note as to whether or not attempting to lock compasses to lodestones in spawn protection causes a desync.
Observed Behavior:
The action succeeds client-side but fails server-side, causing a desync.
Expected Behavior:
No desync would occur.
- relates to
-
MC-99075 Cancelled block place (spawn protection) causes inventory desync
- Reopened