What I did:
I took a default settings JSON from a world and changed a single character in the nether's dimension preset line. I then used this file to generate a custom world.
What I expected:
I expected the game to just ignore the nether's custom settings and continue with default generation, since that dimension section was 'broken.' I thought that all three dimensions would've generated normally(only the nether was modified on the JSON).
What Happened:
The game complained about the JSON, but still let me continue. When the world generated I discovered that both the nether and end were completely gone from the world. The overworld appeared to generate as normal with the exception that portals would never take you to their respective dimension(as they no longer existed).
Linked issues
Attachments
Comments 6
Liam, custom dimensions can be made with data packs, as such you can also overwrite the vanilla ones.
Even if you wanted to delete a dimension, the generator shouldn't ignore dimensions further down the list. My edit only should have changed the way the nether generated, but it seemed to just stop trying anything past the error despite nothing being wrong with the end's generation settings.
If you move the end from third to second in the list on the provided JSON it will make it so only the nether gets deleted(nothing is wrong with that). I feel I should not have to change the list order because of this behavior.
Thank you for your report!
We're tracking this issue in MC-197860, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
-- I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
This seems intended to me; only the top-level file is used to define the dimension; it being invalid doesn't change how it loads. The same is done with everything that is not sounds.json, or data pack tags (both of which are just "lists" basically).
Additionally, this is the only way to delete a dimension, without disabling vanilla (if you do disable vanilla, you need to update the tags almost every update to even be able to launch...)