After extensive testing, I have gathered a full list of disparities between the old biomes_client.json and the new client_biome system.
1. Several 'client_biome' biome identifiers are missing from vanilla biomes_client.json
Here's the complete list
birch_forest_hills_mutated
birch_forest_mutated
deep_dark
desert_mutated
dripstone_caves
frozen_peaks
grove
jagged_peaks
jungle_edge_mutated
legacy_frozen_ocean
lush_caves
meadow
mesa_plateau_mutated
mesa_plateau_stone_mutated
redwood_taiga_hills_mutated
redwood_taiga_mutated
roofed_forest_mutated
savanna_plateau_mutated
snowy_slopes
stony_peaks
pale_garden
These are valid vanilla biome identifiers that are never referenced by the vanilla biomes_client.json, and only exist as client_biome files in the more recent client_biome system.
Note:
It seems appropriate to include these biome identifiers and their water and fog settings in the vanilla biomes_client.json file, assuming it is not going to be deprecated ( ? )
2. Several 'biomes_client' biome identifiers are invalid when used in new 'client_biome's
Here's a complete list of the identifiers that exist within the vanilla biomes_client file, but are absent from the vanilla client_biome files, and when attempting to create these client_biomes manually, the biome IDs are marked as invalid by the game.
mega_spruce_taiga
mega_spruce_taiga_mutated
mega_taiga_mutated
mesa_mutated
and possibly:
default
Notes:
Since apparently the new biomes_client does not function anymore, it is expected for the new system to have a Default biome client that will be used as the default biome configuration, and for the new client_biome system to cover all previous existing biomes.
It could also be the case that some of these biomes (aside from default) are simply obsolete and are unsued leftovers in the old biomes_client even in latest Minecraft resource versions found at: aka.ms/resourcepacktemplate
I am unable to verify this and a word from the developers would be greatly appreciated.
Attachments
Comments 3
migrated
It seems the following biomes in biomes_client:
mega_spruce_taiga.client_biome
mega_spruce_taiga_mutated.client_biome
mega_taiga_mutated.client_biome
mesa_mutated.client_biome
no longer exist in game, so the identifiers are invalid when used in a client_biome.
If Biomes_client.json is going to be deprecated, this bug report is of little value, should client_biomes replace everything eventually.
The vanilla biomes_client.json has a comment at the top explaining that unlisted biomes use the default parameters. It includes a default. Therefore, there is no need to include every biome in biomes_client.json.
There is no reason to have client_biome files for deprecated biomes. I expected that world that is version-locked to an older version and does not update the deprecated biomes is going to be using biomes_client, not client_biome files.
I think this is working as intended.