Woodland mansions are a cause of much grief. Mainly due to the fact that if you actually make the 50,000+ block journey to reach one, your Switch file size can reach upwards of 300MB. This makes copying your save file impossible. The Switch will crash and say an “unexpected error” forced the game to close whenever you attempt to copy a file of that size. What’s more, the game play drags and freezes as new areas take an excessive amount of time to load. This also makes Elytra travel almost impossible as you hit an “invisible wall” in mid-air while the next chunk loads but you still lose altitude while stuck there, leading to deaths that are no fault of the player. This is infuriating with such a rare item as Elytra. I’m not sure how to fix the file size issue once you exceed a certain size (I doubt it can be fixed on pre-existing files), but either the ability to turn off auto-save, or reset The End would take some of the sting away from losing rare items that take hundreds of HOURS to acquire, but one freeze or glitch can wipe it all out.
I understand it may be unrealistic to expect a truly “bug-free” Minecraft, but allowing options to mitigate the unintended consequences of these bugs is the LEAST that could be done.
Long story short: Switch file sizes over a certain size (300MB in my particular case) can’t be copied without crashing the game, and tend to lag and freeze constantly while playing.
Disabling auto-save and/or being able to reset The End would be an acceptable temporary work-around to an outright fix of the file size bug.
Comments 5
Not to mention, even tho internal NAND Flash memory can handle upwards of 100,000 read/write cycles, if Minecraft is going to auto-save every 15-30 seconds then people with a 300 hour save file (like myself) will have “saved” anywhere from 36,000-72,000 times! The aggressiveness of auto-save actually creates valid hardware concerns!
@Andre See Not totally agree your opinion since only developer know how Bedlock edition handle the save / autosave with switch API. If simply append that's true. But this is a game which may affect to any block in the minecraft world. The simplest way is dump and compress the in game memory and export to file. So I guess the save may have overwrite possibility.
For my observation, I had always encounter save game then hang issue. After force close the game then reopen, the file size will be reduced. It seems the save may have several copy on single save resource file to prevent any data loss during saving crash. So I guess each save time will write some new data on it, and it is not good for autosave on TLC which may decrease the life of the NAND chip.
Cleaning up old tickets: This ticket has not been updated recently (~1 year+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Yes!! This is exactly what is happening to me! After I made a long trek to a Woodland Mansion, my file size swelled to over 300MB, and now the game won't save no matter what I do (this began almost two years ago and I have essentially been locked out of my world ever since).
I thought the problem was the infamous 'You are out of data storage space and minecraft is unable to save your progress' bug (MCPE-32501), but since that has supposedly been fixed now and my world this must be the problem; the game can't handle worlds of over 300MB big for whatever reason.
Mojang, please get on this! I have seen other people specifically talking about the 300MB issue, it badly needs to be addressed!
I agree 100% with this. Ever since they disabled auto-save on the Switch, the game has gotten heavier and slower to load certain parts of the map. Any means of transportation - minecart, boat, Elytra - end up hitting invisibe walls and every damn time, the auto-save icon is there. And whenever it pops up, the game gets slower and fps drops to 30 around buildings/villages/etc.