-
Bug
-
Resolution: Won't Fix
-
None
-
20w14a, 20w15a, 20w16a
-
None
-
Confirmed
-
Items
The bug
I set a custom villager trade with a lodestone compass, and when the lodestone was destroyed, the compass did not deactivate and still pointed to where the lodestone block used to be.
How to reproduce
- Put a lodestone block at XYZ: 35, 56, 4 in the overworld:
/setblock 35 56 4 minecraft:lodestone replace
- Use the following command in a command block:
/summon villager ~ ~1 ~ {VillagerData:{profession:farmer,level:99,type:plains},Invulnerable:1,PersistenceRequired:1,Silent:1,NoAI:1,CustomName:"\"compass\"",Offers:{Recipes:[{buy:{id:emerald,Count:1},sell:{id:compass,Count:1,tag:{LodestonePos:{X: 35, Y: 56, Z: 4},LodestoneDimension:"minecraft:overworld"},maxUses:9999999}}]}}
→ Notice how the compass in the villager trade interface points to the lodestone
- Destroy the lodestone
→ Notice how the compass in the villager trade interface still points to where the lodestone used to be - Buy the compass from the villager
→ Notice how the compass has updated in both your inventory and the villager trade interface and no longer points to any location
- relates to
-
MC-177347 Lodestone compasses in mob's hands don't update properly
- Resolved
-
MC-177561 Compasses used on the top of lodestone at y=255 do not break when the lodestone is destroyed
- Resolved
-
MC-176084 Lodestone compasses that are stored in containers, item frames, bundles, or are held by mobs do not update if their connected lodestone is broken
- Reopened
-
MC-176176 Compasses react to the player position and not the chest position when in a chest
- Resolved