I have a serious problem with duplicating worlds on PlayStation 5.
When i try to duplicate a world, one of two things happen. Most times there is an error message that say's: “Storage full, your system is out of storage space. You'll need to delete some data before you can save anything".
Just to mention, all my worlds together are just about 1,9GB and my PS5 has still 93,82GB of its internal storage space free, so that can't be true.
The second thing that can happen, but doesn't very often, is that minecraft is creating the duplicate of the world, but a corrupted one. In this case the whole world gets ripped appart, chunks are cutted at random Y-levels or completely missing (screenshots), stuff that i have built is deleted, even the world generation gets weird. So chunks that were originally ocean are replaced with beach for exaple, or islands are generated were never one was, even new biomes replace the ones that were at the exact coordinate before creating the duplicate. It's like the world generation is trying to “overpaint" the world file at some spots.
In some very few cases the game kicked me out of the world instantly when loading such a corrupted duplicated world, showing me a message telling me: “disconnected due to world corruption"
I should say, that all the worlds i tried to copy, were old version worlds. Unfortunately i can't remember on wich versions i created them. The oldest one could be 4 or 5 years old, the newest one about 1½ years. I did not try this out on worlds, that were originally created on the latest version.
Due to all this, it's actually impossible for me to back up my worlds, something that feels a little bit risky, i mean, what, if the game corrupts the orininal files while saving them after playing on it? I would never be able to restore anything. Please help Mojang.
Edit: i forgot to say, that even the player data is deleted, so my whole inventory and levels aren't copied either.
Linked issues
relates to 1
Attachments
Comments 5
I have updated to the v1.21.90 Bedrock edition for PlayStation 5 yesterday, the bug is still there.
To answer your question, i have created a new world at this version and copied it. At a quick look, all seems to be good, so i guess the bug only affects worlds, that were created on old versions.
Unfortunately i have not many worlds created, the latest one was created a short time after the release of the Trial Chambers, but i don't remember the exact version. So i'm unable to tell you the latest version that is affected by that bug.
It never crashed completely, but sometimes, about 1 out of 10, it put me back to the main menu, showing the message “disconnected due to world corruption"
Update:
Hey it's me again. I tried something out and that changed the behaviour of the bug a little bit. I had an old event world, called “15 year jorney", you probably know it. It contained some recource and behaviour packs that weren’t listed in the “my behaviour/recource packs" section and i have no idea how big they were, but probably way bigger than the 8,5mb that the world was listed as in my world list in the storage section in the settings.
I have deleted it (sad moment) and after i did that, i was able to duplicate my biggest world multiple times in a row (of course i have deleted the duplicates after that to keep my storage clean). Anyways, unfortunately now i'm unable to duplicate worlds again, minecraft says my storage is full and i have to delete some stuff again. I have no idea why, all my world files are just 2gb and i have not a single addon or recource pack or anything. My system itself isn't full either.
This changed the bugs behaviour. Now the world i duplicate (if it not says storage full) is not so much cursed anymore, the chunks are all in place and there are no more holes or anything. But unfortunately, everything that was built in the world and the players inventorys still aren't copied, so it is like i had created a fresh new world with the same seed instead of a copy of what my friend and me did in this world. I guess this is a bit better than it was before, but still not useful in any way.
I hope this will help you to find out what is happening here. Thank you. 🙂
Thanks for your report. Does this only affect worlds that you have opened in 1.21.60 or later, or 1.21.80 or later?