Keeping Minecraft plugins updated can provide bug fixes, compatibility improvements, security fixes, and support for newer Minecraft versions.
This guide explains how to safely update plugins on a Down Side Hosting Minecraft Java server.
Before replacing any plugin, check:
Important: Do not automatically assume that the newest plugin release is compatible with your current Minecraft server.
Before updating plugins, create a backup of your Minecraft server.
At minimum, important data can include:
Some plugins store important information outside of the plugin JAR itself.
A backup gives you a way to restore the server if an update causes problems.
Before downloading an update, determine which version of the plugin is currently installed.
You can often find the version:
For example:
ExamplePlugin-4.2.1.jar
Do not rely only on the filename, because some developers do not include the version number in it.
Check the plugin developer's release notes before updating.
Look for information about:
This is especially important when upgrading across several plugin versions at once.
Download the plugin from a trusted source.
Common sources include:
Plugins are normally distributed as:
.jar
For example:
ExamplePlugin-4.3.0.jar
Open your Down Side Hosting server panel.
Select your Minecraft server and click:
Stop
Wait until the server has completely shut down.
Avoid replacing plugin files while the server is running.
Open the Files section of your Down Side Hosting server panel.
Navigate to:
plugins/
You should see your installed plugin JAR files.
For example:
plugins/
ExamplePlugin-4.2.1.jar
Vault.jar
LuckPerms.jar
Locate the old plugin JAR.
For example:
ExamplePlugin-4.2.1.jar
Remove or rename the old JAR and upload the new version:
ExamplePlugin-4.3.0.jar
Afterward, make sure you do not accidentally have both versions installed.
For example, avoid:
plugins/
ExamplePlugin-4.2.1.jar
ExamplePlugin-4.3.0.jar
Having multiple versions of the same plugin can cause startup errors or unpredictable behavior.
Many plugins have a separate data folder.
For example:
plugins/
ExamplePlugin-4.3.0.jar
ExamplePlugin/
The folder may contain:
Normally, you should replace the JAR but keep the plugin's data folder.
Only remove configuration or data files if the plugin developer specifically tells you to do so.
An updated plugin may require a newer version of another plugin or library.
For example:
Vault ProtocolLib PlaceholderAPI LuckPerms
Check the plugin's documentation for required dependencies.
If necessary, update those dependencies as well.
Do not update dependencies blindly. Make sure the new dependency version is compatible with your other installed plugins.
Return to your Down Side Hosting server console.
Click:
Start
Watch the console carefully during startup.
Look for the plugin name and messages such as:
Enabled Loaded ERROR WARN Exception Could not load
A server reaching a normal startup message does not always mean every plugin loaded correctly, so review the console for plugin-specific errors.
After the server starts successfully, connect using:
dsh.network:YOUR_PORT
Replace YOUR_PORT with your assigned server port.
See:
How to Connect to Your Down Side Hosting Minecraft Java Server
Test the important features of the updated plugin.
For example:
Watch the console while testing the plugin.
Some errors only appear when a player uses a command or feature.
Look for:
ERROR WARN Exception
and messages containing the plugin's name.
For a small server with only a few plugins, updating several together may be manageable.
For larger or important servers, updating plugins in smaller groups can make troubleshooting much easier.
For example:
If something breaks, you will have a much smaller list of possible causes.
If the plugin fails after an update:
If the new plugin changed configuration files or database data, restoring only the old JAR may not always be enough.
That is why creating a full backup before updating is important.
If the server fails to start after a plugin update, check the console.
Common causes include:
If the server worked immediately before the update, restoring the backup or previous plugin version can help confirm whether the update caused the problem.
Some plugins only support specific Minecraft versions.
For example, a plugin built for a newer Minecraft release may not work correctly on an older server.
Download the plugin version intended for your Minecraft version.
Do not assume:
Newest plugin version = correct plugin version
The correct version is the newest release that supports your actual server environment.
Some plugin updates add, remove, or rename configuration options.
Before manually copying an old configuration over a newly generated one, read the plugin's documentation.
Sometimes it is better to:
This can prevent outdated configuration options from causing errors.
Your Minecraft server software and plugins are related, but they do not always need to be updated at the same time.
Before changing your server software, verify that your important plugins support the new version.
See:
Paper vs Purpur vs Spigot: Which Minecraft Server Should You Use?
Sometimes, but use caution.
A newer plugin version may modify:
An older version may not understand the newer data format.
If you need to roll back, restoring the backup made before the update is usually safer than simply replacing the new JAR with an old one.
You do not necessarily need to install every update immediately.
You should pay particular attention to updates that contain:
For major updates, read the release notes and make a backup before installing them.
If you have not installed the plugin yet, see:
How to Install Plugins on a Down Side Hosting Minecraft Server
Down Side Hosting supports Minecraft Java servers using Paper, Purpur, Spigot, and other supported server configurations.
Customers have access to server files, console controls, backups, configuration files, and plugin management through the server panel.
Minecraft Java hosting starts at $2/month.
View Minecraft Java Server Hosting
Contact Down Side Hosting Support