Direct answer

Back up the complete world and server before opening it in Java Edition 26.3. The release sets the data pack version to 121.0 and changes multiple data-driven formats. PaperMC warns that after a world is upgraded to 26.3, it cannot safely be downgraded to an older version. Test datapacks, world generation and custom content using a clone first.

What to review in 26.3

  • Check pack.mcmeta and all datapack version requirements against the official release notes; do not simply change a number and assume data formats are compatible.
  • Review relevant modified registries, configured features, density functions and custom biome/spawn definitions if your pack uses them. The full release notes list the exact schema changes.
  • Examine any custom signs that rely on vanilla click events: new sign data uses allow_op_features defaulting to false.
  • Check datapack function errors, registry warnings and world-generation messages in logs. A successful boot alone does not prove all dimensions will generate correctly.

Safe staging upgrade

  1. Record the current server JAR, Java runtime, plugin/mod versions and datapack list.
  2. Stop the server cleanly and make an offline copy of all world and dimension folders, datapacks/, plugins/mods and configurations.
  3. Verify the backup on a separate device or location and make a second copy for testing.
  4. Start the test copy with a version-compatible 26.3 server build and Java runtime. Do not allow the production server to open the test copy.
  5. Inspect both existing chunks and newly generated terrain in relevant dimensions; test structures, custom loot, recipes, features and functions.
  6. Update incompatible datapacks from their maintainers or use documented migration instructions. Repeat testing before changing production.

Rollback if content breaks

Stop the new server and restore the unopened pre-upgrade backup together with its compatible old server software and datapacks. Do not point an old JAR at a world already converted by 26.3. If a datapack lacks a 26.3-compatible release, delaying production upgrades is safer than guessing at migration details.

Paper, Folia and modded differences

PaperMC migration and API changes can add extra compatibility requirements beyond vanilla datapack schema changes. Folia regionized plugins and Fabric/NeoForge/Forge mods have separate compatibility concerns. Test your exact server stack, not an unrelated Vanilla-only world.

Official references

Official sources for version-sensitive details. Check the newest release notes before changing a production server.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000