Entering 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.