Data packs can now add dimensions to a world, but naming one minecraft:overworld, minecraft:the_nether or minecraft:the_end causes it to be ignored completely with no errors.
This means data packs have no way to replace vanilla dimensions upon world creation.
How to reproduce:
Download the attached data pack containing settings for
minecraft:overworldAdd and enable it when creating a new world
Notice you didn't spawn in a superflat crimson world
Optional: Teleport to a dimension with identical settings using
/execute in minecraft:expected_world run teleport ~ ~ ~
and see that it was created just fine
Linked issues
relates to 1
Attachments
Comments 11
Confirmed for 20w28a, where this bug matters even more, since you need to replace the entire vanilla dimension in order to change any structure or biome generation.
I believe data pack dimensions are not supposed to replace vanilla dimensions in the first place, that is for the Import World Settings button
The fix doesn't seem to have worked completely; /u/dragon3025 and I can both confirm that replacing the noise settings for the Overworld does not work: https://www.reddit.com/r/minecraft_configs/comments/i088xw/having_trouble_adjusting_default_overworld/
In addition, I tried to modify a biome, and that didn't work either.
Did you test mine, is everything set up right?
Should I really make a new issue? The problem currently is the same as this one, except it's "some" datapacks and not "all" datapacks, since yours worked, but mine and Michael Norton's didn't. I would probably title the new issue the same as this one, except with the word "some" before it.
@Michael Norton
Your pack changes the noise_settings file, not the dimension file. If that doesn't work then it is a separate bug, because those are two different types of configuration file.
Okay, I was able to edit the vanilla overworld by copying the noise settings .json to the settings file in the dimension json, and tweak it there.
I don't think it's really necessary to create a whole new issue for noise_settings because that's part of replacing the vanilla dimension that isn't working, but since title of this issue is technically not true anymore, I created a new issue for this: MC-196592.
MC-196592 has the same problem that this one did; the title is just as limited in scope. This issue also affects biomes from my testing, and probably other things as well. Wouldn't it make more sense to have a single issue that covers everything, instead of creating a separate one for every single type of data that isn't overridden properly?
Can confirm for 1.16.1