Josh Simpson
Assigned
Reported
Comments
19w46b here. Just covered my mushroom island in water without knowing this bug still existed. If it doesn't get fixed soon, I'll be manually replacing every mycelium block on the island with grass.
I just spent about an hour in 19w11b killing duplicates from my world (created in 19w09a). I suspected that view distance was responsible for creating them (had it set from default 10 to 16), so I knocked it down to 8 and have not had more duplicates spawn since. Not sure how prevalent this bug was before the 1.14 snapshots (never experienced it prior), but now it seems like only one entity with the same UUID is displayed in the game at a time, chosen seemingly randomly. After killing a duplicate entity, another with the same UUID will be loaded upon relogging. Deleting the duplicates took a very long time as some entities in my base (mostly just specific ones) were duplicated upwards of 15 times, meaning I had to relog at least 15 times to get each duplicate to show in game.
Duplicate entities that are invisible still interact with the world. They are immobile and prevent placing of blocks at their location. Visible mobs such as villagers and golems often get hung up on them when trying to path and sometimes even "look at" them even though it appears nothing is there. There were about 200-300 invisible duplicate entities in my base, to the point where I noticed a lot less lag once all were dead. This is actually a pretty serious problem.
If Minecraft is able to detect these duplicates, a temporary solution should be to automatically delete them. I do not see the harm in doing so. My world is fine now after manually removing them.
I haven't especially paid attention to this in a while because duplicated entities haven't been a problem for me in quite some time now. The "message spam" wasn't really a problem, it was that entities would get duplicated and only one of them would be "active" during any given game session, which caused a myriad of problems. From my own personal experience, it would seem that this bug is fixed now.