Java Edition field instrument

OlderCraft

Repair bench version core

Compatibility is a recorded fit, not a promise.

Pick a version. See what still connects.

Manual
GUIDES/BACK-UP-BEFORE-DOWNGRADING
Record
Java Edition
Edition
2.0.0

Repair procedure RP–01 World preservation

Back up before you go back

World saves upgrade forward: when a newer version opens a world, it converts chunks, entities, and metadata to its own format on load. There is no supported conversion back. Opening that world in an older version afterwards can corrupt it — sometimes visibly, sometimes as quiet chunk damage you find weeks later.

One-way conversion / preserve the original

Procedure04 steps

Make a real copy

  1. 01
    Close the game completely. A world copied while open can be internally inconsistent.
  2. 02
    Open your saves folder:
    • Windows%appdata%\.minecraft\saves
    • macOS~/Library/Application Support/minecraft/saves
    • Linux~/.minecraft/saves
  3. 03
    Copy the entire world folder somewhere outside saves — a dated archive like MyWorld-2026-07-14.zip beats a loose copy.
  4. 04
    Verify the copy opens: temporarily move it back under a different name and load it once, or at minimum check the archive lists level.dat and a populated region/ directory.

Bench rules / 02

Two rules that prevent most damage

  • One era per world. Give each version-era its own game directory in the launcher so an old installation cannot see your current worlds at all.
  • Copies play, originals rest. When experimenting across versions, only ever load the copy.

Servers: the same one-way rule applies to the server-side world/ directory. Snapshot it before any version change, and test the migration on the copy first — theoperator guide covers the rest.