Before I begin, I'd like to list some criteria of my situation to help troubleshoot and coordinate the issue. I play on Bedrock Edition, with an original model PlayStation 4. I sometimes play by myself, and sometimes two of my friends play as well. I have never used a texture pack with this world. This is not a Realm, as Realms are not yet available on Bedrock for PlayStation. My world size is dormant, and stuck at 953.1 megabytes, and has not changed ever since I encountered this issue over one month ago. My storage capacity has plenty of space, and I began to encounter this bug briefly after the release of the 1.14.60 hotfix.
Similarly to many reports, this glitch triggers randomly. I may encounter this glitch several times upon struggling to load up the world. Other times, it will not trigger at all. I also believe this issue to be triggered by loading chunks, hence all the initial reports referring to the usage of elytras. Usually, I am able to play my world by myself if I travel modestly without loading too many chunks. Other times, the world will instantly corrupt upon loading into the game. Whenever I try to invite a friend to play with me, the world will give me the corrupt message immediately upon their arrival into the world. I believe that when my friends try to join, the game has to keep track of too many chunks at once, and in response, stops functioning.
The conditions of this glitch are ludicrous. Not only my own, but so many magnificent worlds and hundreds of hours of playtime have been unreasonably lost due to this game-breaking issue. Minecraft is a game about exploring. The worlds we play every day should keep their promises about being infinite. Why should we be given the facade that we can explore and play to our hearts' content, when we can only explore a certain amount before our worlds give up on us?
It's a shame that this large of a thread has gone completely overlooked and unnoticed by Mojang. I understand that things are hectic and bustling due to the imminent arrival of the Nether Update, but there needs to be attention given to a glitch that has been rampant and destructive for over six months that causes worlds to become nearly unplayable.
For those who are new to this thread, I highly urge you to upvote. There is still time to get this issue noticed by Mojang before the arrival of the Nether Update. Please upvote and tell your friends about this.. and maybe all of our lost worlds will see the light of day again. Thank you for reading.
I noticed this while playing on Windows 10 edition. I saw a strider with a baby on its head; both were unexposed to lava. The adult strider was shaking and purple; the baby was the typical red color, as if it was exposed to lava.
Before I begin, I'd like to list some criteria of my situation to help troubleshoot and coordinate the issue. I play on Bedrock Edition, with an original model PlayStation 4. I sometimes play by myself, and sometimes two of my friends play as well. I have never used a texture pack with this world. This is not a Realm, as Realms are not yet available on Bedrock for PlayStation. My world size is dormant, and stuck at 953.1 megabytes, and has not changed ever since I encountered this issue over one month ago. My storage capacity has plenty of space, and I began to encounter this bug briefly after the release of the 1.14.60 hotfix.
Similarly to many reports, this glitch triggers randomly. I may encounter this glitch several times upon struggling to load up the world. Other times, it will not trigger at all. I also believe this issue to be triggered by loading chunks, hence all the initial reports referring to the usage of elytras. Usually, I am able to play my world by myself if I travel modestly without loading too many chunks. Other times, the world will instantly corrupt upon loading into the game. Whenever I try to invite a friend to play with me, the world will give me the corrupt message immediately upon their arrival into the world. I believe that when my friends try to join, the game has to keep track of too many chunks at once, and in response, stops functioning.
The conditions of this glitch are ludicrous. Not only my own, but so many magnificent worlds and hundreds of hours of playtime have been unreasonably lost due to this game-breaking issue. Minecraft is a game about exploring. The worlds we play every day should keep their promises about being infinite. Why should we be given the facade that we can explore and play to our hearts' content, when we can only explore a certain amount before our worlds give up on us?
It's a shame that this large of a thread has gone completely overlooked and unnoticed by Mojang. I understand that things are hectic and bustling due to the imminent arrival of the Nether Update, but there needs to be attention given to a glitch that has been rampant and destructive for over six months that causes worlds to become nearly unplayable.
For those who are new to this thread, I highly urge you to upvote. There is still time to get this issue noticed by Mojang before the arrival of the Nether Update. Please upvote and tell your friends about this.. and maybe all of our lost worlds will see the light of day again. Thank you for reading.