Chunks reset and missing in ticking area on Minecraft World

We have two Bedrock Edition servers and one of them has started experiencing the same issue. First we had multiple chunks that loaded and you could see hitboxes but you couldn't access anything. Trying to move items with pistons would crash the server. We installed a backup copy and thought everything was ok but now we have new chunks that have completely disappeared and some that have reset back to first generation. Server is version 1.14.0.9

Loading the backup file we used in UME you can see where an entire strip of the world has been removed. States no chunk found but there was a giant build in this exact chunk just hours before. The one lone chunk that does show in that strip is the chunk that is now completely missing.

*Reply from [~Auldrick]:*

Blank stripes in the map in UME (Universal Minecraft Editor) are the result of a bug in UME. I've been seeing that in large worlds for years. Sometimes you can make the stripes fill in by over-scrolling past them and coming back.

In general, if you find something that looks like a bug in a third-party tool like UME or MCC Toolchest PE, please verify it in Minecraft and use the latter when reporting it as a bug. Mojang does not use such tools and can't tell whether it's a bug in the tool or in Minecraft, so they have to ignore evidence that comes from a tool.

I'm removing the unusable screenshots from this comment and the next one, but will leave them as attachments in case you need them.

We have also discovered a reset in the nether as well which led me to see that the reset is happening in the same location(s) in all three dimensions. We now have at least two separate strips that have went missing and it is always along the Z axis. 

1-16-2020 Update...

We restarted the server on new hardware using the original 1.13 world and the latest Bedrock server software. Everything was fine for about a week and then the same problems started happening again. First chests that could not be accessed and then random chunk regeneration. 

Our second Bedrock server (Also 1.14) which has been running fine since July and is housed on completely separate hardware is now seeing the same problems including inaccessible chests and chunk regeneration.

This is a MASSIVE issue on realms, and does not appear to be tied to ticking areas. At least not from my experience with it.

These corruption lines appear to go from the very bottom of the map, all the way to the top, and reset/corrupt everything in their path. You can fix this issue using world edit to copy/paste the chunks, but it takes ages. Depending on when you notice the corruption lines, you might have to revert to a save that is days old.

We did try replacing using world edit but our experience was that once we were back online a new area would appear within the first 24 hours. Once this bug has you it holds on tight!

If you have a copy of the world available, you might like to upload a copy of it for investigation.

• On Windows 10 you can use the Export world feature.

• On Android or iOS you need to use a file explorer to navigate to Device storage > games > com.mojang > minecraftWorlds

• On Xbox or Switch the only way is to upload it to a Realm, and then download the world on Windows 10 or Android/iOS. (Please do not purchase a Realms subscription just to provide a world to us - but if you have a Realm already this may be a viable option if you wish to do so.)

If the world is larger than 10MB you can upload the world to OneDrive or a similar file sharing site, and then share the link.

@Mega_Spud The world is large but I will get you downloadable files asap.

@Auldrick I understand your point but in our case those strips are actually messed up in the world prior to loading in UME,

Affects 1.14.1 and 1.14.2 as well

not sure if this will help but if i go to the same coordinates in the nether the nether chunks reset as well

Affects 1.14.3. This bug needs to be elevated to a much higher priority due to the fact that this is erasing huge amounts of players progress. This bug affects players in one of the most negative ways possible since it is deleting things that players have put hours upon hours of time into.

My world just started to fall apart today. There were large areas that were covered in holes straight through bedrock where chunks did not load. As soon as i noticed them I logged out and made a copy of my world. This is the link for my world.

https://drive.google.com/open?id=1eRoVRItnms2bR3RDHVE14ZzDNRsAVB4f

I found this in a normal survival world in beta 1.16.0.53, meaning it’s not restricted to realms.... 

Still affects 1.16.0.55 beta. My entire desert village disappeared after a game crash with massive chunk errors. Couldn't use a world editor to delete and replace those chunks using an old world backup

my person survival world got 19  of these lines going from the beginning of the world to the end. It is not even a visual bug like how it was on MC ( Jarver). I lost my ender dragon armour and my whither armour . it was unplayable also reset lines are a BAD . May I just humbly ask how this got in-game  

