mojira.dev
MC-228113

Some world changes don't get saved in some worlds upgraded from 1.16.5 (caused by corrupted/modded world file)

I opened the game and resumed playing like normal. I moved all my items from chests outside my house to inside the house and began expanding the house. I kept hearing a villager but could not see him so I thought he was invisible. I saved and exited the world then rejoined it to see if it was a glitch. All my progress was gone. The items were moved, some things were duplicated while others were completely gone. But the area I had been mining out had stayed except the wooden wall I had cut down to access this area had reappeared. It happens every time I close and reopen the game. I know because I moved the items again and decided to quit but wanted to make sure it saved this time. It did not, I was back at square one. I notice it is as if anything that was made or put in place before the 1.17 update does not get saved if you change it. I tested just breaking a dirt block, exiting the world, reloading the world, and the block was back in place despite the broken block being in my inventory. But blocks I had not touched before 1.17 can be broken, moved, and they save where you leave them. This also applies to the items in the chests, if they were in one chest before the update they will automatically go back to the chest they were in before if you move them and reload the world.

Linked issues

Attachments

Comments

violine1101

We do not have enough information to find the cause of this issue.

Please attach the affected (zipped) world file. If the file size is too large, please upload it somewhere else and then link to it here.

This issue is being temporarily closed as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

migrated

I uploaded it to google drive and will provide a link to it. I am not sure if this method will work but it was the only way I knew since it was too big to upload here. https://drive.google.com/file/d/1ZiyvleDUXrlt_ZD-7Ke6lvg1g-KOM9o0/view?usp=sharing

It might also be worth noting that I used this backup to try and see if it would solve the issue, it did not. But when I loaded a backup from a month ago everything started to work again. I do not know if it was a world file issue or not but I thought any extra information would help.

One last thing, I dont know where it is going to spawn you in the world because I dont know how this works so the coordinates to my main base are -52 / 69 / -824

violine1101

Thanks. Yeah, I can confirm this. This is very concerning.

ampolive

Might relate to MC-216148.

migrated

If you want I can add the game file that worked so it can be compared to the one that doesn't. 

boq

This world was at one point saved with a mod called "Supplementaries". That causes some chunks to not save correctly once mod was removed.

I will just drop that data, but this world will have more issues than that.

slicedlime

World file is modded.

migrated

boq

Confirmed

Very Important

Save Data

1.17

Retrieved