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

Recently-placed blocks despawn after leaving chunk

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • 1.18 Pre-release 1
    • None
    • Unconfirmed
    • Survival
    • (Unassigned)

      Hey there, I'm having a problem with my Minecraft 1.18 PR1 game, which was converted from last screenshot. I was building a structure using cauldrons next to my base (which sits at chunk 46,-62), which is in a village. I had placed down the first cauldron a few days ago, and went mining for more iron to build the next 3 today (for a total of 4). However, after I went exploring a few chunks away, when I returned, the 3 cauldrons that I had placed disappeared. Curious, I used the iron I got while exploring to make new cauldrons, place them down, then exit the game and re-enter to see what happened. They once again disappeared. The rest of the structure was not damaged, and the first cauldron I had placed days ago was still intact, so even before they disappeared after exiting and entering the game, I don't believe it would have been a creeper attack or anything like that.

      Below is the latest.log file for my most recent session. A part that I suspect is relevant is [00:30:39] [Server thread/ERROR]: Failed to save chunk 46,-62 java.lang.NullPointerException: Cannot read field "d" because "$$0" is null     at ddm.b(SourceFile:23) ~[1.18-pre1.jar:?] because it specifically references being unable to save changes made in the chunk I had placed my structure in. latest.log I have also attached a picture of my structure, which is notably absent of the cauldrons (and cobbled deepslate I had placed beneath it.)

        1. 2021-11-13_01.42.17.png
          1.18 MB
          A Mongus
        2. latest.log
          47 kB
          A Mongus

            Unassigned Unassigned
            dreamcheems A Mongus
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: