I have a world I've worked on since December of 2015 on the Xbox 360 Edition and have done so with relative ease for years. On Bedrock Edition, I've experienced glitchy chunks that crashed my world that lasted an update, but never have I experienced such a long gap in time where I haven't even been able to enter my world. Since late June of 2019 through today, every time I have attempted to enter this world, I've been stuck on "Generating Terrain" for at most 20 minutes at a time, but eventually, the game would crash anyways. I've never had the issue of being stuck in the Nether or the End, as the glitch occurred while I was in the overworld, and hadn't left it in months. I cannot tell if the world is corrupted, because usually, a notification shows up that it is corrupted. This issue only consistently happens with one world, and the only, most recent copy I can enter was from May of 2019, but in that span of a month, until I lost it again, I built a large amount of stuff that I do not want to just forget about. I decided I'd wait until 1.13 (since SUPPOSEDLY it was fixed in 1.12.1) to see if this issue would become fixed, and it still is just as bad as it has always been. I decided to finally waste $3.99 on a month of realms to export the world to PC in an attempt to tamper with a copy of the world in an editor, but all attempts at any alterations were ineffective.
Below is an exported link of the world from OneDrive. If someone from the team could try and take a glance at my specific case and figure out what it is I am to do, that'd be fantastic. Otherwise, I don't know what to do, and I honestly don't have the motivation to attempt to rebuild what I lost.
Linked issues
Attachments
Comments 17
migrated
I just tried to open the world provided, and it crashed my Minecraft (1.14.30 Win 10 PC). It only stayed on the loading screen for a few seconds seconds, and the entire Minecraft window disappeared, no error message. Tried it again with the render distance and simulation distance reduce to minimum and the only difference was a shorter loading time before crash.
I did notice that "experimental gameplay" is turned on for the world. It could be that an experimental feature from an earlier version is causing the crash. That is a risk with using experimental features.
I also have noticed looking at the world file in MCCToolChest that the world has been opened in, and may have been created in, a beta version. The InventoryVersion listed in level.dat is 1.2.13-beta8. That could be why it does not load in the release version.
On the official beta page, there is the following warning:
Beta builds will likely be unstable and are not representative of final version quality. Please backup your Worlds before joining the beta
I just tried to open the world provided, and it crashed my Minecraft (1.14.30 Win 10 PC). It only stayed on the loading screen for a few seconds seconds, and the entire Minecraft window disappeared, no error message. Tried it again with the render distance and simulation distance reduce to minimum and the only difference was a shorter loading time before crash.
I did notice that "experimental gameplay" is turned on for the world. It could be that an experimental feature from an earlier version is causing the crash. That is a risk with using experimental features.
I also have noticed looking at the world file in MCCToolChest that the world has been opened in, and may have been created in, a beta version. The InventoryVersion listed in level.dat is 1.2.13-beta8. That could be why it does not load in the release version.
On the official beta page, there is the following warning:
Beta builds will likely be unstable and are not representative of final version quality. Please backup your Worlds before joining the beta
I am able to open the world with maps removed provided by Nathan Senter.
Due to a lack of response from the creator of this report, I will have it closed as "unable to reproduce."
I am able to open the world with maps removed provided by Nathan Senter.
Due to a lack of response from the creator of this report, I will have it closed as "unable to reproduce."