AMP version: 2.8.0.0 (Proteus), Mainline/Release, built 25/06/2026
Module: MinecraftModule 2.8, ServerType=Paper_Spigot, licence: Advanced Edition
Environment: Debian Linux, Docker mode (cubecoders/ampbase:java)
Issue:
With SpecificPaperVersion=26.2 and Application Startup Mode set to Update and Start, AMP installs Paper 26.2-rc-2
build 9 even though the latest upstream build is 26.2 build 53 (stable). AMP’s version feed for Paper appears to be
stale — presumably because PaperMC has sunset their v2 API: https://api.papermc.io/v2/projects/paper now returns
{“ok”:false,“error”:“sunset”,…}. The current endpoint is the “fill” v3 API, e.g.
https://fill.papermc.io/v3/projects/paper/versions/26.2/builds/latest.
Impact:
Because the update runs on every application start, AMP silently overwrites a manually updated paperclip.jar and
downgrades the server back to the RC build on each restart. RC builds of Paper break several popular plugins
(packetevents, Citizens, etc.), so this effectively pins servers to a broken version with no way to update from within
AMP.
Steps to reproduce:
- Paper_Spigot instance, Specific Paper Version = 26.2, startup mode = Update and Start
- Manually replace paperclip.jar with Paper 26.2 build 53 from fill.papermc.(io)
- Restart the application → AMP replaces the jar with 26.2-rc-2 build 9 again (no update activity is logged, which
also makes this hard to diagnose)
Workaround I’m using: chattr +i paperclip.jar — AMP then logs “Unable to delete ./Minecraft/paperclip.jar: Access to
the path is denied” as a warning and starts normally with the correct jar.
Requests:
- Migrate the Paper (and presumably Folia/Velocity) version feed to the fill v3 API
- Log the server-jar download/replacement step (version + source URL) so downgrades are visible in the instance log