-
Bug
-
Resolution: Fixed
-
1.18.10.20 Beta, 1.18.0.27 Beta, 1.18.0, 1.18.2 Hotfix
-
None
-
Confirmed
-
Multiple
-
590265
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:
- In java (latest snapshot) create a new world, leaving the seed field blank.
- Once in that world use the /seed command to get the seed for the world.
- Launch Bedrock Beta 1.18.0.27
- 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.
- is duplicated by
-
BDS-16581 Java and Bedrock World Seed Parity Mismatch
- Resolved
-
MCPE-148379 Seed Parity doesn't work
- Resolved
-
MCPE-149801 Seeds with more than 10 digits wont load
- Resolved
-
MCPE-150005 Seed changes after World Creation
- Resolved
-
MCPE-150801 Seed keep changing to different seed
- Resolved