How to Check Minecraft Plugin Compatibility
Check Minecraft version, Paper or Purpur support, Java requirements, plugin builds and dependencies before installing a Minecraft config or plugin.
How to Check Minecraft Plugin Compatibility
A Minecraft resource depends on several layers working together: the Minecraft version, server software, Java runtime, target plugin and any dependencies. Checking each layer before installation helps avoid startup errors, missing features and broken configuration files.
Quick answer: match the exact Minecraft release, server implementation, Java runtime and plugin build listed by the product and upstream plugin documentation. Test on a backup or staging server before deploying to players.
Compatibility checklist
| Check | What to confirm | Where to look |
|---|---|---|
| Minecraft version | The exact release your server runs, not just a broad version family | Server startup log or host panel |
| Server software | Paper, Purpur, Spigot, Folia, Velocity or BungeeCord support | Product listing and plugin documentation |
| Java runtime | The Java version required by your Minecraft release and plugin | Server startup log and plugin requirements |
| Target plugin | The installed plugin build supports that Minecraft/server version | Plugin release notes |
| Dependencies | Required libraries, PlaceholderAPI expansions or companion plugins are installed | Product guide and plugin documentation |
| Configuration format | The keys, placeholders and formatting tags match your plugin version | Product guide and upstream config reference |
1. Check the Minecraft version
Find the exact Minecraft version your server is running. Do not assume that support for one release automatically means support for every later release. A product may list specific tested versions rather than a continuous range.
2. Check the server implementation
Identify whether your server uses Paper, Spigot, Purpur, Folia or another implementation. Some plugins use server-specific APIs or have limitations on certain implementations. Proxy plugins may require Velocity or BungeeCord, while backend plugins may need to be installed separately.
Confirm support in the plugin's official documentation before copying files.
3. Check the Java runtime
Use the Java version required by your Minecraft release and the plugin. A plugin may fail to load if the runtime is too old, even when the JAR is in the correct folder. Check the Java version printed near the start of the server log.
4. Check the target plugin version
For a configuration pack, the target plugin is especially important. A messages file or menu created for one plugin version may use keys or options that do not exist in another.
- Confirm the required plugin is installed before applying the config.
- Compare the product's compatibility notes with the installed plugin build.
- Read upstream release notes for renamed, removed or newly required settings.
- Keep a copy of the original configuration so you can roll back.
5. Check dependencies and placeholders
Some configurations reference placeholders, expansions, libraries or other plugins. Install the required dependencies and verify that they load before testing the configuration. A missing placeholder expansion may show raw text even when the config itself loads correctly.
6. Test on a backup or staging server
Back up your production server, install the resource on a test instance when possible, and inspect the startup log. Test the commands, menus, messages and features that the resource changes before deploying it to players.
If compatibility is unclear
Do not guess or rely on a version number from a different product. Check the product's compatibility section and the upstream plugin documentation. If you contact ZCraft Studios support, include your Minecraft version, server software, Java version, target plugin version and the exact error.