Skip to content
Tickwise
WarningPluginsSIG-PL-003

Duplicate plugin: two jars with the same name (Ambiguous plugin name)

Platforms
Paper · Purpur · single server
Verified
Verified
Confidence
Confidence 98%

What it looks like in the log

Any one of these lines is enough. The agent matches them locally, on your server.

logs/latest.log
  • [WARN] Ambiguous plugin name

Symptoms

  • After a plugin update, the old version is running or behaviour is unpredictable
  • In the startup log: “Ambiguous plugin name '…' for files …”

Cause

plugins/ contains two files that declare a plugin with the same name (usually an old and a new version). Only one of them is loaded — not necessarily the right one.

Possible causes

  • The new jar was added during an update but the old one was not removed
  • Two different plugins/forks use the same name in plugin.yml

How to fixLow risk

  1. Take the plugin name and both file paths from the evidence.
  2. Stop the server, keep only the version you need in plugins/ (usually the newer one), and delete the other file or move it to a backup folder outside plugins/.
  3. If these are different plugins with the same name, keep one of them (they cannot run side by side).
  4. Start the server and check the version with /version <plugin>.

Translated from the Russian original; log lines are quoted verbatim.

Sources