Pretty much the title, I've been trying to load a custom biome for a pretty good little while and it takes an incredibly long time to load (which is probably on my end) but it won't load any of my custom biome colors. I'm not sure why this is, as one of my biomes does seem to work. Attached is the Datapack with both biomes to test out.
Not sure what to do here, but this bug needs to be fixed because these custom biomes will be integral to my server..
It seems that people are getting confused that I'm trying to load these as dimensions, I'm trying to load these as overworlds.
Linked issues
Attachments
Comments 5
The biome still doesn't load the colors though, which is the main issue. I'm not sure where I've gone wrong, or if I have.
Just to clarify, this issue is caused by doing `"type": "minecraft:fixed"` in the biome source for the dimension. minecraft:fixed is the single biome provider and it is broken for json biomes by causing the client to spam unknown biome id: -1 and thus, treat the biome colors as if it is an ocean biome. The workaround is to use "type": "minecraft:multi_noise" biome provider and give it only a single biome as multi_noise handles the json biomes correctly and safely. Here's a workaround datapack of what I mean. You can also use this datapack to test minecraft:fixed in a reproducable manner as well by switching multi_noise to fixed and change the entries to what minecraft:fixed uses
[media]
A buddy of mine tried running the datapack, the Dagobah biome specifically, and it wouldn't even generate for him, it crashed and he got an error Received invalid biome id: -1. It loaded for me but none of the colors loaded.