mojira.dev
MCPE-154121

8 year old Minecraft world “out of storage” corruption playstation

Hello, I have an 8 year Minecraft world that I have been building on for so long, now corrupted after the 1.18.30 update. It now says “Out of storage” when loading into the world, but I have plenty of storage and I have also attempted deleted several other worlds, closing and re-entering the application, reinstalling etc. The result is the same. This was an issue for the last two major updates, however the patches from those updates fixed my world, but now I’m having the same similar issue, which seems to happen after every new update… It’s a very sentimental and extensive world, snapshots below… it would be an Absolute shame if I lost this world after I have spent so much effort and love into it. 

 

please fix, or refer this to a ticket with the same issue. Thank you. 

Related issues

MCPE-154134 1 Year Stream world out of storage space after 1.18.30 update MCPE-154469 World does not work and sometimes has texture issues MCPE-154585 Cannot load world. Sometimes I can load in, but everything is pink and black before it crashes after about three seconds. MCPE-154709 World corruption - Same as an already resolved bug MCPE - 149193 MCPE-154874 PS4 worlds over 1gig corrupted after recent update MCPE-154933 After 18.30 my world has been corrupted. MCPE-155093 World won't load MCPE-155248 My game saved progression. MCPE-155638 Update from 4/27/22 Caused world to crash. Now states unloadable MCPE-158126 Login in a world MCPE-159544 Bedrock No storage Glitch when Having plenty Storage MCPE-159671 Bedrock no storage glitch MCPE-160644 "There was a problem loading this world, You are out of data storage space and Minecraft will return you to the main menu to clear up storage space" MCPE-160753 Impossible play MCPE-161425 Not enough storage but i clearly have enough . MCPE-161646 Game crashed mid travel with my brother MCPE-162983 Not enough storage MCPE-163569 Worlds won't save when file size approaches 1gb (953.1mb). Receiving error that there is not enough storage space. MCPE-164233 Corrupted World MCPE-172368 Game crashes when loading save file and out of storage messages on Playstation 4 MCPE-172581 1.20.1 not compatible with large older worlds? MCPE-175086 Loading failure for a world over 1000 MB on Playstation MCPE-176959 latest update 2.67 causes a loaded world to become corrupt after saving

Attachments

Comments

migrated
[media][media][media][media][media][media][media][media][media][media][media]
migrated

Also Having the same issue with a 1 year world. Had the same bug when 1.18 released

migrated

The last issue I had was from this ticket 

  1. MCPE-149193

however, after the hotfix.. it fixed my world. This bug that I have now, is saying I’m “out of storage” any other copies of my world will say the same thing, and it happened right after the 1.18.30 update on PlayStation. 

migrated

Same issue, really frustrated so much time invested into my world… and just like that, can’t load because of an update.

migrated

Do we have an update on this yet? Apparently it’s not just PlayStation, looks like Windows is having a major issue as well with similar problems.. it’s a bedrock issue, needs a new Hotfix, mainly a storage issue.. it’s because Bedrock is capped, has to be a way to fix this, so many people are loosing there older and larger worlds.  

migrated

Also having this issue with a world created as 1.18 came out, where all my textures were replaced by the purple and black no textures block or the dirt with green text, and then occasionally the world was just not accessible. also on PS5

[Mod] OcelotOnesie

@unknown: Thank you for providing the world. I've made your comment visible to moderators and Mojang only and set the security level of this ticket back to public so other users can view the ticket.

migrated

Ok, thanks for making it available to the moderators and reopening it back to public. 

migrated

Just checking back if they have a fix for this yet?, 1.18.31 still doesn’t work, I heard one of my friends is having the same issue with there 2 year old large PlayStation world, but they don’t know how to submit a ticket. I guess it’s affecting quite a bit of people with large worlds on PlayStation Bedrock.

migrated

Any updates on this yet? I’ve been able to reload my same copy with the new terrain generated and I didn’t have any crashes but that was days ago and I haven’t looked in a while 

migrated

Do we have any updates with this by chance?

migrated

It has been just about three weeks if not more now and still no updates or progress? I understand with 1.19 just about ready Mojang needs all hands on deck but several of us won’t be able to play it. Please get this fixed

migrated

@IsaacGenest, agree it’s been awhile, from my understanding, I believe Mojang releases patch fixes and updates on Thursday’s last week Android had an update, and before that it was Bedrock.. which did not fix Playstation worlds, and it also didn’t fix many other worlds either. Both on PC and Xbox. I know several friends around me having the same issue as me. Hopefully by Thursday we will get an update and fix for this on Bedrock. Fingers crossed. 

migrated

