Mineralogy 6 World Upgrades

World Upgrades

Mineralogy 6 documentation: M6 index | Player guide | Troubleshooting

Minecraft rewrites world data when a save is opened in a newer version. Treat an upgrade as a one-way operation and work on a copy.

Before opening the world

1. Close Minecraft and the server completely.
2. Make a full backup of the original save.
3. Create a second disposable copy for the first upgrade attempt.
4. Record the Minecraft, Forge, Mineralogy, OreSpawn, and other mod versions used by the source world.
5. Install the target versions of every mod that owns blocks or items in the save.
6. Read the release notes for the exact target file.

Never test an upgrade against the only copy of a world.

What Mineralogy can preserve

Modern Mineralogy retains:

• historical Mineralogy registry IDs;
• known renamed-ID aliases;
• compatibility paths for older saved block states;
• old Mineralogy blocks that now overlap vanilla rocks.

Mineralogy can preserve only content it owns. It cannot reconstruct a Base Metals block, machine, item, or fluid when the mod that owns that registry entry is missing.

Pre-flattening worlds

Minecraft 1.10 and 1.12 stored blocks using numeric registry snapshots and metadata. Modern Mineralogy ports include compatibility work for this old format.

The migration needs the old registry information before Minecraft's data fixer discards it. Some target versions retain a world-local sidecar so chunks that were not loaded during the first upgrade can still be interpreted later.

The exact migration implementation differs by Minecraft version. Use the release notes and exported guide for the target build, and verify the result in a disposable copy.

What to inspect after conversion

Visit representative locations containing:

• natural Mineralogy rock;
• bricks and polished blocks;
• slabs in different orientations;
• stairs and walls;
• reliefs and lamps;
• rock furnaces with items and active timers;
• renamed historical materials;
• blocks from every other content mod in the save.

Check inventories, block orientation, furnace contents, and large builds, not only whether the world reaches the title screen.

Old and new terrain

Existing chunks keep their saved blocks. Newly generated chunks use the current OreSpawn world profile.

That can create a visible boundary when the old and new generation styles differ. This is expected and is not fixed by changing Mineralogy's content configuration.

OreSpawn does not retro-generate modern rock strata through existing terrain.

Moving to a server

After the upgraded copy has been checked:

1. stop the server;
2. copy the whole world;
3. preserve its serverconfig directory;
4. install the same mod set and versions;
5. start the server and inspect the log;
6. keep the original backup until the upgraded world has been played and backed up successfully.

If the upgrade fails

Stop and return to another copy of the original world. Do not repeatedly open the damaged test copy with different mod sets.

Collect:

• the source and target version lists;
• latest.log;
• the first relevant exception;
• missing-registry messages;
• the affected registry IDs;
• whether the same failure occurs on a fresh copy.

Report the issue through the Mineralogy issue tracker.