MCPE-8046loss of seed generation of the world
when I make all things new either default or seeds and time spent together the creation of the world the seed of the world becomes 0 this gives the loss of seed.
PS: I am speaking Spanish so use google translator to report bugs.
Linked Issues
Attachments1
Comments13
History18
Added relates to link: MCPE-1069Started game in survival, now it is in creativeCannot Reproduce
Resolution: Unresolved → Fixed
Added affects versions: 0.11.0
Confirmation Status: Unconfirmed → Confirmed
Added Assignee: 
Daniel Wustenhoff
Added affects versions: 0.11.0 Beta 1
Removed affects versions: 0.11.0 Beta 1
Resolution: Fixed → Unresolved
Resolution: Unresolved → Fixed
Added affects versions: 0.11.1
Resolution: Fixed → Unresolved
Resolution: Unresolved → Awaiting Response
Resolution: Awaiting Response → Unresolved
Added is duplicated by link: MCPE-12534Biome Chunk RearrangementDuplicate
Added is duplicated by link: MCPE-11610EXTREMELY WEIRD BUG!!!! LOST EVERYTHING IN INVENTORY!!!! Included World LinkDuplicate
Resolution: Unresolved → Awaiting Response
Resolution: Awaiting Response → Unresolved
Added affects versions: 0.14.0 Beta 1 0.13.1
Resolution: Unresolved → Cannot Reproduce
The same thing has happened once on Lumia 1320 Windows 8.1 when the phone lost power,the game changed to "creative mode" from "survival mode", and all my work have gone.
Do you edited your worlds with a world editor?
NO
[Spanish]
¿Todavía mantener el mundo de la misma ?
[English]
Does it still keep the world the same?
This relates to
MCPE-1069. Most likely not duplicable, as the gamemode does not appear to have changed.AMAN4700, are you resolving this issue based on confirmation from the developers? Or personal experience?
Still affects on older worlds. I openned a world that i have made on 0.4.0, when i openned, it crashes, and then the seed turns to "0"
Thank you, Luis.
This was fixed in 0.11.1. Now you can only see seeds from the edit screen
That was not the issue.
Can you confirm whether or not this happens in the latest release so I can close the issue? Thanks!
In
MCPE-12534, Nathan said that he encountered this on, apparently, 0.14.0 build 1.Please confirm if this still affects 0.14.1