found some chunks just getting deleted down to void

Boy have I found a big one...

bug is exist in the newest beta, I was going to use the block blocktopography app to see how many moves were in between me and my home and I saw that the chunks had gotten deleted, my whole village and my nether portal were just erased

This happened to me in my Xbox world and I linked pictures to it in this. But I guess my question is, is it still safe to play in the world after this happened? I stopped playing in the world with this problem out of fear it would be irreversible if I played on it before the bug was fixed.. So if I play on it and the bug gets fixed will my world get fixed? Or would it not because I kept playing on it 

It happened to me on an Xbox one superflat world in beta 1.16.0.57, where the chunks went missing or got reset, meaning builds were destroyed completely

Happens on MCPE...seems like every time I close/reopen another chunk disappears. Can only have one active Realm at a time, so months of work down the drain...

Also affected by completely missing chunk on latest PS4 release. Not even any Bedrock so a nice hole to leap out if the world. The missing chunk should be in a village if that helps.

Just had this happen on my Xbox world. Logged into another console and it had reset my world to when I just put up the house. I lost farms railroads and not to mention loot. When I logged back into the original console all that is gone but now half my chests are too and yet some elements like the carpet that I found later on is there. Basically have to delete the world and start over. Again. 

Same here.. I'm currently using 1.16.0.59 Beta
I feel bad about all my stuffs, I hope some fix will spank this bug right in the face in the next future updates.. God bless Mojang! ✊

In my world several craters were made that literally have no bottom, one of them was in the middle of my house, everything was lost, other things disappeared, I closed and opened it several times and I did not know fix,

It appears that this bug occurs during game crashing. This happened in my world 2 times and they both were from game crashes. 

Use blottopograh, "an app" and select the missing chunks, then delete them, this will reset everything you selected and will make it a new chunk and will load in

Similar issue

same exact thing happened to me, a ton of progress from quarantine instantly gone.

Same here happend with my i lost 5 monht's of progress at once when i looked in to the game file there was an extra fille added called ''corruption''

the bug only took the parts that i and my friend worked hard on, im not sure if i should start again a world

so this thing happened to my world today, deleting almost all buildings and deleting everything 

this kind of bugs ruins the gameplay and its demotivating,I take backup on regularly, I got lucky take backups !!!

That is biggest problems in minecraft

For those still affected, could you please mention whether this is happening in a Realm, 1.14.60 local world, or in the beta version.

It would also be very helpful if you could upload a copy of your world save to a file sharing site and share the link here.

Hi spud, thanks for investigating! Here is a folder containing both the bugged, and the backed up world (from the original bug report). Hopefully these can be of help to you!

https://drive.google.com/drive/folders/16oqfhomml4opVs_rCtk2B0Dg0wiB6E2P?usp=sharing

If the link ever somehow expires and you need the files again, let me know, I'll keep both world versions on my hard disk.

https://drive.google.com/drive/folders/1VAaJgozUFa9m3thwydrzgxQew8diX4oG?usp=sharing

This is a link to my world, where I also have chunks missing.

[Minecraft] Mega_Spud (Jay Wells), it happened to me on minecraft dedicated

This happened recently with my cousin, he is very sad the version that this problem occurred is 1.16.0.64.

This is actually a really old bug. It happened to me once on my main world (+550mb) near spawn, and never experienced the bug anywhere else.

I heard it was a thing for worlds greater than 300mb in size

Is this happening in 1.16? It’s listed as fixed, just wondering.

confirmed for 1.16, this still happens :c

This just happened to my world is there a way to fix it? On bedrock pc

This happened on our realm today. We have an active realm with multiple players. We've been playing on 1.16 since it updated. I logged in on XBox to an empty rectangular section directly in front of me where I had been building with redstone previously. I jumped in to investigate and it began killing me. I was unable to break or place blocks to get out and died. On respawning, I was still in the hole with no gear, and once I moved, I began dying again. I reloaded a backed up version and the hole hasn't appeared and there have been no other problems so far.

Still happening as of 1.16 I have video to prove that... https://youtu.be/-MkmG58hVxM

Please fix this!

My world is a realm and 1.1gb if that matters

