How to Add TerraBlender Regions to a Custom Dimension

Why Dimensions Need Extra Setup

TerraBlender's overworld injection is automatic once biome mods register their regions, but other dimensions (the Nether, the End, or modded dimensions) do not receive those regions unless the dimension's biome source is built to accept them. If you are a datapack or mod author, you need to wire the region list into the dimension's biome source yourself.

Steps for Datapack and Mod Authors

1. Locate the dimension's biome source definition in your datapack's dimension JSON or in your mod's dimension registration code.

2. TerraBlender exposes a multi-noise biome source parameter list. Add the region entries you want this dimension to use, referencing the region keys registered by the biome mods you depend on.

3. If you are writing a mod, call TerraBlender's API to fetch the registered regions for the dimension type you are targeting, then pass that list into your biome source constructor.

4. Make sure your dimension's noise settings are compatible — regions rely on multi-noise parameters, so a flat or single-biome source will ignore them.

5. Test by creating a new world and travelling to the dimension; check that the expected biome families appear in the correct climate bands.

Common Pitfalls

Forgetting to declare the biome mod as a dependency means the region keys will be missing at load time and the dimension may fall back to vanilla biomes. Always test with only the required mods enabled first.