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. 

Linked issues

MCPE-154134 1 Year Stream world out of storage space after 1.18.30 update Resolved MCPE-154469 World does not work and sometimes has texture issues Resolved MCPE-154585 Cannot load world. Sometimes I can load in, but everything is pink and black before it crashes after about three seconds. Resolved MCPE-154709 World corruption - Same as an already resolved bug MCPE - 149193 Resolved MCPE-154874 PS4 worlds over 1gig corrupted after recent update Resolved

Attachments

Comments 50

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

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. 

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

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.  

Brodieplayzstuff

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

40 more comments
Eduardo Ramirez

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!!!!

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. 

Eduardo Ramirez

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!

Eduardo Ramirez

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?? 😤 

Tylercolasuonno

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.

Elijah

(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