No matter what backup I have the same holes appear in my world despite them not being there in the update before... And its not like I didn't notice as the chunks missing go on for a freaking absurd 25000 blocks and the thing is 300 blocks wide....

Can someone link me some information that I can use to at least reset my missing chunks? I want to play in my world but it's missing multiple chunks (over 10) chunks around my base and I cant build any like that. I play on bedrock windows 10

My realm is more than 1g and i have only had it happen once other then that just random holes everywhere in the nether.

At least its a good way to find some diamonds 🙂

(assuming you don't have enough when your world is 1g)

Still occurring for me as of 1.16.1 

It's the same exact corruption every time... And it wasn't there when the game was in 1.14...

Can confirm bug still happens in 1.16.1, my realm randomly crashed and reloaded a save from like 30 minutes before

https://www.youtube.com/watch?v=WdImZ7ECROI

Another video of just a small piece of the 25k block long corruption in my world... Im so sad to see my world like this..... Also what software everyone is using to the extent of their corruption?

This happened to my brother and I on 1.16 and 1.16.1. Luckily we both keep backups of our worlds. Ive attached copies of both worlds (world 1 and world 2). Screenshots are of world 1. I tried various devices (iOS and Android). All produced the same results. The world type did not matter. Some corruptions were worse than others. When I removed everything but the level.dat, there did not seem to be any corruption.

Note: The corruption occurred on LOCAL WORLDS. I do not use realms as of yet.

Hey yeah so this happened on my Realm. How do I fix it? I have a bunch of backups but should I just wait for a fix to reopen the Realm on a backup that hasn't loaded the corrupted chunks yet? This is the first time I've had this happen so idk what to do and my world is 3.9 GB. 

I reopened my Realm on a backup that hadn't corrupted yet, the corruption didn't occur again after that.

(Question for a minecraft dev) Was there a leveldb format update for 1.14 that might have been buggy? Did DataFixerUpper do its job properly? Would those cause the missing chunk issue?

To help the devs out can anyone confirm whether any LOCAL worlds created with Minecraft version 1.16.1 corrupt themselves. If that is not an issue, I suspect the datafixerupper is at fault as 1.14 introduced a new mob (bees).

I do not claim to know anything about the inner workings of minecraft. These are just educated guesses.

I'm having this same issue.  I played PE on my old tablet for a few years until I got a phone, which I then transferred those worlds to my new phone and deleted Minecraft on my old tablet.  Well this was a mistake, since when I tried to open one of the old worlds from my tablet, they had this same issue.  All of the worlds but one had missing chunks, and only one of the worlds that had missing chunks actually had a trace of any of the builds I had done.  All the rest's missing chunks were any of the chunks I had interacted with (breaking or placing blocks/items).  If there is a way to recover this without the original device, that would be great.

Update:  I tried doing the same thing with another device and this time the missing chunks were all the chunks bordering the chunks I had previously loaded, so this time I kept my builds, but there's a massive chasm with void at the bottom surrounding the entire thing.

I have provided two copies of my world for investigation on this corruption issue. One is before the corruption and one is after the corruption. The first link is the world before chunks got deleted and the second link is the world after chunks got deleted. 

If you do not end up at the desert village island where the corruption is, head to about x=650 y=-250

Before chunks got deleted. (January 2020 Backup)

https://drive.google.com/file/d/13GAIAMNghE7N2vG3FTaidXBpSS5QINC7/view?usp=sharing

After chunks got deleted. (July 2020 Backup)

https://drive.google.com/file/d/1uLpotkIXxj_9811BGN0cZ1H7T-OuL2yn/view?usp=sharing

You do not need to be in the beta to load the second world as the that world was loaded in 1.16.1

EDIT: The first link was the same as the second link. I changed it so the world before corruption should be downloadable. 

At least give us the ability to enable backups in case this happens, It gets annoying to constantly make copies..

Here are the game world files from our server. This server has never been upgraded past 1.14

Day one (No curruption)

https://adultscraft.com/downloads/tb.mcworld

A few months later with multiple areas of curruption.

https://adultscraft.com/downloads/doomsday.mcworld 

Similar bugs are occurring with older worlds that have not been loaded since pre-2018. Those are being tracked at MCPE-87503 and MCPE-85039.

Hope this helps the devs, I've been able to answer a few of these questions.

It appears it happens to all chunks that have not been loaded since ~2018. This bug did not exist (to my knowledge) at all in 1.14.60.

The problem is much much worse for worlds that are pre-0.9.0. The world takes around 10 minutes or more to load before loading a world with no chunks whatsoever. Trying to make the world infinite crashes the game immediately, and the game only manages to rename the broken world to [world name]-old, created a new folder called [world name], then crashed.

The corruptons can happen to worlds of any size from what I've seen. I've seen it happen on Old style worlds, superflat, and infinite worlds ranging in size from barely over 0MB to more than 200 MB.

The best solution to the problem I have seen for players is to, using a backup of your world (or a copy) from before the corruption, either by:

A) Use an external program (such as MCC Tool Chest) to convert the world to Java Edition, then convert it back to bedrock. This will erase anything in chests, may glitch doors, glass panes, and will remove any exclusive blocks to bedrock, like old stonecutters and nether reactor cores, but at least you'll have the world. Keep the original version for when they fix the bug.

