[BDS-6959] Mobs that have been nametagged or leashed or should not despawn (e.g. villagers) constantly despawning in Minecraft Bedrock 1.16 Created: 02/Jul/20  Updated: 04/Jul/20  Resolved: 04/Jul/20

Status: Resolved
Project: Bedrock Dedicated Server
Affects Version/s: 1.16.1
Fix Version/s: None

Type: Bug
Reporter: Oli Assignee: Unassigned
Resolution: Duplicate Votes: 1
Labels: None
Environment:

Minecraft Bedrock Edition 1.16 for PS4 in a World


Issue Links:
Duplicate
duplicates MCPE-21416 Mobs and Entities can despawn randomly Resolved
Confirmation Status: Unconfirmed

 Description   

In my Minecraft PS4 1.16 world, constantly now villagers or mobs I have nametagged, leashed, fed or bred have despawned. This has happened with foxes, turtles, villagers, dolphins, fish, and polar bears. This is becoming a serious issue in my Minecraft world as I am losing level 5 villagers I have traded with many times, and I am losing some of the animals in my zoo. Please fix this, it's now to the point I no longer want to log in in fear it might cause more animals to despawn while playing. I can verify these mobs have not escaped or died.



 Comments   
Comment by IonicEcko [ 04/Jul/20 ]

Thank you for your report!
We're tracking this issue in MCPE-21416, so this ticket is being resolved and linked as a duplicate.

Please note though, this project is for the Bedrock Dedicated Server software only. For any future reports please head over to the appropriate project (links below).

Minecraft: Bedrock Edition — Gear VR, iOS, Android, Windows 10 (from the Windows store), Xbox One, Windows 10 Mobile, Fire TV, Nintendo Switch, and PS4
Minecraft: Java Edition — Windows, Mac, and Linux
Minecraft Launcher — Bugs about the Minecraft Launcher specifically
Minecraft Earth — AR Compatible Devices
Minecraft Dungeons — Action-adventure title set in the Minecraft universe

Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 BDS Wiki – 📖 FAQs

Generated at Sat Jan 11 07:38:46 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.