Clouds do not render in custom worlds if the cloud_height is not specified
This issue was introduced in 25w15a when the cloud_height field was introduced
Reproduction Steps:
- Load the attached world REPO.zip (warning: allocate at least 4GB of RAM)
- Run /tp ~ 100 ~ (which is where the clouds should be)
Observed Results:
- Following these steps in 25w16a you’ll find that there are no clouds
- Following these steps in 1.21.5 you’ll find that there are clouds
Expected Results:
- If the cloud_height field is left empty, clouds would render at their default position. The patchnotes state that this field is optional.
Attachments
Comments 5
Hi
Could you let us know what datapack are you using and if this issue still occurs without the datapack?
This ticket will automatically reopen when you reply.
The datapack is included in the “REPO.zip” world download I provided.
It’s a very simple datapack, all it does is create a superflat world with a logical height of 4064 blocks. As it only modifies worldgen stuff it should have no impact on cloud rendering.
The issue doesn’t occur without the datapack because this issue is specifically about clouds not rendering in worlds with custom height.
Here’s the datapack on its own.
[media]The customized.zip datapack does not specify the cloud_height field in the overworld dimension type, that was added in 25w15a. It appears intended that a dimension doesn’t have clouds when that field is not specified.
Can confirm.