For Paper / Spigot server admins
Update the plugin.
Keep your settings.
New plugin versions ship new config.yml files. Cobblekit merges the new default with yours:
new options and their comments come in, your values stay, and anything that needs a decision is flagged.
- your settings kept
- new options added
- conflicts flagged
-
1
Which plugin?
-
2
From which version to which?
Not on Modrinth or Hangar (premium plugin)? Drop both jars instead:
-
3
Your config files
Result
Tested, not promised
How it compares on real plugins
On a real server
What it cannot do
Method and plugin list
How does the merge decide?
It compares three files: the default of your current version, your file, and the default of the new version. If you never changed an option, you get the new default. If you changed it and the plugin did not, your value stays. If both changed it, it is a conflict: your value is kept (or the new one, with the checkbox) and it is listed so you can check. Options you added yourself, like your own kits, are kept; options you deleted stay deleted.
Are my files uploaded?
No. Everything runs in this page. The only network requests download the plugin jars from Modrinth or Hangar.
Can I do this on my server directly?
Yes, with the cobblekit merge command line tool:
cobblekit merge plugins/EssentialsX-2.19.6.jar --write merges every config file of the plugin and
backs up the originals.