MCPE-187270client_biome files are missing options from biomes_client.json, preventing resource packs from updating to the new system
Three options from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
water_surface_transparencyFixed in 1.21.60.24- remove_all_prior_fog
- inherit_from_prior_fog
- fog_ids_to_merge
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The "water_surface_transparency" property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.
Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
Default values can be configured to automatically override biomes which are not otherwise specified, like in biomes_client.json.
New biomes (added post-1.21.40) can have their water transparency configured by modifying vanilla pack files, just like biomes_client used to.
Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system.
Default values cannot be configured, so packs which change water will have to be updated for every new biome addition.
A Pale Garden entry must be manually added to biomes_client.json to change water transparency.
Linked Issues
Created Issue:
client_biome files are missing options from biomes_client.json
Three options from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
- water_surface_transparency
- remove_all_prior_fog
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
Expected Result
client_biome files provide an updated system, fully deprecating biomes_client.json.
Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality.
Three options from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
- water_surface_transparency
- remove_all_prior_fog
- inherit_from_prior_fog
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The water_surface_transparency property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.
Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system, especially with water surface transparency.
Three options from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
- water_surface_transparency
- remove_all_prior_fog
- inherit_from_prior_fog
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The water_surface_transparency property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.
Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system, especially with water surface transparency.Three options from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
- water_surface_transparency
- remove_all_prior_fog
- inherit_from_prior_fog
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The water_surface_transparency property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.
Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
New biomes (added post-1.21.40) can have their water transparency configured just like biomes_client biomes.
Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system.
The Pale Garden cannot have its water transparency configured due to only having a client_biome file, and not a biomes_client.json entry.
client_biome files are missing options from biomes_client.json, preventing some resource packs from updating to the new system
client_biome files are missing options from biomes_client.json, preventingsomeresource packs from updating to the new system
Three options from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
- water_surface_transparency
- remove_all_prior_fog
- inherit_from_prior_fog
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The water_surface_transparency property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.
Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
New biomes (added post-1.21.40) can have their water transparency configured just like biomes_client
biomes.Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system.
The Pale Garden cannot have its water transparency configured due to only having a client_biome file, and not a biomes_client.json entry.
Three options from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
- water_surface_transparency
- remove_all_prior_fog
- inherit_from_prior_fog
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The water_surface_transparency property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.
Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
New biomes (added post-1.21.40) can have their water transparency configured just like biomes_client used to.
Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system.
The Pale Garden cannot have its water transparency configured due to only having a client_biome file, and not a biomes_client.json entry.
![[Mod] LateLag](../../../data/avatars/users/92884.png){kind=small}
Three options from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
- water_surface_transparency
- remove_all_prior_fog
- inherit_from_prior_fog
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The water_surface_transparency property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.
Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
New biomes (added post-1.21.40) can have their water transparency configured just like biomes_client used to.
Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system.
The Pale Garden cannot have its water transparency configured due to only having a client_biome file, and not a biomes_client.json entry.
Three options from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
- water_surface_transparency
- remove_all_prior_fog
- inherit_from_prior_fog
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The water_surface_transparency property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.
Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
New biomes (added post-1.21.40) can have their water transparency configured just like biomes_client used to.
Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system.
The Pale Garden cannot have its water transparency configured due to only having a client_biome file, and not a biomes_client.json entry.
Three options from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
- water_surface_transparency
- remove_all_prior_fog
- inherit_from_prior_fog
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The water_surface_transparency property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.
Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
New biomes (added post-1.21.40) can have their water transparency configured just like biomes_client used to.
Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system.
The Pale Garden cannot have its water transparency configured due to only having a client_biome file, and not a biomes_client.json entry.
Three options from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
- water_surface_transparency
- remove_all_prior_fog
- inherit_from_prior_fog
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The water_surface_transparency property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.
Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
New biomes (added post-1.21.40) can have their water transparency configured just like biomes_client used to.
Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system.
The Pale Garden cannot have its water transparency configured due to only having a client_biome file, and not a biomes_client.json entry.
Three options from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
- water_surface_transparency
- remove_all_prior_fog
- inherit_from_prior_fog
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The water_surface_transparency property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.
Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
New biomes (added post-1.21.40) can have their water transparency configured just like biomes_client used to.
Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system.
The Pale Garden cannot have its water transparency configured due to only having a client_biome file, and not a biomes_client.json entry.
Three options from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
- water_surface_transparency
- remove_all_prior_fog
- inherit_from_prior_fog
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The water_surface_transparency property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.
Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
New biomes (added post-1.21.40) can have their water transparency configured just like biomes_client used to.
Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system.
The Pale Garden cannot have its water transparency configured due to only having a client_biome file, and not a biomes_client.json entry.
Three options from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
- water_surface_transparency
- remove_all_prior_fog
- inherit_from_prior_fog
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The water_surface_transparency property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.
Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
New biomes (added post-1.21.40) can have their water transparency configured just like biomes_client used to.
Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system.
The Pale Garden cannot have its water transparency configured due to only having a client_biome file, and not a biomes_client.json entry.
Three options from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
- water_surface_transparency
- remove_all_prior_fog
- inherit_from_prior_fog
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The water_surface_transparency property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.
Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
New biomes (added post-1.21.40) can have their water transparency configured just like biomes_client used to.
Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system.
The Pale Garden cannot have its water transparency configured due to only having a client_biome file, and not a biomes_client.json entry.
Three options from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
- water_surface_transparency
- remove_all_prior_fog
- inherit_from_prior_fog
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The "water_surface_transparency" property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.
Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
New biomes (added post-1.21.40) can have their water transparency configured just like biomes_client used to.
Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system.
The Pale Garden cannot have its water transparency configured due to only having a client_biome file, and not a biomes_client.json entry.
Three options from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
- water_surface_transparency
- remove_all_prior_fog
- inherit_from_prior_fog
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The "water_surface_transparency" property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.
Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
New biomes (added post-1.21.40) can have their water transparency configured just like biomes_client used to.
Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system.
ThePale Gardencannot have its water transparency configured due to only having a client_biome file, and not a biomes_client.json entry.Three options from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
- water_surface_transparency
- remove_all_prior_fog
- inherit_from_prior_fog
- fog_ids_to_merge
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The "water_surface_transparency" property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.
Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
New biomes (added post-1.21.40) can have their water transparency configured by modifying vanilla pack files, just like biomes_client used to.
Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system.
A Pale Garden entry must be manually added to biomes_client.json to change water transparency.
Threeoptions from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
- water_surface_transparency
- remove_all_prior_fog
- inherit_from_prior_fog
- fog_ids_to_merge
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The "water_surface_transparency" property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.
Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
New biomes (added post-1.21.40) can have their water transparency configured by modifying vanilla pack files, just like biomes_client used to.
Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system.
A Pale Garden entry must be manually added to biomes_client.json to change water transparency.
Four options from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
- water_surface_transparency
- remove_all_prior_fog
- inherit_from_prior_fog
- fog_ids_to_merge
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The "water_surface_transparency" property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.
Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
New biomes (added post-1.21.40) can have their water transparency configured by modifying vanilla pack files, just like biomes_client used to.
Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system.
A Pale Garden entry must be manually added to biomes_client.json to change water transparency.
![[Mod] Jarl-Penguin](../../../data/avatars/users/92849.png){kind=small}
![[Mod] GoldenHelmet](../../../data/avatars/users/18951.svg){kind=small}
relates to
![[MCQA] v-krbaj](../../../data/avatars/users/10122.svg){kind=small}
Fouroptions from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
- water_surface_transparency
- remove_all_prior_fog
- inherit_from_prior_fog
- fog_ids_to_merge
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The "water_surface_transparency" property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.
Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
New biomes (added post-1.21.40) can have their water transparency configured by modifying vanilla pack files, justlike biomes_clientused to.Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system.
A Pale Garden entry must be manually added to biomes_client.json to change water transparency.Three options from the old biomes_client file cannot be used in the new, separated client_biome files. These options are:
water_surface_transparencyFixed in 1.21.60.24- remove_all_prior_fog
- inherit_from_prior_fog
- fog_ids_to_merge
In addition, there is no way to create a "default" biome configuration that overwrites all other biomes.
The "water_surface_transparency" property in particular is required for many resource packs. Losing this functionality will prevent pack creators from switching to the updated system.Old biomes_client.json Features:
New client_biome Features:
Expected Result
client_biome files provide an updated biome visuals system, fully deprecating biomes_client.json.
Default values can be configured to automatically override biomes which are not otherwise specified, like in biomes_client.json.
New biomes (added post-1.21.40) can have their water transparency configured by modifying vanilla pack files, just like biomes_client used to.Observed Result
client_biome files lack all the options necessary to recreate biomes_client.json functionality, forcing resource pack creators to stick with the old system.
Default values cannot be configured, so packs which change water will have to be updated for every new biome addition.
A Pale Garden entry must be manually added to biomes_client.json to change water transparency.
Can confirm. This bug is caused by MCPE-187270. Your report is not a duplicate since it specifically describes the swamp issue.
Warm oceans are also affected, as they used to have a water_surface_transparency of 0.55, but now they don't.
Did they remove the ability to add biomes_client.json entries for biomes that don't normally have them? Or does this not work specifically with the Pale Garden? If neither of these are true, then it should still technically be possible to change these aspects of the Pale Garden.
Also, another biomes_client.json feature that is not mentioned here is "fog_ids_to_merge", which has been removed from the most current iteration of the file but still retains function.
Replying to cornbread_:
It turns out, you can add a pale_garden entry to biomes_client.json and it is functional, but that entry is not present in any of the vanilla resources, so it may be unintended. The 1.21.40 changelog indicated the client_biome files are meant to entirely replace biomes_client.json, not just supplement it, so I think the original issue stands.