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

Seed parity for random seeds only works in one direction

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Resolution: Fixed
    • 1.18.10.20 Beta, 1.18.0.27 Beta, 1.18.0, 1.18.2 Hotfix
    • 1.18.20.21 Beta, 1.18.30
    • None
    • Confirmed
    • Multiple
    • 590265

    Description

      During the Minecraft Live event seed parity was explained. The scenario given was a that Java player can generate a random world and that seed can be given to a bedrock player and they will get the same world. I realise this likely only covers biomes, terrain etc.

      As at 1.18.0.27, seed parity for worlds with a random seed only works when going from Bedrock to Java. Ie a Bedrock player can generate a world with a random seed and give that seed to a Java player.

      If a Java player generates a random world and gives that seed to a Bedrock player, the bedrock player gets a completely different world.

      (see https://youtu.be/w6zLprHHZOk?t=3265 54:26 - 54:38)

      Steps to Reproduce:

      1. In java (latest snapshot) create a new world, leaving the seed field blank.
      2. Once in that world use the /seed command to get the seed for the world.
      3. Launch Bedrock Beta 1.18.0.27
      4. Create a new world with the seed from java

      Observed Results:
      The worlds have completely different biomes and terrain.

      Expected Results:
      The worlds should have very similar biomes and terrain

      Notes:
      I realise this side of seed parity might simply not have been implemented yet. I figured it would turn up in one of the betas at some stage. Now that 1.18 is at the pre-release stages I'm worried this may have been overlooked.

      Attachments

        Issue Links

          Activity

            People

              crackedMagnet Matthew Ferguson
              Votes:
              22 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                CHK: