Mineralogy 6 OreSpawn Provider

OreSpawn Provider

Mineralogy 6 documentation: M6 index | Configuration | Modpack guide

The exact provider used by an installed build is exported to config/mineralogy-guide/examples/mineralogy-provider.json.

Mineralogy packages its OreSpawn provider at:

data/mineralogy/orespawn/provider.json

This declaration tells OreSpawn which world-generation content Mineralogy owns. It contains data, not callbacks into Mineralogy's generation code.

Current reference provider

The current Mineralogy 6 reference provider contains:

• schema version 3;
• provider mod ID mineralogy;
• provider revision 3;
• 32 enabled rock rules across four families;
• sulfur, phosphorous, and nitrate ore rules;
• Overworld stone and deepslate replacement hosts;
• stable-layer profile defaults;
• one provider-owned crude-oil deposit;
• aliases from Mineralogy andesite, basalt, diorite, granite, and tuff to the matching vanilla blocks for new terrain.

The old Mineralogy blocks remain registered. A worldgen alias changes the default output selected for newly generated terrain; it does not rename blocks already saved in a world.

The canonical reference declaration is available in the Mineralogy source.

Ownership

Provider-owned IDs begin with clear names such as:

mineralogy:rock/mineralogy/limestone
mineralogy:ore/mineralogy/sulfur_ore
mineralogy:fluid_deposit/crude_oil

Stable IDs matter because existing world profiles keep their own choices. Renaming an ID is a migration, not a cosmetic edit.

Mineralogy does not declare OreSpawn's optional vanilla ore presets. Those are engine-owned features and should not be duplicated in the Mineralogy provider.

Pack override

To replace Mineralogy's bundled declaration for a pack, provide a complete file at:

config/mineralogy-orespawn.json

The external file is authoritative when present. It is not a small patch file.

Validate the whole override against the schema supplied by the installed OreSpawn build. If the override is malformed, incomplete, mismatched, or conflicts with another provider, OreSpawn marks the Mineralogy provider inactive instead of silently combining two different definitions.

That fail-closed behaviour makes pack errors visible and prevents duplicate or partly applied generation.

Existing worlds

An existing world uses its self-contained OreSpawn profile.

A newer provider can introduce newly added IDs, but it does not overwrite values already established by the world. Removed provider IDs can remain in a profile as orphaned entries so user choices are not silently repurposed.

Provider changes therefore do not automatically redraw old terrain or reset a world's settings.

Validation checklist

Before shipping a provider override:

1. Start with the exported example from the exact installed Mineralogy build.
2. Validate it with the matching OreSpawn schema.
3. Keep every provider-owned ID stable.
4. Confirm all referenced blocks, fluids, tags, biomes, and dimensions exist.
5. Check /orespawn status for an active Mineralogy provider.
6. Generate a fresh test world.
7. Inspect rocks, all three ores, and any enabled crude-oil rules.
8. Test with every optional compatibility mod both present and absent.

For the provider contract, fields, lifecycle, and API, use the OreSpawn Worldgen Providers guide and the guide exported to config/orespawn-guide/.