NeverUp2Late - Automatically keeps Server+Plugins up to date

Paper updates are back on track: PaperMC’s v2 API was disabled on July 1, 2026, and the fetcher now supports Fill v3. Starting immediately, releases will first appear as pre-releases and will only be released after a soak period, so that a faulty build can still be withdrawn. Existing installations that previously updated via SpigotMC itself will automatically switch to the GitHub releases.

Corrective release for the update pipeline. An update now installs only what is genuinely newer than the installed version. Three earlier branches reached "download" without comparing versions at all - a destination missing under its configured file name, a build number that happened to be larger, and a version string that merely differed - and each of them could put an older build onto a server. Modrinth, Hangar and CurseForge no longer invent a build number from a hash when a release publishes none. A jar that is genuinely gone is still restored; one that was only renamed is left alone. An installation is refused if the jar at the destination belongs to a different plugin, or if the plugin is already installed under another file name. Both cases used to go ahead: the first overwrote an unrelated plugin, the second left two copies in the folder, and Bukkit then refused to load one of them. Quick install no longer guesses which installed plugin a source belongs to by substring. A finished update names the backup of the file it replaced. New: /nu2l plan reports what an update run would install and what it would refuse, without downloading or writing anything.

Bugfixes

Complete transition to English and bugfixes

Big Bugfixes

stabilised the whole process

· Again resolving problems with SpigotMC/Spiget API...

· Bug fixes regarding SpigotMC links

· Bugfixes

· Bugfixes

Thanks to spiget.org NeverUp2Late now supports also Spigot.org Resources!

Thanks to spiget.org NeverUp2Late now supports also Spigot.org Resources!

· Bugfixes

· Bugfixes

· Bugfixes

· Flexible update sources. The update registry now reads a configurable updates.sources list (with Paper/Geyser fallbacks), instantiates fetchers by type via reflection, and can register new sources at runtime—supporting bundled fetchers for Hangar, Modrinth, CurseForge, GitHub Releases, Jenkins, and any custom UpdateFetcher implementation you wire in. · Quick-install workflow & GUI. /nu2l now covers GUI access, asset selection, URL analysis, installed-plugin detection, config persistence, and scheduling of the first install without blocking the main thread, while the in-game overview lists managed plugins and guides players through linking new sources. · Asynchronous update pipeline and manual runs. UpdateHandler drives a scheduled fetch→download→install pipeline off-thread, resolves file destinations, copes with network hiccups, and exposes manual executions that report progress and outcomes back to the caller. · Lifecycle-aware post-update handling. When enabled, the plugin now registers loaded plugins for lifecycle control, queues post-update actions until players have left, enforces a restart cooldown, reloads plugins in-place when possible, and shuts down the server to complete installs if needed. · Persistent update tracking & migrations. Build/version metadata is stored in a normalized plugins.yml, legacy schemas are auto-migrated, and old config.yml entries are moved across with informative logging, giving the updater a reliable baseline for comparisons.

Eue to an error, only unstable versions of paper have been considered so far. Now it is possible to include or exclude the stable versions of Paper in the config.yml. A new line has been added to the config for this, which must either be inserted manually or the plugin folder must first be deleted again and regenerated independently. Code (YAML): # Ignore unstable builds ignoreUnstable : true

Setting the default name of the Geyser JAR file to: "Geyser-Spigot.jar"