mojira.dev
MC-226157

Attempting to lock compasses to lodestones in spawn protection causes a desync

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:

  1. Start a server, join it, give operator permissions to yourself, and switch into creative mode.

  2. Set the world spawn to your current location and summon a lodestone nearby by using the commands provided below.

    /setworldspawn ~ ~ ~
    /setblock ~2 ~ ~ minecraft:lodestone
  3. Obtain a compass.

  4. Switch into survival mode, remove your operator permissions, and grant anyone else with them in order to activate spawn protection.

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

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

Related issues

Attachments

Comments

migrated
[media][media][media][media]
tryashtar

Probably duplicates MC-99075

Avoma

I wouldn't say that this is a duplicate of MC-99075 since this is a block interaction and not a block placement. See MC-225587, for example.

Avoma

(Unassigned)

Confirmed

Items, Networking

compass, lodestone, spawn-protection

1.16.5, 21w20a, 1.17.1, 1.18.1, 1.18.2, ..., 1.19.3, 1.19.4, 1.20.1, 1.21, 1.21.4

Retrieved