OreSpawn 4 Troubleshooting

Troubleshooting

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

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

Provider remains inactive

Check that the provider mod is loaded, file name and provider_modid match, provider_revision is positive, provider rule IDs use its namespace, all output blocks resolve, all pattern codecs decode, and every enabled ore or terrain dimension has hosts. A malformed override deliberately prevents fallback to packaged or API declarations.

OreSpawn installed alone does nothing

That is the intended passive default. Install a provider such as Mineralogy, add a provider file, or explicitly configure rocks/ores and terrain dimensions.

Custom terrain does not appear

Confirm the dimension is enabled in terrain_dimensions, its hosts resolve, at least one enabled rock includes that dimension, and biome restrictions match. OreSpawn does not replace Nether or End terrain by default.

A custom biome does not appear

Confirm its registry ID resolves, its palette targets the intended dimension, the palette scope includes the source biome namespace, and the placement's temperature/downfall ranges match. similar_biomes are optional comparisons; missing IDs are ignored. Every ID in required_similar_biomes must exist or OreSpawn deliberately skips that placement and logs one setup warning.

If no palette matches, OreSpawn leaves the biome supplied by the wrapped vanilla or modded biome source unchanged. Use /orespawn dump-biomes to inspect the IDs available in the current installation.

Aquifer or surface materials do not change

Confirm an enabled dimension_materials rule targets the exact dimension and uses registered fluid-block IDs for aquifers. Surface substitutions are tied to enabled palette entries and affect newly generated terrain only. Features or structures that explicitly place blocks after terrain generation are not global material replacements.

Changes do not affect terrain

Restart after editing JSON or changing provider/API declarations. Travel to new chunks. Ore retrogen and flat-bedrock retrogen must be explicitly enabled; geological strata are never retrogened.

Server differs from a client test world

Copy <world>/serverconfig/orespawn-worldgen.json, not merely the global client config. Install the same provider mods and blocks on the server.

Native ores duplicate

Provider mods suppress native generation only after OreSpawnApi.isOreTakeoverActive(modid) is true. Keep native generation for PENDING and INACTIVE. For pack-wide vanilla or modded suppression, review manage_vanilla_ores and suppress_all_ore_features carefully.

Operator diagnostics

• /orespawn status shows active mode, rule/provider counts, and retrogen queue.
• /orespawn reload reloads providers and the active world profile.
• /orespawn retrogen [radius] queues currently loaded chunks only.
• /orespawn dump-biomes writes config/orespawn-biomes.txt.