OreSpawn 4 Terrain Dimensions

Terrain Dimensions

OreSpawn 4 documentation: OS4 index | Player guide | Legacy OS3 documentation

Exact fields for the installed build are documented in config/orespawn-guide/.

Standalone OreSpawn has no enabled terrain-replacement dimension. The Overworld is the conventional geology target used by full providers such as Mineralogy. Nether and End remain untouched unless a global/world profile explicitly enables them. Providers may automatically opt in only dimensions in their own namespace.

Biome palettes and dimension-material rules are separate from terrain replacement. They may target minecraft:overworld, minecraft:the_nether, minecraft:the_end, or a provider dimension without adding rock strata. Unconfigured dimensions keep their original biome source, aquifers, snow, and ice. OreSpawn wraps the biome source already installed by the dimension.

Each terrain_dimensions entry supplies replacement host blocks or tags and may restrict generation to explicit biome IDs or biome namespaces. With no biome restriction, all biomes in that dimension are eligible.

Rock entries may include a dimensions array. For backward compatibility, an entry without this field belongs only to minecraft:overworld. A custom dimension is disabled during baking if no valid eligible rocks resolve.

Ore rules may instead use the built-in dimension_selectors.orespawn:all_except_nether_end policy. It covers the Overworld and ordinary custom dimensions, but never the vanilla Nether or End. An explicit ore rule for a dimension takes precedence over the selector, even when the explicit rule is disabled.

Example:

"examplemod:crystal_caverns": {
  "enabled": true,
  "biome_namespaces": ["examplemod"],
  "biome_ids": [],
  "host_blocks": ["examplemod:base_rock"],
  "host_tags": []
}

OreSpawn resolves dimensions, hosts, tags, rocks, and biome filters before chunk generation. An unconfigured dimension performs one table lookup and immediately skips.