I have this same issue on my test build creative world on xbox bedrock (1.18.31) with the file size at 1.1 GB and it was working fine before the update/patch to fix the furnace xp glitch. I think its now corrupted as well cause it wont load I get no error code it just crashes my game and end up on xbox one s home screen! Worked fine before that update/patch! I am not sure if this will help but during update that gave me 1.18.31 I saw my tv screen showing me this in the 2 pictures provided. https://www.xbox.com/play/media/Z6BH68UW screen pic when update was taking place next pic was after update aka main menu screen https://www.xbox.com/play/media/SFEUZEGG

migrated

Why do we not have a fix for this on PlayStation yet. It’s been 3 and half, almost 4 weeks… I lost my Minecraft world due to an update… that’s sad. 

migrated

Are there any updates with this by chance? Still corrupted from the update, just won’t load. 

[Mod] OcelotOnesie

Unfortunately, I don't have any updates to share.

migrated

Is the issue being worked on though, cause it’s been quite a while without updates or any visible sign of the problem being worked on

[Mod] OcelotOnesie

This ticket has an ADO number, which means that the issue has been reported to Mojang's internal bug tracker. I don't know if they are working on the issue right now though, because I don't have access to their internal bug tracker.

migrated

Oh ok I see, well hopefully we have one soon, maybe before or with the 1.19 update. I’ve been eager to play on my world, I miss building on it. I’d just be sad if they decide not to fix the issue after 8 years of building on it.  

migrated

Agreed hopefully it gets fixed as it was the basis for my strea. And i had alot of really large builds im proud of and wouldnt want to lose.

migrated

Me as well. I have so many large builds and cities all over that world. I tried loading back in, it just shows those purple and black blocks. I got it to load in once before it corrupted again, most the time it says “disconnected due to corruption” or it says “problem loading this world” I had this issue when caves and cliffs part 2 released, the hotfix had fixed my world afterwards with no issues, than I had it again with this recent update. .30 and .31 , I guess .31 had fixed issues with the switch and pc. But Bedrock is still down, PlayStation and some Xbox worlds are still corrupted because of it. I’m hoping we have the fix with this next update for Bedrock. 

migrated

I’ve been waiting for a month.. my world is still corrupted.. will they ever fix this?

migrated

Having the same issue.. it won’t load in on PlayStation. I’m on the latest bedrock update. I’ve had it ever since the update. Please fix this. I have a lot of hard work and progress on my world. 

migrated

I have same issue on PS4... No worlds over 900MB will load without disconnecting due to "lack of memory" or "world corruption"... Been going on too long, in my opinion

migrated

I believe this issue is a duplicate and should be linked to the master bug tracker ID MCPE-55010.  There are a lot of linked/duplicate reports on this issue which has watered down the true scope of exactly how many players are impacted by this. Thank you.

migrated

Still no fix??? Come on man 1.19 is just around the corner. Please fix this horrendous bug. I wanted to play 1.19 on my world that I’ve been building on for forever.

migrated

Ok so as far as I know, (maybe this isn’t the case) but isn’t it that usually when there are large game breaking bugs, the devs are usually on top of it and are constantly trying to fix the worst bugs. It has been six weeks and the Wild Update is next Tuesday. How has there been no updates or responses to anything people have said. We have been waiting to play our worlds after a larger break in the game and we have been put at the bottom of a list regardless of the importance of our issue. This isn’t the first time this issue has happened and it probably won’t be the last I imagine. Please Mojang, we are all anxiously waiting to get back into our larger worlds and hopefully be able to play and prepare for the Wild Update. Please provide us with at least some news as we have heard nothing. Thank you.

migrated

Well hopefully this will be fixed alongside the 1.19 update, fingers crossed.

migrated

Updates on this? 1.19 comes out tomorrow…

migrated

Mojang what’s going on, why have we been left in the dark and left behind. The Wild update is today and none of us can experience it in our favourite worlds, we have had no news, updates or responses from mods or developers. This has been a bit of a let down and I hope this gets fixed by the end of this week since there is no more Wild update preparing you should be able to focus attention on these issues. Thank you.

migrated

My world is still not fixed. I thought for sure 1.19 would have hotfixes.

migrated

Elijah, have you tried making a copy of your world, exploring new terrain and the leaving and reloading the world. I just tried that by making a back up of my survival and I went to the new swamps and came back then went back to the swamp again. All while leaving and seeing if I crash or go to purple cubes. Try it maybe and see what happens, is working for me but I am still cautious.

migrated

sometimes, but it’s still corrupts here and there.

NeoCyania

Is this a console only bug? Have you tried exporting the world somehow to play it on pc or a phone and see if it works there? I've been playing large and old worlds for years on pc/phone and never had this bug happen. Also always keep external backups of important worlds that are not saved on the console. 

migrated

