Plugins on Minecraft servers; It operates the authorization system, economy, protection, market, event, claim, anti-cheat and many special systems. If one of the plugins is not installed, a significant part of the server may not work.

Plugin errors usually occur in the console or logs/latest.log appears in the file. The most common mistakes; Couldn't load plugin, Unsupported API version, unknown dependency, Invalid plugin.yml and Java version incompatibilities.

1. Where Can You See the Plugin Error?

If the plugin is not loading, the first place to look is the server console and latest.log file.

tail -n 200 logs/latest.log

For live tracking:

tail -f logs/latest.log

To search by plugin name:

grep -i "pluginadi" logs/latest.log

2. Unsupported API Version Error

This error indicates that the Minecraft API version supported by the plugin is incompatible with the server version.

Unsupported API version 1.20

For example, the plugin may be prepared for 1.20, but your server may be running 1.16.5. In this case, the plugin may not be loaded or may work incorrectly.

Solution:

• Check the Minecraft version supported by the plugin.
• Download the plugin version compatible with your server version.
• Do not expect new plugins to work on very old servers.
• If necessary, find the appropriate version from the old version archive of the plugin.

3. Unknown Dependency Error

Some plugins do not work alone. It asks for another plugin to be installed first. This is called dependency.

Unknown dependency Vault
Could not load plugin because dependency LuckPerms was not found

For example, economy plugins often Vault wants. Authorization or market plugins may also need other library plugins.

Solution:

• Read the requirements on the plugin page.
• Download the missing dependency plugin.
• Make sure that the dependency plugin is also compatible with your server version.
• Restart the server completely.

4. Invalid plugin.yml Error

Inside the plugin jar file plugin.yml If the file is corrupt, missing or incorrect, the plugin cannot be installed.

Invalid plugin.yml
Plugin does not contain a plugin.yml

This usually occurs when:

• The wrong file was downloaded.
• Instead of the plugin, the source code zip has been placed in the plugins folder.
• Jar file is corrupted.
• The plugin was packaged incorrectly by the developer.

As a solution, the plugin is correct. .jar The file should be downloaded. The source-code.zip downloaded from GitHub should not be placed directly into the plugins folder.

5. Java Version Incompatibility

Minecraft version and plugins require specific Java versions. If the wrong Java version is used, the plugin or server may not open at all.

java -version

Common error:

UnsupportedClassVersionError

This error indicates that the plugin was compiled with newer Java, but older Java is used on the server.

General logic:

• Older Minecraft versions often require older Java.
• Newer Minecraft versions require newer Java.
• The Java requirement in the plugin description should be checked.
• The selected Java version in the hosting panel must be verified.

6. Is the Plugin File in the Correct Folder?

Plugin files on Bukkit, Spigot and Paper servers plugins is thrown into the folder.

ls plugins/

The plugin file should be like this:

plugins/PluginAdi.jar

Plugins left in zip, rar, source code or folders often do not work.

7. Plugin Conflicts

Two plugins that do the same job may conflict with each other. For example, two different chat plugins, two different economy plugins or two different claim systems may try to manage the same events.

Conflict symptoms:

• The plugin is installed but its commands do not work.
• One plugin overwhelms another's setting.
• An event conflict or exception occurs in the console.
• Players cannot use commands even if they have permission.
• The server behaves differently after restart.

To find a solution, plugins can be tested by disabling them one by one. However, before doing this on the live server, a backup should be made and low player hours should be preferred.

8. Config Error May Prevent Plugin from Opening

Some plugins will not open if there is a YAML error in the config file. Whitespace indentations are especially important in YAML files.

Common mistakes:

• Using tab character
• Do not leave a space after the colon
• Writing text that requires quotes without quotes
• File corruption due to Turkish character or special symbol
• Saving missing config file

If there is an incorrect config file, the plugin folder can be temporarily renamed to back up the plugin folder and recreate the config.

Common Mistakes

• Installing plugins that are not compatible with the server version
• Not installing missing dependency plugins
• Mistaking the GitHub source zip file as a plugin
• Not checking Java version
• Trying to install a plugin with /reload
• Using tabs in YAML config files

FAQ

The plugin is in the plugins folder but it doesn't work, why?
It could be version incompatibility, missing dependency, Java incompatibility or config error. The latest.log file should be examined.

What does UnsupportedClassVersionError mean?
The plugin has just been compiled with Java. The Java version used on the server is outdated.

Is it safe to use /reload?
It is not recommended for many plugins. A full restart is safer for plugin installation, removal and major config changes.

Safety and Operations Recommendations

• Download plugins from reliable sources.
• Before adding the plugin to the live server, try it on the test server.
• Back up the plugins folder before each plugin update.
• Reduce the attack surface by removing unnecessary plugins.
• Check plugin logs regularly.

This article is specially prepared for PvPServer.