Skip to main content

Choose the correct ProtocolLib artifact for Paper or Spigot

Applies to: ProtocolLib; match the linked maintainer documentation to your installed platform and release.
Documentation checked .

ProtocolLib's current distribution distinguishes its primary Paper artifact from the Spigot compatibility artifact. Old instructions that treat every file as interchangeable can lead to a startup failure. Confirm the platform and the maintainer's current release guidance before downloading another copy.

Record the starting point

Record the actual server software from startup output, not just a panel label. Note the server build and Java runtime. Save the current ProtocolLib artifact and dependent-plugin list outside the active folder so the previous combination can be restored if the trial fails.

Work through the change

  1. Open the official ProtocolLib repository and release instructions. Confirm whether your platform needs ProtocolLib.jar for Paper or the documented ProtocolLib-Spigot.jar compatibility artifact.
  2. Download the matching server plugin from the maintainer. Do not substitute a developer API dependency, sources archive or an unofficial renamed download.
  3. Stop the server and remove duplicate ProtocolLib artifacts from the active plugins folder before adding the selected one. Keep the saved previous file outside that folder.
  4. Start normally and read the ProtocolLib load result. Test one dependent feature with an ordinary player and check that no second copy or dependency error appears.

Check the result

The correct artifact should load on the intended platform and satisfy dependent plugins that support that release. Record the filename and release number together. A renamed file is not evidence that the internal artifact matches the platform.

If the result differs

If the correct artifact still fails, compare Java requirements and supported server builds. A dependent plugin's own missing class is a separate compatibility check. Preserve the first cause instead of repeatedly swapping files from different websites.

Restore the previous matching artifact and restart if the new release regresses a required integration. Keep the platform decision in the server notes so a future update does not repeat the mismatch. Player data and worlds remain outside this change.

CloudExa game panel file manager
Use the file manager for the specific configuration file described in this guide; the screenshot shows the panel, not a plugin interface.

References and related help

No comments to display