PluginPulse Web Tool

Add an auto-updater to a compiled Paper/Spigot plugin — no source code, no build tools. Everything runs in your browser. Your jar is never uploaded anywhere.

1. 1. Choose your plugin jar

   Preview jar

   Use this to review the current plugin and author details before making any changes. Nothing is modified — if the jar can't be processed, you'll get a plain-English explanation.

2. 2. Where do updates come from?

   Plugin updating will only work if at least one of these is available. Set the priority (#1 is checked first) to choose the order they're tried in.

   Modrinth modrinth.com/plugin/viaversion

   #1#2#3#4
   GitHub github.com/ViaVersion/ViaVersion

   #1#2#3#4
   Hangar hangar.papermc.io/kennytv/ViaVersion

   #1#2#3#4
   Jenkins (CI snapshots) job page URL, e.g. ci.athion.net/job/FastAsyncWorldEdit/

   #1#2#3#4

   Follows the job's last successful build — these are dev snapshots, not releases. Jenkins publishes no checksums, so with download or auto-stage mode the tool writes require-hash: false for you; otherwise CI updates would be notify-only.

3. 3. How should it behave?

   Update mode notify — tell admins on join (no download) check-only — silent; only shown on command download — download & stage; applies on restart auto-stage — download automatically when found Contact (recommended)
   Advanced settings

   Command root (optional) Permission (optional) Release track (optional) Check interval (hours) (optional) Re-inject a jar that already has PluginPulse

4. 4. Generate

   I have the right to modify and redistribute this jar. Generate updated jar

   Test the result on your own server before distributing it. The tool can't verify the jar boots.