Mineralogy 6 Troubleshooting

Troubleshooting

Mineralogy 6 documentation: M6 index | Player guide | Configuration

Start with the exact guides exported by the installed jars:

config/mineralogy-guide/
config/orespawn-guide/

Then check logs/latest.log. The first provider, registry, or JSON error is usually more useful than later follow-on messages.

Mineralogy says OreSpawn is missing

Mineralogy 6 requires a compatible OreSpawn 4 build for the same Minecraft and Forge version.

Do not install an OS3 jar with Mineralogy 6. Do not mix files built for different Minecraft versions.

A new world contains only vanilla stone

Check:

1. Mineralogy and OreSpawn are both loaded.
2. /orespawn status reports the Mineralogy provider as active.
3. The world's terrain-replacement setting is enabled.
4. The Overworld terrain-dimension entry has valid hosts.
5. You are inspecting newly generated chunks.
6. A provider override has not replaced or broken the bundled declaration.

If config/mineralogy-orespawn.json exists, temporarily validate it against the matching schema. Do not expect OreSpawn to ignore a malformed authoritative override and fall back silently.

I changed the profile but the old area did not change

Profile changes affect newly generated chunks. Mineralogy rock strata are not retro-generated through old terrain.

Travel to unexplored chunks or make a fresh test world.

I disabled a content family and blocks disappeared

Mineralogy's GENERATE_* settings control registration and recipes. Disabling a family that already exists in a world can create missing mappings.

Restore the previous setting and reopen another backup. Choose registration flags before public world creation whenever possible.

Mineralogy ores appear twice

Check whether:

• another mod still runs its own generator for the same block;
• the same rule ID is declared by two providers;
• an old datapack or provider override duplicates the bundled rules;
• optional vanilla-ore management has been confused with Mineralogy's three provider-owned ores.

Use /orespawn status and inspect the merged world profile.

I cannot find crude oil

The reference oil rule is deliberately uncommon and underground. It favours ocean biomes, compatible sedimentary hosts, and Y -48 through 48.

Check:

• place_fluid_deposits is enabled;
• Mineralogy's provider is active;
• the world profile still contains the crude-oil rule;
• the dimension and biome filters match;
• you are searching newly generated chunks;
• the deposit is below solid rock rather than exposed at the surface.

One small search area is not enough to prove a rare regional feature is missing.

A server generates different geology

Copy the complete world, including:

<world>/serverconfig/orespawn-worldgen.json

Install the same mod set on the server. Compare the client and server Minecraft, Forge, Mineralogy, OreSpawn, and provider-mod versions.

A legacy world has missing blocks

Return to a fresh copy of the original world and read World Upgrades.

Make sure every mod that owns content in the old save is installed. Mineralogy cannot recover registry entries belonging to a missing third-party mod.

Useful OreSpawn commands

• /orespawn status shows active and inactive providers.
• /orespawn reload reloads providers and the active profile.
• /orespawn dump-biomes writes discovered biome information.
• /orespawn retrogen [radius] queues bounded supported retrogen for loaded chunks.

Back up before retrogen. Retrogen does not add Mineralogy rock formations to existing chunks.

Reporting a problem

Include:

• Minecraft version;
• Forge version;
• Mineralogy version;
• OreSpawn version;
• complete mod list;
• whether the world is new or upgraded;
• whether a provider override exists;
• the first relevant error from latest.log;
• steps that reproduce the problem in a fresh test world.

Use the Mineralogy issue tracker for Mineralogy content, registry, recipe, model, or provider-declaration problems. Use the OreSpawn issue tracker for engine, profile, placement, schema, or OreSpawn UI problems.