-
-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: spawn biome json files are broken if using with biome mods. #5039
Comments
checked myself, the tags work fine i did notice that terraliths deep caves cause problems with certain features
normally this would look like this
|
Thanks for the reply. but if I use |
is_desert probably would probably work if you add the terralith cave biomes to it |
Adding terralith:cave/deep_caves into is_desert then using forge:is_desert as spawn seems to make the roosts spawn in every biomes. |
the problem is terralith worldgen and how biomes get recognized when its present might need to make a custom one to check surface biome with a fitting world height |
Sorry if I sound stupid, but in that case shouldn't this work? Assuming that the roosts are spawning underground making on-ground roosts not spawning? (deep_caves is in is_underground)
|
thing is some of these caves are generic, like deep_cave |
I will plan on rewriting how caves will be generated in future releases so they look at the overworld biome to decide where to generate to circumvent this issue. |
- fixed worldgen with terralith (and maybe others) - fixes #5039
What happened?
With mod Terralith.
Tested with "Generate Dragon Roost Chance" = 1 and with fire_dragon_biomes.json
Config examples that spawns:
Config examples that don't seem to spawn at all:
BIOME_TAG forge:is_desert
BIOME_TAG forge:is_plains
Seems that all tags that doesn't have /overworld at the end doesn't work.
If using without Terralith BIOME_TAG forge:is_desert works as intended.
Minecraft Version
1.20.1
Ice and Fire version
alpha 7
Citadel version
2.4.9
Relevant log output
Other Information
The text was updated successfully, but these errors were encountered: