If Paper starts but a plugin command fails, or the server began crashing after an update, do not delete JARs or plugins folders at random. Preserve the original state, read the first useful error in the log, and test plugin interactions on an isolated copy.
This guide covers Minecraft Java Edition and Paper. Panel labels and file locations depend on your host. Plugins have broad access to the server machine, so use trusted sources and keep plugin configuration and data with the world backup.
Preserve the original state#
Record the exact Minecraft, Paper, Java, and recently changed plugin versions. Save the error text and when it first appeared. If the server is running, stop it cleanly from the console with stop and wait for the process to exit. A plain copy of an active world can miss the latest changes.
Make a complete, separate copy of the server directory: worlds, server.properties, plugin configurations and JARs, local databases, and plugin data files. Check that the copy contains all three dimensions and is readable only by administrators. Some plugins store data in external SQL databases, Redis, or web services; inventory those connections separately. Do not point a test instance at a production database, send real webhooks, or run two copies with the same server identity.
If the server runs on your VPS, Nexardo can help you manage your own infrastructure. It does not replace an independent backup of your world and plugin data.
Check the log and versions first#
Open logs/latest.log and find the first plugin-related error, not just the last lines before shutdown. Paper's official plugin troubleshooting guide also starts with the log. Check that each JAR is actually a Paper/Bukkit plugin, downloaded completely, and intended for your server version. A Fabric or Forge mod cannot run in Paper's plugin folder.
The server-console command plugins lists loaded plugins; /version PluginName helps check a specific plugin version. A green status means it loaded successfully, but it does not prove that every command or feature works. Paper also provides /paper dumpplugins for dependency, load-order, and class-loader diagnostics, as described in its command reference.
Separate likely causes before calling something a conflict:
- A missing dependency is named near the beginning of the log: install a compatible version of that dependency.
- Paper reports
Invalid plugin.yml: check that the file is not a mod, an HTML error page, or an incomplete download. - An ambiguous plugin name is reported: two JARs for the same plugin remain in
plugins; keep one chosen release. UnsupportedClassVersionErrorpoints to a mismatch between Java and the server's requirements.- The problem started after a Paper update: check the plugin's supported versions and its first relevant stack trace, especially when it manages worlds or chunks.
Do not use /reload as a test. Paper warns that reloading is known to cause plugin issues. Fully stop and restart the test server after each change.
Reproduce the issue on a copy#
Create a separate directory and configuration for the test instance. Keep public players out: bind it locally or block its port with a firewall. Separately disable or replace connections to production databases, webhooks, payments, email, and other external integrations. Otherwise an experiment may change live data even if the world itself was copied.
Start with an unchanged copy and check whether the same symptom occurs. If it appeared after adding one plugin, disable only that plugin on the test copy and repeat the same action. If the error disappears, check compatibility, required dependencies, settings, and Java version, then send the author a small relevant log excerpt and the version list.
If several plugins are suspects, split them into small groups and test each group. Keep required dependencies together with the plugin that needs them; otherwise the test measures a missing dependency, not the original interaction. Once a group reproduces the issue, narrow it to a specific interaction by changing one cause at a time. Preserve the original configuration before each test set.
If the error is about load order or circular plugin loading, do not add -Dpaper.useLegacyPluginLoading=true blindly. Paper documents it as a last resort in its troubleshooting guide, where it warns that this may make other issues harder to debug. Save the full message and contact the authors of the plugins involved.
Return to the live server carefully#
Once you find a supported update or fix, repeat the check against the copied world first. Confirm that expected dimensions load, important plugins work, permissions and configurations are present, and the log has no new errors. Stop the test instance cleanly and make a separate copy of its state before applying the change to the live server.
On the live server, change only the required JAR or configuration setting. Keep the previous files until you verify startup and in-game behavior. Do not delete plugin data folders as “cleanup”: they may contain regions, permissions, databases, or settings. If the world, configuration, or an external service has already changed, stop the server and restore a consistent set from your backup instead of mixing files from different states.
This guide follows Paper documentation and community questions. It does not report a server, plugin, or backup restore being run here.
