When inputting a pre-selected seed, world generation creates an entirely different seed. Used seed 013523053477933 entered world, save/quit, examined world information, seed instead read as -1798537171.
Linked issues
relates to 1
Comments 3
More information about the seeds and integer size can also be found here: https://minecraft.gamepedia.com/Seed_(level_generation)#Technical
Like Java edition, Console edition also uses a 64-bit integer, hence why you might see larger values for seeds there.
if Java and Console use 64bit integer seed, why can't bedrock do the same, why does it have to be truncated to 32bit?
Thank you for your report!
However, this issue works as intended.
013523053477933 in hexadecimal is C4C 94CC 802D. -1798537171 in hexadecimal is 94CC 802D. This shows that the seed change is the result of conversion to a 32-bit signed integer and truncation of the result. This is by design. Bedrock Edition converts whatever you enter for a seed into a 32-bit signed integer which it stores in the world and uses for chunk generation.
If you got 013523053477933 from a Java Edition or Console Edition world, be advised that even if the seed weren't changed, it would not have generated the same world anyway. World seeds are not compatible across editions, and may not be compatible between updates within a version.