☰

Plugin Conflict

A Bukkit/Spigot/Paper server throws a NoSuchMethodError, typically when a plugin calls an API method that no longer exists or differs from what it was built against. Two plugins, or a plugin and the server version, disagree on the API.

What does this error mean?
NoSuchMethodError means code tried to call a method that is missing at runtime. On a plugin server this usually means a plugin was compiled against a different API version, or two plugins bundle conflicting versions of the same library. 
java.lang.NoSuchMethodError
Most Common Causes
  • A plugin built for a newer or older server API than you run.
  • Two plugins shading different versions of the same library.
  • An outdated plugin that has not kept up with API changes.
  • A dependency plugin at the wrong version.
  • Mixing plugins built for incompatible server forks.
How To Diagnose
  1. Read the stack trace, the top plugin package name is your prime suspect.
  2. Note which method/class is missing to identify the API mismatch.
  3. Bisect: disable half the plugins, then narrow down by halves.
  4. Confirm each plugin supports your exact server version.
Recommended Fixes
  • Update the plugin
    Install a build that matches your server version and API.
  • Remove the outdated one
    Drop or replace any plugin that has not been updated for your version.
  • Resolve library clashes
    If two plugins shade the same library, update both to compatible versions.
  • Fix dependency versions
    Install required dependency plugins at the versions the plugin expects.
Analyze My Log
Frequently Asked Questions

The stack trace names the plugin's package. If unclear, disable plugins in halves to narrow it down.

Usually, but read the changelog, major plugin updates can change configs or behavior.

Yes, if they bundle incompatible versions of a shared library. Updating both typically resolves it.