NeoCyania, thanks for the comment, I do have backups, it seems to be a console only bug right now, my world has been working on and off after 1.19. Sometimes it’s fine, other times it’s not. 

and unfortunately no, I cannot transfer the world, I’ve been wanting to transfer it to PC for years but am unable to because PlayStation Worlds are locked.. the only way to transfer that I am aware of is through realms, however, I have the “account linked” bug for PlayStation and Microsoft, I’m unable to sign in online and haven’t been able to since bedrock came out on PS4 back in December 2019, I’ve reached out to Mojang and Microsoft many times, as well as PlayStation with no help. 

It’s just been a constant battle for me.  

migrated

To raise awareness on this, my understanding was this was a Bedrock code based issue affecting multiple platforms not just consoles. Refer to MCPE-55010 for details as I believe there are reports on Windows as well. The commonality among reports is that the impacted World size has become "too large", usually over 500MB. This affected my world starting when it became 900GB in size. Given how long this issue has been open with no attention or movement, I'm not sure this can or will be fixed unfortunately. 

NeoCyania

The reports have a bunch of votes tho so other people have the same issue. It is strange that this hasn't gotten any real attention yet as it breaks your worlds and all the amazing progress gets lost. I wish you guys good luck that this issue gets resolved eventually or that you find any other way to export the worlds to a different device. Maybe try creating a new account and the realm thing might work again?

migrated

I just think its a serious issue in a game thats all about building and exploring and if im streaming my current world its going to corrupt sooner or later especially since the new update has even more data to drive up the file size. It NEEDS to be fixed!

NeoCyania

Some ideas that could temporarily help:

  • try to clear Minecrafts cache, it can fill up over time with random stuff and take up many gigs of storage (look up how to do it if you don't know how)

  • backup your worlds and completely reinstall the game

  • get the world on a pc and edit/prune unwanted chunks to reduce the world file size (with Amulet editor or Chunker app)

  • to avoid getting a big file size in the first place don't explore too much and don't create many maps (definitely turn off the option that gives new players maps because maps create a huge amount of data junk in the world file that can only be removed with external programs)

OpaqueSleet7802

I looked at the duplicates and clones and it looks like they all say PlayStation. I think this bug only affects PlayStation players.

migrated

This bug affects the Bedrock version of the game, this specific bug report (MCPE-154121) tracks issue reports for Playstation, but this issue affects multiple platforms. See MCPE-55010 - confirmed on multiple platforms.  Same issue. MCPE-55010

migrated

The bug came back with the "hot fix " i was playing and it crashed my world and gave me the same message "out of storage " and it only appears when a new update is out  ( caves and cliffs part 2 and the wild update "hot fix")  it was fixed before so hopefully it will get fixed again 

migrated

Is this getting fixed yes or no? Why is my report put as "resolved " when its clearly not ?! Your bot said that its a duplicate when the version that's being effected is the hot fix not 18. Ect smh! Its 19.2.21 !!!! Ill ne waiting for a reply from a mod because i need confirmation that its being looked at and finding a solution 

migrated

 This getting fixed YES OR NO? This is ridiculous mojang!

migrated

I am having the same issue. started happening yesterday. I'm on PlayStation. I get the out of data storage message for one world 923mb in size. It the only world i have. Why limit our storage size?

migrated

Mojang! Is this issue being looked at? I dont want to play on my world anymore because of this ridiculous bug that's extremely game breaking and i don't want to lose my world.  At least say something that this issue is being looked at smh!!!!

migrated

this is getting ridiculous. After the most recent patch for PlayStation, my world is once again corrupted “failed to load world due to storage” I HAVE SO much storage?????????? And the backup won’t work, And it’s not with just my main world. It’s also with several others now that only have like 100mb if that ….. like seriously? 

this game needs updating.. there should be sole focus on an advanced technical update. Not to mention, Minecraft is way behind schedule. It’s 2022.. and the game doesn’t even compare to most games now.

 

come on now. I know it can be better. 

migrated

I swear to god im done with mojang and bedrock you people are so careless this bug has been going on for months and was an issue for more then a year! And its not even a small harmless bug it literally a game breaking bug that destroys worlds knowing the console has plenty of storage!

migrated

The game is unplayable as im typing this this is ridiculous! I can't even open a copy of my world what are yall doing in that office?? 😤 

migrated

Game is unplayable on my world. This only affects worlds approaching 1gb (953.1MB).

Might as well just forget about bedrock and start playing on Java.

migrated

(Unassigned)

776529

Community Consensus

PlayStation

1.18.30, 1.18.31, 1.19.0, 1.19.2 Hotfix, 1.19.10, ..., 1.19.41, 1.20.1 Hotfix, 1.20.15 Hotfix, 1.20.30, 1.20.41 Hotfix

Retrieved