GuidesOnly show guides for your app
GuidesGuidesUpdates fix bugs and security holes — and occasionally break your config or your world. Here's the back-up-first flow that gets the fixes without the drama, plus how to roll back when an update goes wrong.
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 |
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.
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:
If the notes mention none of that, it's a low-risk patch. If they mention all of it, slow down.
/plugins is a classic breakage. After updating, open /plugins in the File Manager and confirm there's only one .jar for that plugin — delete the older one if both are present.| 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" |
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.
If an update misbehaves, you have two ways back:
/plugins and the plugin's config folder if you don't want to roll back your whole world..jar (renaming it to PluginName.jar.bak before 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.
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.
/plugins for two copies, confirm the build matches your Minecraft version, or restore the backup. See Diagnosing plugin conflicts.