[MCPE-18739] Entering a seed past a 32bit integer truncates it to be under the 32 bit integer limit Created: 26/Nov/16  Updated: 26/Apr/22  Resolved: 14/Nov/17

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 1.13.0.1 Beta, 1.12.0.14 Beta, 1.16.100.53 Beta, 1.16.100.52 Beta, 1.16.100.51 Beta, 1.16.100.50 Beta, 1.16.20.54 Beta, 1.16.20.52 Beta, 1.16.20.50 Beta, 1.16.0.68 Beta, 1.16.0.67 Beta, 1.16.0.66 Beta, 1.16.0.64 Beta, 1.16.0.63 Beta, 1.16.0.61 Beta, 1.16.0.60 Beta, 1.16.0.59 Beta, 1.16.0.57 Beta, 1.16.0.58 Beta, 1.16.0.55 Beta, 1.16.0.53 Beta, 1.16.0.51 Beta, 1.15.0.56 Beta, 1.15.0.55 Beta, 1.15.0.54 Beta, 1.15.0.53 Beta, 1.15.0.51 Beta, 1.14.30.51 Beta, 1.14.25.1 Beta, 1.14.2.51 Beta, 1.14.2.50 Beta, 1.14.0.51 Beta, 1.14.0.50 Beta, 1.14.0.4 Beta, 1.14.1.3 Beta, 1.14.0.3 Beta, 1.14.0.2 Beta, 1.14.0.1 Beta, 1.13.0.18 Beta, 1.13.0.17 Beta, 1.13.0.16 Beta, 1.13.0.15 Beta, 1.13.0.6 Beta, 1.13.0.5 Beta, 1.12.0.13 Beta, 1.12.0.11 Beta, 1.12.0.2 Beta, 1.11.0.10 Beta, 1.9.0.0 Beta, 1.4.4.0, 0.16.2, 1.0.0, 1.2.0.2, 1.1.5.0, 1.2.0.9, 1.2.0.11, 1.2.0.15, 1.2.0.18, 1.2.0.22, 1.2.0.25, 1.2.0.31, 1.2.0.81, 1.2.1.1, 1.2.2.3, 1.2.5.0, 1.2.3.6, 1.2.5.12, 1.2.5.15, 1.2.6.2, 1.2.9.1, 1.2.10.1, 1.2.10.2, 1.2.13.5, 1.2.11.4, 1.2.13.6, 1.2.13.10, 1.2.14.2, 1.2.14.3, 1.2.13.54, 1.2.20.1, 1.2.13.60, 1.2.16.3, 1.2.20.2, 1.5.0.0, 1.5.0.1, 1.4.0.5, 1.5.0.4, 1.5.0.7, 1.4.3.0, 1.5.0.10, 1.6.0.1, 1.4.2.0, 1.6.0.5, 1.5.0.14, 1.6.0.6, 1.6.0.8 Beta, 1.6.0.30 Beta, 1.7.0.2 Beta, 1.7.0.3 Beta, 1.7.0.7 Beta, 1.7.0.9 Beta, 1.8.0.8 Beta, 1.8.0.11 Beta, 1.8.0.13 Beta, 1.8.0.10 Beta, 1.8.0.14 Beta, 1.9.0.2 Beta, 1.9.0.3 Beta, 1.10.0.3 Beta, 1.10.0.4 Beta, 1.11.0.1 Beta, 1.11.0.3 Beta, 1.11.0.4 Beta, 1.11.0.7 Beta, 1.12.0.3 Beta, 1.12.0.6 Beta, 1.13.0.4 Beta, 1.13.0.2 Beta, 1.14.1.2 Beta
Fix Version/s: None

Type: Bug
Reporter: Delvin4519
Resolution: Works As Intended Votes: 2
Labels: world-generation

Attachments: PNG File Screenshot (47).png     PNG File Screenshot (48).png     PNG File Screenshot (49).png     PNG File Screenshot (50).png     PNG File Screenshot (51).png     PNG File Screenshot (52).png     PNG File Screenshot (53).png     PNG File Screenshot (54).png     PNG File Screenshot (55).png    
Issue Links:
Duplicate
is duplicated by MCPE-36169 Seed generator does not work Resolved
is duplicated by MCPE-42945 can't add a custom seed - minecraft x... Resolved
is duplicated by MCPE-147899 Changing seed generation Resolved
Relates
relates to MC-250445 There are only 2^48 possible carver a... Open
relates to MCPE-7091 CompoundTag::putLong has wrong parame... Resolved
relates to MCPE-28471 Input seed altered during world gener... Resolved
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" MCPE-148168

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 MC-236650 and its resulting parity implications.

Comment by Delvin4519 [ 29/Feb/20 ]

PLEASE FIX THIS BUG

 

https://www.youtube.com/watch?v=Hj6XAOApFl4

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 MCPE-7091... seeds are only saved as 32-bit numbers, so numbers outside of the 32-bit range are either being truncated or simply overflow.

Generated at Sat Jan 11 15:20:31 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.