MCPE-18739Entering a seed past a 32bit integer truncates it to be under the 32 bit integer limit
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.
Linked Issues
is duplicated by3
MC-250445
Low
- Works As Intended
Delvin4519- 2
- 7
- Unconfirmed
- Windows
- Windows 10 Pro 64bit Version:14393.447
- world-generation
1.13.0.1 Beta - 1.14.1.2 Beta
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
Created Issue:
Entering a seed past a 32bit integer breaks the seed generation.
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)
What happened instead: Minecraft changes the seed to a completely different value. (seed 52968166106 always returns seed 1428558554)
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.
Attachments9
- Unresolved
- Open
- Unconfirmed
- Windows
- Windows 10 Pro 64bit Version:14393.447
- 0.16.2 1.2.13.10
relates to
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)
What happened instead: Minecraft changes the seed to a completely different value. (seed 52968166106 always returns seed 1428558554)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.
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)
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.
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
relates to
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.
When entering a seed integer past 2147483647 or -2147483648, Minecraft changes the seed to be completely different.Wh
at should happen: Entering a integerup 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 canchange the seed ofa 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.
MCPE 1.2.9 still uses 32bit seeds, so 1.2.9 is sitll 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.
MCPE 1.2.9 still uses 32bit seeds, so 1.2.9 is s
itll 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.
MCPE 1.2.9 still uses 32bit seeds, so 1.2.9 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.
MCPE 1.2.
9still uses 32bit seeds, so 1.2.9is 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.
MCPE 1.2.10 still uses 32bit seeds, so 1.2.10 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.
MCPE 1.
2.10still uses 32bit seeds, so 1.2.10is 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 -21474836483. 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.
MCPE 1.6.0.1 still uses 32bit seeds, so 1.6.0.1 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.
is duplicated by
is duplicated by
Entering a seed past a 32bit integerbreaks the seed generation.Entering a seed past a 32bit integer truncates it to be under the 32 bit intergar limit
Entering a seed past a 32bit integer truncates it to be under the 32 bit intergar limitEntering a seed past a 32bit integer truncates it to be under the 32 bit integer limit
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
MCPE 1.6.
0.1still uses 32bit seeds, so 1.6.0.1is 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.
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.
is duplicated by
is duplicated by
is duplicated by
![[Mod] OcelotOnesie](../../../data/avatars/users/43220.png){kind=small}
is duplicated by
This should be reopened!!!
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
relates to
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-18739.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue at MCPE-18739, so we will resolve and link this ticket as a duplicate.
If you haven't already, you might like to make use of the search feature, to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Importantly, given the aim of generational parity between Java Edition and Bedrock Edition, this also applies there as well.
It might be advisable to have MCPE-18739 be reopened as a result.
Thank you for your report!
We're tracking this issue in MCPE-18739, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as working as intended, which means this is not considered a bug and won't be fixed. Please do not leave a comment on the linked ticket.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Still?They seem to think it’s been fixed. Could this relate to MCPE-18739
![[Mod] EVGENSYPERPRO](../../../data/avatars/users/92853.png){kind=small}
This problem is 32 bit numbers. Java version uses 64 bit numbers for seed. This problem was first described in MCPE-18739, however, it is closed as "Works As Intended", but after the seed parity was officially announced for minecraft live, I think this problem needs to be revise.
I can confirm this report.
Very closely relates to MC-250445. Likely also relates to MC-111378, MC-236650, MCPE-18739, MCPE-95011 and MCPE-154323.
This is specifically the Bedrock Edition equivalent of MC-250445; the differences between these two tickets constitute MCPE-154323.
The bug
Bedrock Edition recently expanded to allow for the main world generation to support 64-bit seeds. However, this only appears to affect the superficial terrain shape and noise caves; it appears that carvers will end up being the same for very many seeds.
How to reproduce
A keen eye can be used to reproduce this on any seed - just create a world with a desired seed, locate a carver cave, then create another world with a seed which has an integer multiple of 4294967296 added to the previous seed and go to those exact coordinates. Assuming that the cave's generation hasn't been interrupted by something like an aquifer, surface terrain or a structure, the cave's basic shape should be identical.
I've specifically opted to use the seed 1669320484, which becomes 5964287780 when 4294967296 is added to it. The choice of this seed is due to the very unique cave generation it results in (MCPE-95011), which makes the similarities between the two seeds incredibly obvious. The weird cave generation is not the focus of this bug report - I'm just using it since it makes the matching caves across different seeds obvious.
Expected results
Cave generation would use all 64 bits of the seed, just like the rest of terrain does.
Actual results
It only uses the lower 32 bits of the seed. As a result, any given carver layout will be shared by another 4,294,967,295 other seeds.
How to fix
Carvers should be made to also respect the upper 32 bits in the world seed as to eliminate duplicate caves like these.
If the carver RNG is redone, it should also be reworked in the same way in Java Edition as to fix MC-250445 and MCPE-154323. Such a change could also fix MC-111378 and MCPE-95011.
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.Same issue here on iPhone X please update to 64bit int
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.
PLEASE FIX THIS BUG
https://www.youtube.com/watch?v=Hj6XAOApFl4
I would strongly recommend reopening this as per
MC-236650and its resulting parity implications.Should this be reopened? Because this really gets in the way of 1.18’s seed parity idea.
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
mooing_cowmilk: problem "cloned"
MCPE-148168