1: Confirming this issue using a local server on Windows 10. Client version 1.16.210.06, Server version 1.16.210.06 - Previously 1.16.210.02
2: This may or may not be a viable workaround, but I was able to circumvent the issue as follows:
- Close BDS. Create backup copy of world folder. - Rename "old" world folder so BDS generates a new one. - Reopen BDS and connect with a player to generate the world. - Close BDS. Copy both worlds into primary Minecraft world folder (this step is not strictly necessary, just a function of my setup.) - Copy db folder from original world folder into new world folder, overwriting. - Open level.dat for original world and new world (using MCC Toolchest PE, if it matters) and adjust values for relevant entries - mostly current time/tick, spawn location, etc. - Save. Copy resulting world folder back to BDS world path.
When I reopened BDS and Minecraft, I was able to connect normally and - more importantly - the old world had "ported" over without any issue.
My suspicion is that something changed in the level.dat which is causing this issue, but I lack the programming skill to go any further.
For obvious reasons, I would suggest keeping an unaltered backup copy of your world if you should choose to use this workaround. I'm sure it will be patched soon enough. Additionally, I'm sure you could just edit the level.dat and copy it from the "good" world to the old one without all the extra steps, but I wasn't sure anything I was doing would work.
Chris Trulock
1: Confirming this issue using a local server on Windows 10. Client version 1.16.210.06, Server version 1.16.210.06 - Previously 1.16.210.02
2: This may or may not be a viable workaround, but I was able to circumvent the issue as follows:
- Close BDS. Create backup copy of world folder.
- Rename "old" world folder so BDS generates a new one.
- Reopen BDS and connect with a player to generate the world.
- Close BDS. Copy both worlds into primary Minecraft world folder (this step is not strictly necessary, just a function of my setup.)
- Copy db folder from original world folder into new world folder, overwriting.
- Open level.dat for original world and new world (using MCC Toolchest PE, if it matters) and adjust values for relevant entries - mostly current time/tick, spawn location, etc.
- Save. Copy resulting world folder back to BDS world path.
When I reopened BDS and Minecraft, I was able to connect normally and - more importantly - the old world had "ported" over without any issue.
My suspicion is that something changed in the level.dat which is causing this issue, but I lack the programming skill to go any further.
For obvious reasons, I would suggest keeping an unaltered backup copy of your world if you should choose to use this workaround. I'm sure it will be patched soon enough. Additionally, I'm sure you could just edit the level.dat and copy it from the "good" world to the old one without all the extra steps, but I wasn't sure anything I was doing would work.
Either way, hope this helps.
Best,
Chris