I was playing Minecraft bedrock edition with my sister when suddenly a blackout occurred. When power came back, I launched minecraft and then saw my high effort world got corrupted, why would that happen? What's the purpose of auto save if it doesn't help in emergencies? Worlds also corrupt when the game crashes, then why is auto save there if it doesn't help? If the game crashes or the console got turned off suddenly, I should spawn on the latest spot the game auto saved, or else then auto saving have no purpose. Ease help, minecraft isn't playable for me at the moment because power isn't stable in my house, I'll have to wait until you guys fix it in order to play.
Linked issues
is duplicated by 51
BDS-5507
Lost My World due to Power Outage
Resolved
BDS-10028
Minecraft Ps4 Worlds corruption when ps4 accidentally turns off
Resolved
MCPE-58675
Ps4: The data is corrupted
Resolved
MCPE-61361
Power outage game became corrupt
Resolved
MCPE-63015
Console Edition - Currupt Worlds if system crashes/shuts down
Resolved
Comments 38
I noticed that there was a change to how autosave works in 1.14.1. Everything in the world save database is normally supposed to be reachable by starting at a MANIFEST-xxxxx file. When the world is changed, the changes are written to new files and the older versions of those files are left unchanged so that in the event of corruption, the older version of the world can be recovered. The MANIFEST file is likewise left unchanged so that you can use it to find those older files.
During gameplay, autosave creates the new versions and maintains an in-memory copy of the MANIFEST, which it updates to point to the new version files. However, it doesn't write the in-memory copy to the MANIFEST file, because then you'd lose the ability to recover. Instead, it saves the in-memory copy to a file called CURRENT, and only copies CURRENT to MANIFEST after all the updated files are in sync.
Prior to 1.14.1, third-party tools could leverage this scheme by accessing the database through the MANIFEST file, even when the world was open and being played. This enabled them to see a slightly outdated version of the world, since MANIFEST isn't kept strictly up to date by the game. (Technically, this technique is forbidden, but as long as you don't allow the third-party tool to update anything it won't cause any damage to the database.)
Since 1.14.1, however, I find this technique no longer works. If you use a third-party tool to open the MANIFEST file while the world is being played, what the tool sees is a completely empty world, not a slightly outdated one. It's as if the information in the MANIFEST file is now being erased when the world is opened. The game and autosave generally seem to work fine (except perhaps in the event of a power failure recovery) so I have to assume the changed behavior was intentional. But it demonstrates that they did change something about how the world save and autosave work, so it's possible they introduced a bug that prevents recovery from succeeding under some abnormal circumstances.
@Justerfrog yes I do this now sometimes, but it's lame and boring, I have to copy the world every now and then to name sure my world is safe.
@Auldrick so this means there's something wrong with the new system, right? I really hope this gets attention because it's an important problem and it's causing good worlds getting corrupted every day. Please fix the recovery process asap.
We can't say for sure at this point that what I observed in 1.14.1 is a bug, because it's something that doesn't affect gameplay and there's no authoritative definition of how it's meant to work. What I saw might have been an intentional change to the world save and is working as it's intended to, and it's just a coincidence that whatever is causing your world corruption sounds like it could be related.
We have tagged the developers asking whether they think what I saw might be a bug and might be causing your problem (as well as another bug we've found that sounds like it could be related). If they agree, we'll forward this report to them through the normal channels. But even if they say it's not related, there's still some kind of issue here and we'll pursue it. It'll just be harder to narrow down on it in that case, and we'll probably have to get more information from you. So stay tuned.
You guys really need to fix how the game saves. If I didn't keep creating a backup of my game saves after every hour of gameplay, I would have lost my 2+-year-old world several times.
Whenever there is a power outage, the game will ALWAYS get corrupted and be deleted. This never happens on any other game I have, just Minecraft.
I don't know what coding or protocol you use for Minecraft game saving, but it currently sucks. I have had to RAGE QUIT my game for weeks on end because I forgot to duplicate my game save after several hours of gameplay and builds, only to lose all the hours of work because the game save file gets corrupted and deleted after a power outage.
This isn't something new either. You all know that this problem exists. Why haven't you fixed this?
PS4, PS5 Bedrock. Current version.
Steps to Reproduce:
1. load world and play for several hours
2. Wait for a power outage - or pull the plug.
3. Try and load saved world, then Rage Quit game.
Observed Results:
Spend several hours building things, then the power goes out. The power comes back on and turn on the PS5 and loads the Minecraft game. Go to load the world file and get an error saying the file is corrupted and the file gets deleted.
Expected Results:
Expect to load Minecraft and up again and open the saved world and be back at the last save point.
More on this, just in case it might help IF anyone is watching this:
In line with MacBros just said 2 days ago, i quitted the game for a while and just yesterday decided to recover the last backup i had, fortunately i do back ups from now and then but still lost a month worht of gameplay. Anyway going technical:
This is for Bedrock in PS4:
When triying to retrieve the back up from the file on the cloud:
You need to deleted the actual saved game, it does not overwrite properly over the same game with the same name. this might give you a clue to where the problems are.
First i tried to just overwrite the file, it did not worked, FUnny fact, it seems to append both contents, the initial file was arouns 600mb, and the file after download the oncloud version weighted 1,2 gb, and still did not work, stopping at the same place in the bar as before (right after the end of it).
Deleted the old saved game, and downloaded a fresh instance of the back up, and this time it did work. So actually the overwrtting from the cloud saved version did not work properly. that is something to look at also.
Please everyone reading this thread upvote the issue so the Jira does its job.
Please adiministrators of this Jira up vote this thread with as many inputs you have in the 30+ duplicated thread you have all around, so developers have a TRUE sense of how many people is pissed of. To close a thread and redirect to duplication without upvoting it subsequentially is a waste of time for all those people who wrote those 30+ threads.
This also happened to THREE of my worlds since I live in a country with frequent power outages. I constantly make backups, but I still end up losing my progress constantly if I forget to make a new backup. It corrupts the world and only gives me the option of deleting it. None of my other games delete my worlds in the event of a power outage i.e. No Man' Sky. The issue still exists in the latest version of Minecraft Bedrock on PS4 (as of May 5th2024).
it happens when it auto saves when the power goes out
a solution would be to have the world save to 2 different places, at different times, so only one can be corrupted at a time.