Direct answer

Updating Forge is a Minecraft version, loader build and modpack migration, not merely a JAR replacement. Use a clean staging directory for major version changes.

Step-by-step procedure

  1. Back up world/, mods/, config/, defaultconfigs/, scripts and any external data.
  2. Download a Forge installer for the target Minecraft release from the official project, then follow its server-install mode for that build.
  3. Use the run scripts and JVM settings generated by the installer; do not assume every modern Forge installation launches with java -jar forge.jar.
  4. Install corresponding mod versions, start staging, read missing-mod errors and test representative modded blocks/entities before migration.

Common mistakes and trade-offs

Removing content mods or downgrading a world after upgrading can permanently lose block/entity data. Never use a production save for trial upgrades.

How to verify it worked

Record the Minecraft version, Forge build, Java version and mod list that passed; only then schedule a production maintenance window.

Version and platform differences

Installer arguments and generated file names change across Forge generations; consult the download’s matching installer instructions.

Official references

These sources were checked for the current MSH revision. Version-sensitive details should always be confirmed against the project documentation for the release you run.

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