Keep your existing world on its working version until the software and add-ons you need support the target release. A successful startup is not enough: check a real join and the features your friends use.
What changed in the game
The update adds the Dappled Forest, poplar trees, abandoned camps and camping-themed items. It also includes technical changes. See Mojang’s official Java 26.3 notes for the full list. For a shared world, decide whether the new content matters more than keeping your current setup working this week.
Check your server stack, not just Minecraft
Write down the game version, server software and installed add-ons before changing anything. Check the download page and release notes for the exact target version. A Java release announcement does not certify a Paper build or every plugin.
For Fabric, the project’s 26.3 announcement asks players to give mod authors time to update. A compatible loader does not make an older mod compatible. Check each mod’s game version, loader and dependencies, including the client pack your friends use.
If Bedrock players join through Geyser, verify the installed build’s supported protocols separately. Our Bedrock update checklist explains what to collect before changing the server.
When to update, and when to wait
- A new, unmodified test world is a useful place to try the release if your selected server software offers it.
- For an established plugin world, wait if a plugin you rely on has no compatible release or its author reports a blocking problem.
- For a modpack, follow the pack author’s supported combination rather than mixing individual updates.
On ChunkArc, use the versions actually offered by Manage. This article is not a promise that 26.3 is available for every software option.
Before the first start on a new version
Save a backup of the world, server configuration and add-on data. Keep a separate copy outside the hosting account. Paper’s update instructions warn against replacing running JARs and recommend watching startup logs.
Stop the server before replacing its software. Do not delete the world to fix a compatibility error. Treat an older-version restore as a recovery from the saved pre-update copy, not a promise that a world opened on a newer version will downgrade safely.
What to test before inviting everyone
- Read the first startup errors, not only the final status.
- Join with the intended Java version and test saving, inventory and any important plugin commands.
- For modded play, use the agreed client pack. If you support Bedrock, make a separate Bedrock join.
- Stop and start once more, then check that the same world and progress remain.
If a step fails, record the version and first relevant error. Use the plugin troubleshooting guide or connection checklist instead of reinstalling the server at random.
Official sources
Sources checked: 30 September 2026. Documentation-based advice, not a compatibility test of every build, plugin or server.
Continue with your goal
All Minecraft updates · Ideas for your server · Practical guides