XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • Minecraft 1.14
    • None
    • I run a Windows 10 OS and I have only played in this world on version 1.14. No switching to snapshots, no adding mods, texture packs, anything. It's a single player Survival world with cheats that has never had LAN activated.
    • Unconfirmed
    • (Unassigned)

      I have closed and open this world many times before this point and today, I loaded in my worlds and saw that the cats I have just tamed, weren't at my home base so I explored the area and found a chunk of the ground disappeared. I switched to Creative mode to take screenshots and I noticed that my world had many chunks that disappeared or relocated.

       

      What I expected to happen was...:

      When I opened the world, everything would be ok and I could play like normal with my new cats and build my house.

       

      What actually happened was...:

      One section of my house was a pit with water at the bottom. The rest of the world had similar chunks that disappeared or were placed in random spots.

       

      Steps to Reproduce:

      I don't know why this happened. I've opened this world before and everything was fine. I will include screenshots. I can't include my save file through this, I apologize. The files don't stay within the folder.

        1. 2019-05-10_10.38.47.png
          2019-05-10_10.38.47.png
          3.55 MB
        2. 2019-05-10_10.38.58.png
          2019-05-10_10.38.58.png
          1.45 MB
        3. 2019-05-10_10.39.15.png
          2019-05-10_10.39.15.png
          598 kB
        4. 2019-05-10_10.39.38.png
          2019-05-10_10.39.38.png
          1.36 MB
        5. 2019-05-10_10.39.46.png
          2019-05-10_10.39.46.png
          1.71 MB
        6. 2019-05-10_10.40.13.png
          2019-05-10_10.40.13.png
          1.72 MB

            Unassigned Unassigned
            AkiKitty8 Alyssa
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: