Hi,
since a few days ago, i was playing on Xbox OneX with Ver. 1.2.11.
Around April the 3rd, Xbox told me, there is an update.
I updated and played a few hours.
The next day, the game told me, that the last update was a beta version and it is now not available anymore.
I should deinstall and reinstall the game from the shop to get rid of the beta version.
I did this (now on Ver. 1.2.13), and sorry to tell, but my world is destroyed.
My house, basement etc. all gone.
Most of the blocks simply disappeared.
Any solution on this?
i think my world, which I played on a beta version (which I didn't ordered) is not compatible to the regular Ver. 1.2.13.
what do plan to do on this?
thank you,
Linked issues
duplicates 1
Comments 8
This is the same bug as I reported (linked to this one by Bemoty). This was a forced update for no-beta XB1 gamers done by Mojang and/or Microsoft as an error.
Unfortunately, any world that was opened in the accidentally delivered beta version can no longer be played on 1.2.13. I believe it should be playable in the next regular release when it comes out, but I'm worried by what you said: "My house, basement etc. all gone. Most of the blocks simply disappeared." Does this mean you were able to open it again after you downgraded to 1.2.13? I didn't think that was possible, but if you did I'm afraid the damage might be irreparable.
Obviously, if you have a backup from before you opened it with the beta release, that's an option. You'll lose a few hours' work, but it's guaranteed not to be corrupted (assuming there was no error during the backup).
Mojang is sorry for accidentally releasing the beta, but mistakes do happen. To help prevent a similar problem in the future, I would recommend backing up all your worlds—regularly if you can, but at least before installing an update.
Hello,
Thank you for your honest feedback.
Yes, i was able to open my world in the beta version, and after downgrading.
There was no warning.
I have a backup, but it is a few days old — or another where I am standing in the endcity.
How safe it is to assume, that I can open my beta-ininfected world with the next update? And when will it be released?
Dear @Auldrick,
This is ofcourse not a solution.
We do have regular backups that is the cloud sync is for, this is to prevent accidental dataloss.
I agree with Gerald on this.
And if Mojang do not have versioned saves of the game in the cloud is crazy. Especially when releasing a version of the game that makes the worlds corrupt is even possible.
Making a backup of the saves in this scenario was not possible since the auto update feature on Xbox One. People did not see the update happen before starting the game and saw the beta-info in the top of the screen in-game... and worlds was already modified. The corruption was not apparent before people downgraded as you instructed in the game pop-up.
I'm not interested in a blame-game on this but Mojang and/or Microsoft need to come up with a statement and a resolution to this.
By the way.. Beside having my worlds corrupted, I have a bunch of friends with kids that have cried for days now cause of this. So the dark numbers on this issue...
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-32141.
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.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
@unknown: Redmond is studying whether a repairing upgrade path might be possible in the next release. It will be really complicated, but they'll do it if they can, and I'll bet they'll opt not to do it if they aren't absolutely sure it'll work the first time. They're also considering whether they could do it with some kind of fixer tool. Unfortunately, it's impossible to set a date for the next release.
It might interest you to know that many people on the Bedrock team were also affected by this mistake. Their livestreaming console was hit with it and corrupted some worlds, and a lot of their people had it on their home consoles. As you might guess, Xboxes are pretty popular with the Microsoft Studios folks.
@unknown and @unknown: If you mean my earlier comments to Robert aren't a solution to the problem of preventing future erroneous releases of game-breaking code, I agree, but the bug tracker is not the place to pursue one. However, I can tell you that the release process for Xbox has already been modified to prevent a recurrence. Also, an apology and statement was inserted in the in-game patch notes on two consecutive days when the problem was discovered, but if you didn't see it or don't feel it adequately addressed your concerns you can contact the Community Manager, HelenAngel on Twitter or the Minecraft Discord.
Please backup your worlds because Beta versions are NOT stable.