Uploaded image for project: 'Minecraft (Bedrock codebase)'
  1. Minecraft (Bedrock codebase)
  2. MCPE-165997

After update 1.19.51 Bedrock Edition I have a jungle hillside inside of one of my chunks

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • 1.19.51
    • None
    • Unconfirmed
    • Windows

      I've been playing in a particular chunk during December and never noticed a change. When I went through the nether and back out to the corrupted chunk, I materialized inside of said hill. Afterwards I went back and my gear was on top. I'll send a picture. 

      I tried using the solution of creating a new world and replacing the corrupted world's level.dat and level.dat_old with the new world's version. Still no change. Also I did log in despite the message my world was corrupted. I also tried using my old world's seed number. Still no success. And interesting thing happened. When I created the new world with my original seed, the spawn area is now 0,0. Where originally, that area was over ocean, so the world generator moved my spawn to land. Which wasn't 0,0.

      I back my files up. I understand players have been warned of this. I just thought Mojang should know, because up until now I've never experienced this issue. 

      What these pictures show is a patch of Jungle going through my savannah. The first pictures show current the last shows the same area prior to corruption. If you notice the past photos you'll see a nether portal surrounded by sandstone fences in a circle. That's were I materialized inside that jungle patch.

      Please, if you have the time, give any suggestions. Thank you! This world was started on October 28,2019. There's quite a bit of construction through out this world. Any help would be much appreciated.

       

       

       

            TheBigRed1967 TheBigRed1967
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: