Mineralogy 6 Modpack Guide

Modpack Guide

Mineralogy 6 documentation: M6 index | Configuration | OreSpawn provider

Mineralogy 6 is ready to use with its packaged provider. A pack does not need to write a second generator or copy the provider before Mineralogy will work.

Recommended setup

1. Install matching Mineralogy 6 and OreSpawn 4 builds.
2. Start the game once so both exported guides are available.
3. Create a test world with Recommended Defaults.
4. Inspect the geology and content before changing the profile.
5. Make pack-wide worldgen changes in OreSpawn.
6. Trim optional registered content separately in mineralogy-common.toml.
7. Create another fresh world for final validation.

Start with the authored provider

Mineralogy already declares:

• its 32 rock choices;
• the four rock families and depth preferences;
• three mineral ores;
• its crude-oil deposit;
• Overworld hosts;
• modern stable-layer defaults;
• vanilla block aliases.

Do not duplicate those entries in another provider just to make them visible. Use a complete Mineralogy override only when the pack intentionally needs to replace the supplied declaration.

Coordinate other content mods through OreSpawn

Other mods can publish their own OreSpawn providers. OreSpawn resolves their rules into the same world profile.

For example, a metal mod can own its ore block and declaration while using Mineralogy rock families as valid hosts. Mineralogy does not need to own that metal, and the metal mod does not need to replace Mineralogy's terrain.

Use provider ownership and stable names so two mods do not claim the same rule ID.

Content versus worldgen

Use mineralogy-common.toml for:

• optional relief, slab, stair, wall, furnace, brick, and polished families;
• broad cobblestone behaviour;
• recipe and content choices;
• old-world patching.

Use OreSpawn for:

• formations and geology mode;
• rock weights and depth preferences;
• ore abundance, patterns, hosts, biomes, and dimensions;
• oil deposits;
• templates and world profiles;
• optional retrogen.

Do not try to adjust ore frequency with a Mineralogy content flag.

Useful compatibility tags

Mineralogy publishes:

• mineralogy:rocks;
• mineralogy:standard_rocks;
• mineralogy:rocks/sedimentary;
• mineralogy:rocks/metamorphic;
• mineralogy:rocks/igneous;
• mineralogy:crafting_materials/<rock>.

Use Forge or vanilla stone and cobblestone tags for recipes that genuinely accept any compatible stone. Use Mineralogy's narrow tags for material-specific outputs.

Trimming registrations

Large legacy packs can benefit from disabling optional decorative families. Choose these flags before the pack's first public world.

Changing registration flags after a world contains those blocks can create missing mappings. Back up and test the exact upgrade path if a released pack must remove content.

Pack defaults and templates

Use config/orespawn-worldgen.json for installed-pack defaults. Use an OreSpawn template when players should be able to choose between named geology styles at world creation.

Dedicated servers can use default_template for new worlds. Once a world exists, its profile in serverconfig is authoritative.

Testing a pack

Check at least:

• Mineralogy and OreSpawn load on both client and dedicated server;
• /orespawn status reports Mineralogy active;
• a new Overworld contains several rock families;
• sulfur, phosphorous, and nitrate generate;
• oil follows the intended biome and host rules;
• optional content flags match the recipe and registration set;
• other providers do not duplicate Mineralogy IDs;
• missing optional biome mods do not break provider baking;
• a copied world retains its serverconfig profile.

Do not judge generation from one cave or one chunk. Regional geology and rare deposits need a broader sample.

Documentation to ship

Pack maintainers should keep links to:

• this wiki for readable Mineralogy guidance;
• config/mineralogy-guide/ for the installed Mineralogy declaration;
• config/orespawn-guide/ for exact worldgen fields and schemas;
• the pack's own notes describing deliberate overrides.