Update-Ready Check

By
molonlav3

One command tells you which of your plugins will break on the next Paper version, before you update.

Updating Paper and finding out afterwards which plugins died is the worst part of running a server. This plugin tells you first.

/updatecheck 26.4 downloads the 26.4 Paper API from PaperMC's own repository (once, about 3 MB), reads every jar in your plugins folder, lists each Bukkit, Paper and Kyori class, method and field it uses, and checks them against the new API. Your running server's API is the before, so only what the update actually removes is reported:

Update-Ready Check: 14 plugin jars against Paper 26.4.build.12-stable, compared with this server's 26.3
  OK          PlayerbasePro 1.0.0 (40 API refs)
  WILL BREAK  OldScoreboard 3.1.0
      missing member: org.bukkit.scoreboard.Objective.getDisplayName()
13 of 14 plugins look ready for 26.4.build.12-stable.

/updatecheck latest for the newest stable API, /updatecheck 1.21.11 for an older line, /updatecheck list for the newest versions in the repository
Runs off the main thread; no lag. Needs outbound HTTPS to repo.papermc.io.
Permission updatecheck.use (ops by default)
What it cannot see: behaviour changes behind the same signature, NMS used through reflection, resources. Test those on a staging server.

Paper or Purpur 26.3+, Java 25. MIT. Same engine as the Hytale Update-Ready Check by the same author. Tested on a real Paper 26.3 server before release.

A plugin shows WILL BREAK and the author is gone? I rebuild abandoned plugins for new versions: https://ko-fi.com/molonlav3/commissions ($35 for a small fix, $90 for a port). If this saved you an evening, a coffee helps: https://ko-fi.com/molonlav3