My survival world was normal until today. I have no idea why it has stopped saving progress. I thought it could be some bug with the Nether, with the horses, or something like that. But I have done A LOT of tests and I noticed something very strange. ONLY THIS WORLD has this issue. Other are still saving.
I save the world by pressing the "Back to Menu" button, without closing the app or turning off the device.
Can someone PLEASE help me???? I can't play on that world anymore, it shows the proper screenshot, but when I enter, I'm back to the old save, with all my old stuff, old XP and overall, old world...
(By the way, sorry if I wrote something wrong, I'm trying my best to speak english correctly)
I play on a Samsung Galaxy J5 2016 (SM-J510MN)
Attachments
Comments
migrated
migrated
Auldrick
It seems as if Minecraft is either not really saving the game or reverting to a saved backup when you open it. If it is not saving successfully, it might be because you don't have sufficient storage space on your device for the new save files. (The thumbnail is probably just overwritten and doesn't require any additional space, so that part works.) Can you free up some space and try again?
If the game is reverting to a saved version, it might be because of an error in a resource pack or because the saved game is corrupted. It doesn't seem likely that a saved game would be corrupted every time unless you're out of space; otherwise a lot of people would be having this issue. So if you're using any resource packs (either game-specific or global), try disabling them.
If neither of those suggestions helps, the next step would be to reinstall Minecraft. It probably won't help either, but it has to be eliminated as a possible cause. Make sure to back up your worlds first.
BTW, your English is flawless. I would not have known you aren't a native speaker.
Auldrick
It seems as if Minecraft is either not really saving the game or reverting to a saved backup when you open it. If it is not saving successfully, it might be because you don't have sufficient storage space on your device for the new save files. (The thumbnail is probably just overwritten and doesn't require any additional space, so that part works.) Can you free up some space and try again?
If the game is reverting to a saved version, it might be because of an error in a resource pack or because the saved game is corrupted. It doesn't seem likely that a saved game would be corrupted every time unless you're out of space; otherwise a lot of people would be having this issue. So if you're using any resource packs (either game-specific or global), try disabling them.
If neither of those suggestions helps, the next step would be to reinstall Minecraft. It probably won't help either, but it has to be eliminated as a possible cause. Make sure to back up your worlds first.
BTW, your English is flawless. I would not have known you aren't a native speaker.
migrated
Sounds just like my issue https://bugs.mojang.com/browse/MCPE-29825 but on Windows 10
migrated
Sounds just like my issue https://bugs.mojang.com/browse/MCPE-29825 but on Windows 10
[Mod] LateLag
I found a way to fix it, I went in the world files. Apparently, there was nothing wrong. I saw a document called "CURRENT" inside a file called "db". In that document, I saw the current manifest the world was using. I don't know what they do, but I thought it would be a great idea if I deleted the manifest (the current one, because there was a lot of manifests for some reason). It worked, when I entered the world again, it generated another manifest, deleted all the extra documents and now I can play my survival world again. I still have no idea WHAT happened, and WHY it did.
If you're having the same issue, feel free to try this. Might work! 😉
On a Phone:
/ > storage > emulated > 0 > games > com.mojang > minecraftWorlds > RandomWorldCode > db > CURRENT (open as a text document)
OR
/ > sdcard > games > com.mojang > minecraftWorlds > RandomWorldCode > db > CURRENT (Open as text document)
On a PC:
C: > Users > YourUsername > Appdata > Local > Packages > Microsoft.MinecraftUWP_8wekyb3d8bbwe > LocalState > games > com.mojang > minecraftWorlds > RandomWorldCode > db > CURRENT (Open as text document)
IMPORTANT: ALWAYS HAVE A BACKUP OF YOUR FAVOURITE WORLDS, IN CASE SOMETHING BAD HAPPENS
[Mod] LateLag
I found a way to fix it, I went in the world files. Apparently, there was nothing wrong. I saw a document called "CURRENT" inside a file called "db". In that document, I saw the current manifest the world was using. I don't know what they do, but I thought it would be a great idea if I deleted the manifest (the current one, because there was a lot of manifests for some reason). It worked, when I entered the world again, it generated another manifest, deleted all the extra documents and now I can play my survival world again. I still have no idea WHAT happened, and WHY it did.
If you're having the same issue, feel free to try this. Might work! 😉
On a Phone:
/ > storage > emulated > 0 > games > com.mojang > minecraftWorlds > RandomWorldCode > db > CURRENT (open as a text document)
OR
/ > sdcard > games > com.mojang > minecraftWorlds > RandomWorldCode > db > CURRENT (Open as text document)
On a PC:
C: > Users > YourUsername > Appdata > Local > Packages > Microsoft.MinecraftUWP_8wekyb3d8bbwe > LocalState > games > com.mojang > minecraftWorlds > RandomWorldCode > db > CURRENT (Open as text document)
IMPORTANT: ALWAYS HAVE A BACKUP OF YOUR FAVOURITE WORLDS, IN CASE SOMETHING BAD HAPPENS
migrated
Thanks - this seemed to have worked!!
migrated
Thanks - this seemed to have worked!!
Auldrick
@Kevin: Thank you so much for letting everybody know of the workaround! Not only will it help other people with the same issue, it could very well serve as an important clue to the developers about what's causing this, and possibly certain other problems people have been having with worlds not being saved correctly.
BTW, I believe the CURRENT file is what the game uses to find the manifest from the latest save. After CURRENT is saved, the game can delete the old manifest and obsolete chunk data files because they're not needed any more. The fact that you have many manifest files implies that something is causing saves to fail so that this deletion doesn't happen. One possibility is that you don't have enough free space left for storing the updated world. If so, the problem will probably happen to you again until you free up more space.
Auldrick
@Kevin: Thank you so much for letting everybody know of the workaround! Not only will it help other people with the same issue, it could very well serve as an important clue to the developers about what's causing this, and possibly certain other problems people have been having with worlds not being saved correctly.
BTW, I believe the CURRENT file is what the game uses to find the manifest from the latest save. After CURRENT is saved, the game can delete the old manifest and obsolete chunk data files because they're not needed any more. The fact that you have many manifest files implies that something is causing saves to fail so that this deletion doesn't happen. One possibility is that you don't have enough free space left for storing the updated world. If so, the problem will probably happen to you again until you free up more space.
[Mod] LateLag
I already have a lot of free space, but thanks for letting me know about these things 🙂
[Mod] LateLag
I already have a lot of free space, but thanks for letting me know about these things 🙂
[Mojang] Mega_Spud (Jay)
Could you please upload a copy of the world that is having this issue please?
[Mojang] Mega_Spud (Jay)
Could you please upload a copy of the world that is having this issue please?
[Mod] LateLag