Since AMP v2.8.0.8 (built 27/09/2026), my Minecraft instance (NeoForge, MC 1.21.1) no longer starts. The NeoForge version list in Configuration > Server and Startup no longer offers 21.1.214 (the only entries are 26.x and 47.1.x), and the field falls back to 47.1.82. The console then shows: Error: could not open ‘libraries/net/neoforged/neoforge/47.1.82/unix_args.txt’. My installation of 21.1.214 is intact (the folder exists in libraries/). Java is Temurin 21. It worked fine until yesterday.
Reproduction Steps
Open the instance Configuration > Server and Startup with Server Type set to NeoForge and Release Stream set to Specific Version.
The version dropdown: 21.1.214 is not listed anymore (only 26.x and 47.1.x entries), and the field shows 47.1.82 (mc 1.20.1) instead.
Click Start on the instance: it fails with “Unable to run” and the console shows: Error: could not open libraries/net/neoforged/neoforge/47.1.82/unix_args.txt
Workaround found (server is running again):
AMP was looking for libraries/net/neoforged/neoforge/47.1.82/unix_args.txt, which does not exist on my server. My actual installation is NeoForge 21.1.214 and is intact.
To work around it, I created a folder libraries/net/neoforged/neoforge/47.1.82/ and copied the unix_args.txt file from the 21.1.214 folder into it. After that, the instance started normally on 21.1.214.
The version shown in Configuration > Server and Startup is still wrong (47.1.82), and 21.1.214 is still missing from the version list, so the root cause seems to be the NeoForge version list / selected version handling since AMP v2.8.0.8. I have not used “Download / Update” to avoid overwriting my installation.
CC: @harry647
The NeoForged project has been having issues with their repository recently. This was yesterday but I have it on good authority that they’re experiencing the issue again.
Public service announcement
Hello! We are currently aware of an issue regarding our Maven repository, specifically that nearly all NeoForge versions have disappeared, which has affected downstream consumers.
As far as we can tell from an early investigation, our build pipeline likely had a parallelization issue, where two builds ‘collided’ while publishing, causing our versions list to visually disappear. The actual artifacts themselves are unaffected. (Gradle and Maven…)
We are working as soon as we can to fix this issue. Thank you for your patience.
You can join the CubeCoder’s discord server and checking the minecraft channel for more information and discussion.
Actually turns out it may be resolved now. See if you can see all the versions now in your instance. If not, stop the instance, use the file manager to delete NeoForgeVersionManifest.xml in the instance root, then start the instance again. Should be good after that.