B) Open the world on a device with an older version (1.11 worked for me) and load in all the chunks on your world that you don't want to be corrupt. Then it should be safe to open on the modern version. Make a backup though just in case. You would need to have an old device that's been offline for a while though.

Unfortunately, if you're on console, I'm not aware of any way to do this. If you do have a copy of the world, DO NOT LOAD IT. As long as you keep the world unloaded, it should preserve the files, and the world will work when this is fixed.

As for 1.16 local worlds being affected by this issue, I don't know. I haven't seen any, but I'm not sure that none exist. I haven't personally made many worlds since then, most of my worlds are much older.

Quick edit/update. It does not only happen in older worlds. It can happen in more recent worlds also. It just isn't guaranteed.

@MemoGoodNameYes I think what you're experiencing might be something different then. The world in which this bug occurred for me, was only created in 2019, only 6 months prior to me reporting this bug.

Does this happen in 1.16.20.53 beta? They have tried to fix it again. I hope it was sucessful so I can play without chunk corruption.

I made world maps back in 0.10.4-0.16 days and ever since the 1.16 updates, every time I redownload the copies of my old maps, they are all broken. I'm on 1.16.10 and iOS 13.1.3

@memogoodnameyes its not only in older versions, it happened in 2020 to my world in 1.16 as well.  the bug is really frustrating because all your hard work goes to waste.

Idk why mojang won't address this issue. I brought it up last October when it started, and again a few months later, but they have just continually given me the run-around with zero attempt at a solution (see MCPE-60952 that I created).

I have many examples, and they all look similar to the screenshots you guys have attached here. And yes, the worlds are all completely vanilla.

What I do know is this:

1. The worlds work fine in MCPE versions prior to v1.14.1

2. Sideload an older version version of MCPE and you're off and running

3. Or, open the world in Windows Bedrock (any version including v1.16.10) and all works fine

4. Yes, the above only works if you were lucky enough to have saved the ....MinecraftWorlds\blaHbLAhblAH folder before the bug corrupted it in October.

5. I've tried transferring the working world from Windows Bedrock over to MCPE, but the bug destroys things back to about 1/3 default terrain, 1/3 missing chunks, and 1/3 remnants of the developed world

So, since mojang isn't offerring any kind of recognition or resolution to this specific bug, I propose posting a different question, which is....

Devs, if we have a world that works fine in Windows Bedrock v1.16.10 and MCPE prior to v1.14.1, but anything after MCPE v1.14.1 destroys the world, how do we transfer our currently working world over to MCPE v1.16.10 or higher?

 Thank you for your time...

Are there people still experiencing this issue in 1.16.20.5x Betas?

What happened to me:

When I placed a block in the chunk it sort of just came back.

This can be resolved now. I have not had it happen in 1.16.2.

How did you resolve it?

This is still happening in version 1.16.2 just checked my realm and we still have a giant line on chunk errors going through our Nether idk what to do.

@Ellis this will prevent further chunk errors. Any that happened before will not be fixed as i heard that is not possible. If it happened before then the error the missing chunks will still be missing. I'd recommend to restore from a backup where the chunks were still normal.

