Chunks that haven't been explored since 1.13 are resetting
I run a server with a 20k by 20k block custom world. It was created in 1.13.2, but some areas haven't been explored since. Those areas are bugging out, and around 20% of chunks in them are being reset back to vanilla chunks.
I started noticing this bug in 20w17a, however, it may have been going on for longer. I see that in that snapshot's changelog, something was changed about how blocks are stored.
I've attached a glitched region file - I would recommend opening it in a new world, preferably superflat so you can see which areas are reset (and which ones are terrain that was reset on my server)
[03:00:37] [Server thread/ERROR]: Couldn't load chunk [639, 36] java.lang.NullPointerException: null [03:00:37] [Server thread/ERROR]: Couldn't load chunk [639, 37] java.lang.NullPointerException: null [03:00:37] [Server thread/ERROR]: Couldn't load chunk [639, 38] java.lang.NullPointerException: null [03:00:37] [Server thread/ERROR]: Couldn't load chunk [638, 40] java.lang.NullPointerException: null
Note: No stacktraces are logged, possibly because the wrong logging methods are called (last parameter is Object and not Throwable)? The class logging this is called yf in 20w18a (Mojang name: net.minecraft.server.level.ChunkMap).
Environment
Server hardware is [intel i9-9900k 4.7ghz 16gb ram], running on linux.
It has a lot of custom datapacks, however even without those the glitch occurs. I don't believe datapacks are capable of resetting chunks either.
Linked Issues
relates to4
MC-161823Chunks can occasionally be misplaced upon loading a world
ImportantMC-181511Chunks with redstone are removedFixedMC-181270Trying to open old worlds (in Region format?) without version information in snapshots does not show warning screenFixedMC-18251415 Block States per SubChunk Limit during World Upgrade Fixed
Created Issue:
Chunks that haven't been explored since 1.13 are resetting.
I run a server with a 20k by 20k block custom world. It was created in 1.13.2, but some areas haven't been explored since. Those areas are bugging out, and around 20% of chunks in them are being reset back to vanilla chunks.
I started noticing this bug in 20w17a, however, it may have been going on for longer. I see that in that snapshot's changelog, something was changed about how blocks are stored.
I've attached a glitched region file - I would recommend opening it in a new world, preferably superflat so you can see which areas are reset (and which ones are terrain that was reset on my server)
Environment
Server hardware is [intel i9-9900k 4.7ghz 16gb ram], running on linux.
It has a lot of custom datapacks, however even without those the glitch occurs. I don't believe datapacks are capable of resetting chunks either.
Attachments2
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
Chunks that haven't been explored since 1.13 are resetting.
relates to
I run a server with a 20k by 20k block custom world. It was created in 1.13.2, but some areas haven't been explored since. Those areas are bugging out, and around 20% of chunks in them are being reset back to vanilla chunks.
I started noticing this bug in 20w17a, however, it may have been going on for longer. I see that in that snapshot's changelog, something was changed about how blocks are stored.
I've attached a glitched region file - I would recommend opening it in a new world, preferably superflat so you can see which areas are reset (and which ones are terrain that was reset on my server)
[03:00:37] [Server thread/ERROR]: Couldn't load chunk [639, 36] java.lang.NullPointerException: null [03:00:37] [Server thread/ERROR]: Couldn't load chunk [639, 37] java.lang.NullPointerException: null [03:00:37] [Server thread/ERROR]: Couldn't load chunk [639, 38] java.lang.NullPointerException: null [03:00:37] [Server thread/ERROR]: Couldn't load chunk [638, 40] java.lang.NullPointerException: nullNote: No stacktraces are logged, possibly because the wrong logging methods are called (last parameter is Object and not Throwable)? The class logging this is called yf in 20w18a (Mojang name: net.minecraft.server.level.ChunkMap).
relates to
relates to
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
Very Important![[Mojang] Bartosz Bok](../../../data/avatars/users/10122.svg){kind=small}
[Mojang] Bartosz Bok![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
relates to
relates to
![[Bot] Piston](../../../data/avatars/users/31202.png){kind=small}
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
relates to
Might be the same issue as MC-181522?
I just confirmed that my issue has been fixed with the release of 20w21a. Looks like it was caused by MC-181522. Restoring a backup or copying the affected regions from a backed up save successfully restored the corrupted chunks, and they seem to be staying that way.
Could you attach the world (or a world demonstrating this issue) for testing purposes?
Might be the same issue as
MC-181511My apologies, I forgot to upload the region file! It should be at coordinates 10000 ~ 1000
Added a link to
MC-181507since it appears some chunks in the provided region file also don't have a DataVersion. However, I am not seeing the same stack trace. Errors were logged which I have added to the description of the report, they look similar to the one inMC-181511, however because both don't have stack traces, it is difficult to tell if both are caused by the same underlying bug.