The issue:
The 1.21.60 changelog states the following:
Creakings are now persistent like any other hostile mob, meaning they won't disappear on save/load
Creakings spawned from Creaking Hearts now always persist upon reloading the world (MCPE-188352)
Creakings spawned by a Creaking Heart can now be nametagged, preventing them from despawning during the day
Despite these changes, named creaking mobs are still despawning upon reloading the world or switching dimensions, regardless of the time.
Steps to reproduce:
Create a new world, enable cheats, and teleport to 200 100 200 (shouldn’t have to be at these specific co-ords - it’s just where I tested)
Place 10 creaking hearts on the ground and set the time to night
Rename all 10 of the creaking mobs that spawn - you may want to fence them in
Set the time to noon (makes it easier to see if any despawn)
Leave and rejoin the world a few times, and eventually one or more of the creaking will despawn
Expected results: all 10 of the named creaking mobs will remain across reloads.
Observed results: over several reloads, the number of named creaking mobs decrease, until there are none left.
This is a frustrating issue for players like myself, who want to keep creaking mobs around in survival worlds, and completely goes against what the 1.21.60 changelog claims to have fixed.
Linked issues
is duplicated by 4
Comments 12
Got the same thing on IPhone… they remain indefinitely as far as I can tell, until the world is reloaded.
Similar thing happened on 1.21.73.01, left the named creaking at home to explore, reloaded the world, and returned home to see the creaking gone.
I just tested this on BDS Ubuntu 1.21.80.3, and my name-tagged Creaking still despawned on world reload, same as before. This does not appear to be resolved.
MCPE-220432 a “new” open one to maybe catch attention.
Well, the issue clearly was not fixed yet marked as Resolved and no info about “regression” is readily available besides this 5 year old reddit post: https://www.reddit.com/r/MinecraftDungeons/comments/gzn8vj/community_manager_intro_community_bugs_and_you/
So it wasn’t clear what the process is. Clearly also the process doesn’t do both Dev and Final Release testing (verify no issues once released before closing, even if Dev somehow had no issues), which then lead to squeaky wheel theory.
Observed here as well on Windows client/BDS. Tagged creakings will remain during the day, but then will be just disappeared after world reload.