Upon upgrading my 1.17.1 world, chests and shulker boxes in a specific area are all invisible. All (invisible) chests and (visible) barrels are entirely empty. This only happens within a specific area, other areas seem unaffected. I have gone back and forth several times and also back in time to older backups of the world, and it happens consistently.
Upgrading any world doesn't actually ask me whether I do want to upgrade - it just loads up the world, and afterwards in the world selection it does show 1.18 instead of 1.17.1. Shouldn't I be warned about the version change?
This seems related if not identical to MC-242731. Note that this only happens when loading up this 1.17.1 server backup directly into 1.18 without first loading it into a 1.17.1 local version of the game (see first comment).
For reproduction, here a wall of barrels can be found which all became empty, as well as a chest in front of it invisible:
World: http://www.airblader.de/world.zip
Coordinates: 200 / 64 / 454
I tried running Optimize World before opening it to no avail.
Attachments
Comments 7
I just encountered the same issue. Loading a copy of the world in 1.17.1 locally works, but loading another copy of the world in 1.18.1 locally breaks.
I've tried these steps:
Load original 1.17 world on 1.18 server, join, chests are empty.
Load original 1.17 world on 1.17 client, open, chests are full.
Load original 1.17 world on 1.18 client, open, chests are empty.
Load original 1.17 world on 1.17 client, open, observe chests, save and quit, open in 1.18 client, chests are empty.
Additionally, it appears that all Block Entities are removed since signs, hoppers, etc. are also blank where there are empty chests.
I can reproduce the issue with a single region file:
[media]. Add this region to a world and run `/execute in minecraft:overworld run tp @s -1533.11 71.00 -133.02 236.73 11.40` to go to the location.
I believe the issue manifests when a TileEntity with a non-vanilla ID is included in the list. Because in Schema2842 the DataFixer only reads types of DSL.list(TypeReferences.BLOCK_ENTITY.in(schema)) and the non-vanilla ID isn't considered a "BLOCK_ENTITY" so the type doesn't match. This deletes the data instead of throwing an error because the field is marked as optional.
I've had the same exact issue with my 1.17 world upgrading to 1.18.1.
It's the same configuration than here, a wall of chests with item frames on front.
I have 16 rows of chests, of those only 14 have the issue the 2 rows on the left are ok. In the same room on the other side all the chests are ok.
I use MultiMC and had a save of the old 1.17 world, I re-upgraded it to 1.18.1 and even used the ingame function to optimize it before loading it but the exact same chests are bugged.
This issue is related to MC-241670
This looks very similar to MC-242859 which was supposedly fixed in 1.18-rc3.
I've also attached screenshots, once in 1.17.1 and once in 1.18.
In doing so, something odd happened: if I open the world once in 1.17.1, fly over there, log out and then open it in 1.18, it works fine. But if I open the copy directly in 1.18, it is broken.
Edit: It seems that opening the world once locally in 1.17.1 before opening it in 1.18 does fix it, regardless of flying to the location (at my log-in location those chunks are loaded, though).
Edit: Yeah, I now was able to fix the world on my actual server by opening it once locally in 1.17.1, then 1.18 and then uploading it back to the server. I'll leave this open anyway since the example can reproduce the issue.