mojira.dev
MC-188503

Loading worlds from previous releases with custom dimensions removes them.

Loading worlds from previous releases with custom dimensions removes them.

I started tinkering with datapacks recently and wanted to add a new dimension. I couldn't ever access the dimension in 1.16-pre3, but it worked when I tried loading it on the previous version, 1.16-pre2. Upon reloading the world in 1.16-pre3, I loaded in the overworld and my custom dimension had been removed.

I assume this happens with all datapacks that add custom dimensions, but I'll link mine just in case.

Attachments

Comments 8

see the log then you will find that there are several new options in jsons of "dimension_type"

however I didn't found the correct value of "infiniburn", and also didn't understand the meaning of "logical_height" and "piglin_safe"

Then the issue is related to missing data because of additions? Where can I find the logs that mention these additions?

I have seen this as a problem with at least normal overworld type worlds. Floating Island (not main end island type) worlds and superflat worlds do not seem to have a problem, but I cannot guarantee this will happen or not happen to someone else.

you can see the new options here: https://minecraft.gamepedia.com/Dimension; after change the type json in datapack you can load the dimensions with no problem

Customized worlds are experimental. We do not guarantee backwards compatibility.

"piglin_safe": false,
"bed_works": true,
"respawn_anchor_works": true,
"has_raids": false,
"logical_height": 256,
"infiniburn": "minecraft:infiniburn_overworld"

I appended these extra settings because of this issue, but I am still getting errors in the log:

[Render thread/ERROR]: No key infiniburn in MapLike[{"ultrawarm":false,"natural":true,"shrunk":false,"ambient_light":-0.2,"has_skylight":true,"has_ceiling":false}];

The problem is the dimension type. Custom dimension types have been updated, and so dimension with a custom dimension type may or may not work and if it does not work, it will "cut off" the rest of the worlds from loading (If the first dimension in your first namespace folder uses a custom dimension type, no custom dimensions will work). This indeed is not a bug, there are just some new things needed in the dimension_type file

Ryan Perry

Fry

Community Consensus

Important

Custom Worlds, Data Packs

1.16 Pre-release 3

Retrieved