Description of bug:
If you are holding a lead attached to an animal and attempt to place any kind of block on top of a Fence (assuming the Fence only has air on top of it), the lead will tie to the Fence and the block will appear to place for a split second, but vanish. The block in your inventory UI will also vanish, but this is only graphical. The block is still in your inventory.
To make the block visible again, you must do one of the following:
Open your inventory and click the respective slot the block rests in.
Scroll to the respective “empty” slot and click the ground to place the block. The block will place, but make no sound.
Open any NBT storage block, such as a Chest, Shulker Box, Hopper, etc. The block will reappear immediately.
Quit and reopen the world. The block will reappear upon rejoining.
There may be more methods, but that’s all I could find.
To reproduce the bug:
Hold any leadable animal on a lead
Find (or prepare) a Fence. The top of the Fence must be clear.
While still holding the lead, attempt to place any block on the very top of the Fence.
Assuming all goes right (or, wrong?…), the block will flicker, and vanish in your inventory! But not really…
Expected result:
The game should either prioritize placing the block on top of the Fence, or tying the lead to the fence. I assume a lack of prioritization from these two inputs might be a root cause of this bug… maybe.
Actual result:
When holding the lead and attempting to place the block on the top of the Fence, the block is not placed and the item appears to vanish from the inventory, although this is only graphical. This can be especially annoying when trying to make Lantern posts for horses, which is actually how I discovered this bug.
Extra research:
Apparently, this bug has been in the game since snapshot 16w40a for 1.11. I tried looking for a while, but I’ll still be amazed if this is the only bug report regarding this specific Fence bug, now that I know it’s been in the game for almost 10 years now!
Included attachments:
Demonstrating the bug in version 26.3 snapshot 5
Demonstrating the bug in its first appearance, snapshot 16w40a for 1.11
Linked issues
duplicates 1
Attachments
Comments 3
Nice job researching the first version to introduce this bug 🙂 I think it’s MC-158774
Yes, I think that's it! I'm not surprised to see a duplicate (noting the age of this bug), but I'm a little surprised it's been in the game this long. I actually believe I have more useful information reguarding as to why this bug exists, after observing some of the behaviors from the previous 1.11 snapshots.
Anyways, thanks for helping me find the original.
Thank you for helping us improve Minecraft! We saved your files: