World corruption when reverting from forced beta (1.2.14.3 -> 1.2.13)

MCPE-32135 can also be linked to this one since it's the same result of world corruption.

Earlier this week, a beta version of the game was mistakenly released instead of the 1.2.13 update. We are aware of the risk of game corruption and provided in-game instructions to avoid opening existing worlds using the beta version due to the risk of world corruption. We sincerely apologise for the inconvenience.

For further assistance or advice you will need to contact Mojang Customer Support directly or follow a link below for community support.

Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki

Does the issue with corrupted chunks only affect worlds that were actually opened in the wrong version, or does it affect other saves also?

Hi Mega_Spud,

The corruption happened with two worlds for me. Both where opened in v1.2.14.3 (beta). I have a few other worlds I have checked now and they are not corrupted (old stuff).

It is important to know that the pop-up in game was not visible the first 1-2 days after the game was updated. So there is a gap here where your instructions did not reach us fast enough and the rollback was possible. Probably the most eager gamers.

But the main question is now. Do you have versioned cloud synced saves? Is it reversible? (i.e the tip about contacting Mojang Customer Support above)

Today my child complained that he can not play with friends anymore 😞 Research brought me to this ticket.

I have not yet uninstalled the 1.2.14.3. If I understand right, if I uninstall it and install the game again then 1.2.13 will be installed and all the worlds that have been opened in 1.2.14.3 will become corrupted. Hence the questions:

Will the next released version support 1.2.14.3 world format? In other words, would it be an option to wait with uninstall until the next version after 1.2.13 is released?

Anybody?

The main question is: will it help to avoid world corruption if we don't downgrade now and wait for the next minecraft release for xbox?

Opening worlds on a lower version, that where opened in a higher version, is never a good idea. In this case they will most likely be incompatible and if you are able to open them corrupt.

Worlds opened in beta's can be unstable too at a later stage. At least create a copy of every world before opening /playing them, so you can always revert to a previous state. Use the pencil icon adjacent to the world to create a copy, do not open the world itself. Even if the world has already been opened, it is still advisable to create a copy in-game at this stage. If you are unsure how to do this, create a new world and try to make a copy of that world first.

Sadly currently there is no way to export or backup worlds on xbox one, other than the build in cloud save system. You can export the world over a realm to for example a windows 10 machine (but they both need Minecraft installed and one active realm subscription).

TL DR: My best bet is to wait and not open worlds in the lower version and always keep a copy of your important worlds. Do not open more excisting worlds in the higher version, without a copy first.

Hi,

Feeback on this issue about the corrupted worlds that happened in 1.2.14.3. When Aquatic update (v1.4) was released now all my worlds that was corrupted is not corrupted anymore. This time around I have also done some backups of all my worlds. 🙂

The only thing that is wrong with the earlier corrupted worlds is that the animals I had within fences is not there. This is a minor issue since I can gather them again.

So in short this issue is resolved for my part. I have my worlds back.

Thanks. 🙂

I'm really pleased the worlds opened ok in 1.4.