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

MC 1.16 Release Issues (See description)

XMLWordPrintable

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

      Hi Team,

      I understand that the Bedrock_server is still in 'Alpha' and I fully support this, this is a fantastic product to be offering.

      I believe I have come across a glitch that warrants some investigation. This has put my map at serious risk of damage (good thing I backed up before updating).

       

      Playing the map locally on windows 10 seems ok with some minor bugs, boats under water are now on top with stone going from the ground up to sea level with the boat on top (see attached images).

       

      Playing the same map (copy/paste) on a Minecraft Server (bedrock_server 1.16.0.2) shows the same issue with boats and biomes where I thought I had unlocked by distance rendering are now stone. Any locations where I have explored seem ok. Looks to be that any blocks that I could see in a distance is now stone (images attached).

       

      Duplicate Bugs are fun, but often fixed in every release (shame) to make end users experience 'true' gameplay... but this issue unexplainable.  Every major update appears to just break maps ruining 100s of hours of game play. (Sorry, little rant).

       

      Hope the screenshots help, let me know if there is anything else I can provide.

       

        1. Glitch 1 A.png
          5.80 MB
          Irish Dave
        2. Glitch 1 B.png
          6.83 MB
          Irish Dave
        3. Glitch 2 A.png
          1.91 MB
          Irish Dave
        4. Glitch 2 B.png
          2.14 MB
          Irish Dave
        5. Glitch 3 A.png
          4.15 MB
          Irish Dave
        6. Glitch 3 B.png
          5.76 MB
          Irish Dave

            irishdave Irish Dave
            Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: