| Type: | Bug | ||
| Reporter: | Delvin4519 | ||
| Resolution: | Works As Intended | Votes: | 2 |
| Labels: | world-generation | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Confirmation Status: | Unconfirmed | ||||||||||||||||||||||||||||||||
| Platform: | Windows | ||||||||||||||||||||||||||||||||
| Description |
|
MCPE 1.6.100.60 still uses 32bit seeds, so 1.6.100.60 is still affected. When entering a seed integer past 2147483647 or -2147483648, Minecraft changes the seed to be completely different. What should happen: Entering a integer up to -9223372036854775808 or 9223372036854775807 should generate a seed with that integer. (example: seed:52968166106) This bug is not fixed in MCPE 1.2 and will corrupt a console world's seed transferred to this version from a 64bit integer to a 32bit one. What happened instead: Minecraft changes the seed to a completely different value. (seed 52968166106 always returns seed 1428558554) This is problematic as PC and Consoles use a 64bit terrain gen and seeds and PE uses only a 32bit. It can change the seed of a console world when it's moved from CE to PE. And an unnecessary additional difference between PC/CE and PE seeds. Recreating the bug: 1. Create a new world 2. Enter a integer in the seed box past 2147483647 or -2147483648 3. Generate the world, it doesn't matter whether it's on old or infinite. 4. Exit the world and then click on "edit world", notice the seed has been changed. |
| Comments |
| Comment by [Mod] EVGENSYPERPRO [ 28/Jan/22 ] |
|
mooing_cowmilk: problem "cloned" |
| Comment by mooing_cowmilk [ 27/Jan/22 ] |
|
Minecraft Beta - 1.18.20.21 has added 2^64 seeds to bedrock so the Resolution of Works As Intended is no longer true and should closed as fixed. https://feedback.minecraft.net/hc/en-us/articles/4423151445901 |
| Comment by Sniper1.1 [ 18/Nov/21 ] |
|
Should this be reopened? Because this really gets in the way of 1.18’s seed parity idea. |
| Comment by Connor Steppie [ 08/Oct/21 ] |
|
I would strongly recommend reopening this as per |
| Comment by Delvin4519 [ 29/Feb/20 ] |
|
PLEASE FIX THIS BUG
|
| Comment by Delvin4519 [ 20/Jan/18 ] |
|
I don't think it should marked as "working as intended". Both PC and Console use 64bit seeds. So when someone transfers a world from console, their seed ends up being changed. There are similarities between terrain gen on all consoles. It's frustrating how a seed on PC can work on console but there is no PE equivalent seed. PE only has 0.00000002% of possible seeds from PE or PC so that limits diversity of seeds. (PE seed equivalent). It should be marked as a bug until the devs switch PE over to a 64bit terrain gen from a 32bit. |
| Comment by Michael [ 11/Nov/17 ] |
|
Same issue here on iPhone X please update to 64bit int |
| Comment by Zeb [ 27/Dec/16 ] |
|
Sounds related to |