I am unsure if this is a feature request or a bug, so I decided to try here first.
Normally, it is impossible to load a world on an older version of Minecraft, which triggers an error stating "A newer version of the game has saved this level. It cannot be loaded". However, the error also states "Unable to connect to world" despite being a locally stored world.
To reproduce:
Create a world on a newer version (in my case I used the Minecraft Preview).
Import it into an older version (or in my case, the stable release).
Attempt to load the world.
What was expected:
An error message saying "A newer version of the game has saved this level. It cannot be loaded" with no additional text besides the "OK" button on the bottom.
What was observed:
An error message saying "A newer version of the game has saved this level. It cannot be loaded" with additional text "Unable to connect to world" closer to the "OK" button.
Attachments
Comments 6
Generally an older version will not be able to "import" a newer version world. Please be specific about exactly how you did that and whether any error messages were shown during the import.
To @unknown: You seem to be confused. This isn't about the inability to load a world last saved in a newer version, but rather the error that shows up on the screen falsely stating "unable to connect to world"
To @unknown: The world actually imports successfully when done normally, however when you try to load it, it inadvertently states "Unable to connect to world" in the same error message as the "A newer version of the game has saved this level", however, I've previously been able to import worlds into older versions, and I've always thought it was normal for the game to be able to import worlds from a newer version because, unlike resource packs and behavior packs, there is no JSON file that defines the oldest version compatible. I've provided a clip that shows that the world imports when done normally.
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response.
Is this still an issue in the latest version? If yes, can you please add it to the affected versions (or mention it if you are not the reporter)?
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📓 Project Summary – 📧 Suggestions – 📖 Minecraft Wiki
Well to be honest I forgot about this report. I don't normally export Preview worlds for any reason other than backups, which is how I discovered this in the first place (I accidentally imported one into the release version of Minecraft). With that said, I did reproduce this with a 1.19.30.20 Preview world imported into 1.19.20.
Thank you for your report!
After consideration, the issue is being closed as Won't Fix.
Please note that this is not the same as Working as Intended, as this bug report correctly describes behavior in the game that might not be the intended or desirable behavior, but it will not be fixed right now. Sometimes, this is because the issue reported is minor and/or impossible to change without large architectural changes to the code base.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
This is unable to be fixed, this is caused by loading a world from a beta/preview into the full game release.