Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-181522

Chunks that haven't been explored since 1.13 are resetting


    • Icon: Bug Bug
    • Resolution: Fixed
    • 20w21a
    • 20w18a
    • None
    • 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.
    • Confirmed
    • Datafixer
    • Very Important

      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).

        1. 2020-04-27_12.49.48.png
          3.75 MB
        2. 2020-04-30_07.30.40.png
          4.29 MB
        3. r.19.1.mca
          4.11 MB

            boq [Mojang] Bartosz Bok
            4P5 4P5
            7 Vote for this issue
            7 Start watching this issue