Direct answer
PaperMC announced on September 26, 2026 that it was preparing to merge most options currently spread across Bukkit, Spigot and Paper configuration files. The team planned for the work to land in 26.4. As of October 25, 2026, do not treat this proposed merge as a released configuration schema or rename any files based on predictions.
Why the change matters
Server operators currently manage settings across multiple files. Consolidation may change where options are documented or stored and can affect panels, config deployment scripts and tutorial screenshots. Until a stable release and migration documentation exist, exact keys, defaults and behavior remain uncertain.
A no-risk preparation checklist
- Inventory your current Bukkit, Spigot and Paper configuration files and record the Paper build number.
- Back up all configuration files and the world before testing any major Paper version.
- Document site-specific overrides, panel-generated settings, automated scripts and file paths they expect.
- When official 26.4 builds and migration notes arrive, test a copy of the server and compare effective settings before upgrading production.
- If an option moves, use only the new key and location confirmed by that release. Keep a dated pre-upgrade backup for rollback.
Do not do these things yet
- Do not delete
bukkit.ymlorspigot.ymlbecause a merge is planned. - Do not publish speculative configuration keys as real 26.4 options.
- Do not assume a fork such as Purpur or Leaf will mirror every migration detail identically.
How to verify on release day
Use the stable 26.4 PaperMC announcement and its linked configuration migration issue. Check startup warnings, plugin compatibility, behavior under load and generated files on a staging copy before a production switch.
Official references
Official sources for version-sensitive details. Check the newest release notes before changing a production server.
Related articles
Help us improve this article
Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.