Plugin updates are worth doing — they patch security holes, fix bugs, and add support for newer Minecraft versions. They're also where a happy server occasionally breaks, because an update can change a config format, bump a dependency, or drop support for your version. The fix isn't to avoid updating; it's to update safely. This guide is the flow that gets you the fixes without losing a weekend.
| At a glance | |
|---|---|
| You need | The Plugins page, the File Manager, and Backups |
| Plan | Any |
| Time | Ten minutes per update, done properly |
Back up first — always
Before you touch a single plugin, take a backup. On the free plan backups store to your own Google Drive; on premium they're on the node. This is the one step that turns "the update broke everything" from a disaster into a five-minute restore. Don't skip it because "it's just a small update" — those are the ones that surprise you.
⚠️ Heads up: A backup taken before the update is your rollback. A backup taken after something breaks just saves the broken state. Order matters.
Read the changelog before you download
Every update has release notes on the plugin's page (Modrinth, Hangar, CurseForge, or SpigotMC). Two minutes of reading saves an hour of guessing. Look for:
- "Breaking changes" or "config changes" — the update may rewrite or invalidate your settings.
- Minimum Minecraft version — an update might require a newer server than you run.
- Dependency bumps — "now requires Vault 1.x" or "needs the latest PlaceholderAPI" means you have to update those too.
- Data/format migrations — some updates change how the plugin stores player data; the notes will say if a one-time migration happens.
If the notes mention none of that, it's a low-risk patch. If they mention all of it, slow down.
The safe update flow
- Back up (above).
- Note your current versions — the Plugins page's My Addons view lists what you have installed, so you know exactly what you're moving from.
- Update one plugin at a time. Never update ten at once — if something breaks you won't know which. Search the plugin on the Plugins page and install the current build that matches your Minecraft version.
- Remove any leftover old jar. Two versions of the same plugin in
/pluginsis a classic breakage. After updating, open/pluginsin the File Manager and confirm there's only one.jarfor that plugin — delete the older one if both are present. - Restart and watch the console. The plugin should enable cleanly and, if its config changed, often log that it added new keys.
- Test the feature in-game — not just that the server started, but that the thing the plugin does still works.
- Only then move on to the next plugin.
| Stage | Do | Why |
|---|---|---|
| Before | Back up, read changelog, note versions | So you can roll back and aren't surprised |
| During | One plugin, remove old jar, restart | So a break points at one cause |
| After | Watch console, test in-game | So "it started" doesn't hide "it's broken" |
Minecraft version updates need matching plugins
When you update the server itself in the Version Changer, your plugins may need updating to match — a plugin built for an older version can fail on a newer one (and vice versa). Update the server first, then bring each plugin up to a build that supports the new version, one at a time. See Minecraft software and versions.
Rolling back a bad update
If an update misbehaves, you have two ways back:
- Restore the pre-update backup — the cleanest option, and exactly why you took it. You can do a Selective Restore to bring back just
/pluginsand the plugin's config folder if you don't want to roll back your whole world. - Reinstall the previous version — if you kept the old
.jar(renaming it toPluginName.jar.bakbefore replacing is a good habit), put it back and remove the new one. Watch for config incompatibility, since the new version may have already rewritten the config to a newer format — this is where the backup wins.
🎯 Good to know: The config the new version wrote may not load on the old version. That's why the backup — which holds the matching old config — is the more reliable rollback than just swapping jars.
Verify it works
After each update, the console shows the plugin enabling with no errors, /plugins lists it green, and the feature you rely on still works in-game. If all three are true, move to the next plugin.
Troubleshooting
- Server won't start after an update — likely a version mismatch or a leftover duplicate jar. Check
/pluginsfor two copies, confirm the build matches your Minecraft version, or restore the backup. See Diagnosing plugin conflicts. - Settings reset after updating — the new version rewrote the config in a new format. Compare against your backup's config and reapply your changes. See YAML without tears.
- Update needs a newer dependency — the console names it. Update that dependency too (still one at a time), then retry.
- New version needs a newer Minecraft version than you run — update the server in the Version Changer first, or stay on the plugin build that supports your version. See Minecraft software and versions.