All of my backups from 1.16.1 all have the same chunk errors in the Nether though. So should we just keep playing on the world even though there's a giant line of new chunks going across my Nether highway since the chunk errors won't reach out further/spread?

This is how we found it. We walked across the Nether highway and stopped at a base to save and quit for the night. The next morning we all hopped back on and started to take the highway back only to find a giant line of chunk errors was blocking our way back home. Now any backup that I try has these new chuck errors. If it isn't going to spread further then wouldn't it be okay to keep playing on it on 1.16.2?

It should be okay. This fix should prevent further issues, if you find new corruption lines, let the mods know about the new corruption you know appeared in your world, so then when this gets closed, they will know it is still there and reopen the ticket.

This still happens after opening backups that haven't been opened since 2017.

I cannot reproduce, i opened a world from 1.0 and the chunks were still there.

That happened to my brother when he joined my world but i saw he chunks he was on android 1.16.1

 So I should come back here if I start to see new corruption then? My world is about to be 4GB and I've had it for a little over 5 years. Idk how long the corrupted chunks are but I'll be back here if we notice any new corruption I guess.

Worked fine on 2016 world. Unfortunately on worlds with existing chunk errors there is no easy fix, unless you go to a backup.

However, loading a world from June 2014, it is taking forever to load (20 mins so far). After about another 5 mins i force closed Minecraft and started it back up. The world loaded after 5 minutes on the second try, with no corruption issues. So I believe the problem is mostly solved, but it still took a very long time to load that.

Does this affect 1.16.2?

My world is definitely corrupt just went to the end and it looks like a checker board. It started in the Nether when 1.16.1 came out now it's spread all over the place. Idk what to do about it.  All backups before I found the corrupted chunks now have them. Realms backups is the same thing.

Should this have its affected version updated? Or is this a dead report?

I don't know my realms main survival world is still being eaten by world corruption 

Try replacing the chunks. If you can do so.

It seems the chunks have been fixed on my world... Thank you for fixing this one this made me very sad to see.. I will return if I have found any more issues

If you open your world that was already corrupt and expect it to be fixed, it won't... You need to load a backup from before the corruption happened...

In my case my 1.16.1 world is still corrupted in 1.16.2 and non fixable... But my 1.14 backup loaded onto 1.16.2 lacks the 25k block long void that has been plaguing me...

I cannot be sure about this one. There is a new duplicate, but i do not know if that happened in 1.16.20 or if it existed for a long time and was just reported. Nevermind, the person had it happen before 1.16.20.

It appears the bot says it is not fixed. Meaning we may not see a fix for a long while, being a lot of updates.

The bot simply adds affected versions from duplicate reports. It is run by the bug tracker volunteers and does not represent Mojang's response to the report.

In this case, the bot added 1.16.20 because MCPE-97140 was linked as a duplicate. However, that ticket contains very little information, not enough to be sure it's really the same bug. I have therefore removed 1.16.20 from the affected versions.

Oh, okay. Sorry.

Reopen please, bug has reappeared in 1.16.4.

I've checked some of my old worlds and haven't seen this issue personally in 1.16.40, what version are you on?

The fix won't put back chunks that have already been deleted.

Edit: I think there is still some issue here, very old worlds (unopened since July '14) are still taking a long time to open and save, but the issue is definitely more minor than before.

This bug was never actually fixed. Multiple people have been telling me about this issue in their worlds every update. Its maybe less common now, but still very much happens. The report should be reopened, or otherwise still looked into.

Oct 17th, 2020: New Problem with Missing Land areas.

I no longer have a main floor and can't leave my house because it is over a big area of missing ground.

Please update the status of this problem. It's currently NOT resolved.

Please help us as we help you! Thank you for your time!

We are tracking new instances of this issue in MCPE-98789, so if you have further information about how to reproduce it, beyond that it happens to you, please add it to that ticket.

Please do not add further comments to this ticket.

this bug is back, it just reset a large area of a server i play on. may be a world size issue.

Bilbo6756: please create a new report for your issue. We do not reopen fixed reports after the fix has made it into a release version.