I can confirm this issue is still present in 1.20.5
Can confirm in 1.18.1.
Should this issue be closed for the same reason as MC-66943? Seeing as they are both examples of updating entity data, they are both similar.
I wrote a command for anyone who would like to test this bug to check if it still exists. Run the following command:
/summon villager ~ ~ ~ {Offers:{Recipes:[{maxUses:128,buy:{id:"minecraft:emerald",Count:1b},sell:{id:"minecraft:diamond",Count:1b}}]}}
This will summon a villager who sells one emerald for one diamond. You can easily grab a stack of emeralds and test the bug. I hope this helps!
I just had this problem occur on a 1.12 world in survival mode. The bed was underground (at y=10 if that helps) and was in a 3x3x3 cube dug out. There were two blocks covering the bed one block above the bed. I've included an example of what I am talking about.
[media]
Confirmed for 1.11.2
I know this is already mentioned above, but I can confirm this bug in 1.10.2. Also, the steps to replicate this bug are:
1. Create a world with generate structures off, cheats on, gamemode creative, and customized superflat world type. You can use the preset "3;minecraft:air;1;village".
2. Using the /setblock command, place a block underneath you. For example: "/setblock ~ ~-1 ~ stone"
3. Open your chat and run the command "/spreadplayers ~ ~ 1000 2000 false @p"
4. Observe the results. Now, because there are no blocks for the player to be teleported to, an error in running the command is to be expected. What isn't expected is the message it displays. I hope these steps are useful to anyone.
Yes, I can confirm this bug/inconsistency is still present in 1.10.2, as well as 16w44a.
You might want to add Minecraft Java version as an affected Minecraft edition because of the addition of observer blocks in 16w39a. A very similar glitch occurs there. When opening and closing a door or fence gate, the observer does not detect this block update. I'm sure there are other block updates not detected, but that is just one.
Confirmed in 16w21b and lower 1.10 snapshots.
When a team is configured to have no name tag visibility, it seems this bug also causes pet names to disappear when their owner is near.
[media][media](The screenshots above are taken from my perspective, but I am not the owner of the cat)