Mineralogy 6 Player and Server Guide

Player and Server Guide

Mineralogy 6 documentation: M6 index | Rocks and formations | Troubleshooting

The exact guide for an installed build is exported to config/mineralogy-guide/.

Installing

Mineralogy 6 needs both:

1. a Mineralogy 6 jar for the exact Minecraft and Forge version;
2. a compatible OreSpawn 4 jar for the same Minecraft and Forge version.

Install both mods on clients and servers. Use the CurseForge Files tab and the dependency information on the selected file rather than mixing builds from different Minecraft versions.

A world containing Mineralogy blocks should not be opened without Mineralogy.

Creating a world

1. Open OreSpawn World Generation from the Create World flow.
2. Choose Recommended Defaults for Mineralogy's authored starting point.
3. Optionally choose Sky or Cyano and adjust formations, rocks, ores, deposits, geomes, or advanced settings.
4. Open Help & Guide whenever a control is unfamiliar.
5. Press Done and create the world normally.

Mineralogy supplies the materials and provider defaults. OreSpawn validates the finished choices and saves a complete profile inside the new world.

What to expect underground

Sky is the recommended modern engine. It combines broad geological regions called geomes with rock families, depth preferences, and continuous formations. A cave can stay within one formation for a while, cross a boundary, or expose different families as it descends.

Cyano (Legacy) keeps the older Mineralogy-style layer engine. It is useful for players who prefer that look or for worlds already using it.

Read Rocks, Geomes, and Formations for the full explanation.

Existing chunks

Ordinary world-profile changes affect newly generated chunks. Existing terrain is not rewritten with new rock strata.

OreSpawn can perform bounded ore and flat-bedrock retrogen when deliberately enabled. Rock formations are not retro-generated through existing builds and caves.

Dedicated servers

Every world stores its complete profile at:

<world>/serverconfig/orespawn-worldgen.json

Copy the whole world, including that file, to the server. Install the same required mods and versions. Blocks from a missing content mod cannot be generated or recovered by OreSpawn.

For a newly created dedicated-server world, the installed pack defaults and the selected default_template are used before the per-world snapshot is written.

Important files

Location	Purpose
config/mineralogy-common.toml	Mineralogy content, recipes, drops, and compatibility options
config/orespawn-worldgen.json	Installed-pack defaults for new worlds
<world>/serverconfig/orespawn-worldgen.json	One world's complete worldgen profile
config/mineralogy-orespawn.json	Optional pack override for Mineralogy's provider
config/mineralogy-guide/	Exact Mineralogy guide and provider example
config/orespawn-guide/	Exact OreSpawn guide, examples, and schemas

Restart after changing mineralogy-common.toml or provider JSON. Do not disable content that already exists in a world unless missing registrations are an understood part of the plan.

Moving or sharing a world

When copying a world:

• copy the entire save, not selected region files;
• keep its serverconfig directory;
• install every mod that owns blocks or items in that save;
• use matching Minecraft, Forge, Mineralogy, and OreSpawn builds;
• back up the source before opening it in a newer Minecraft version.

Read World Upgrades before moving a legacy Mineralogy world to a modern version.