I’m trying to start a modded forge server with version 40.2.9. I can download and install the server but when I try to start it, AMP uses the forge installer jar instead of the new startup arguments used by the newer forge versions. After deleting the installer, AMP just re-downloads the installer or tries to start a non-existing minecraft_server.jar.
Reproduction Steps
Create new instance and select Forge → Stable → v40.2.9
Update the server and install correct forge version
Try to start the server with Forge v40.2.9 still selected in server options
AMP tries to use remaining installer.jar from forge instead of picking correct startup args
After deleting the installer.jar, AMP either tries to re-download forge oder output an error about a missing minecraft_server.jar
Already tried to swap the forge version or select vanilla just to swap back to forge with the specified version. I tried to reproduce the error but it immediately worked on a new instance. After adjusting some settings however, the error occurred again; I will try to pinpoint the settings now.
Edit: The problem seems to be with the option Lock to official Server. The server was successfully installed and ran without any problems. After turning this setting on however and restarting the server, AMP wants to use the installer.jar again.
Yeah I only looked at the setting name rather than its description and thats my bad. Anyway, is there a use-case for this setting if it isn’t toggling online-mode in the server.properties?
It’s for hosts that want to lock servers down and not let other server types be used. Although it’s mostly a hangover from MCMA2 and could actually be removed at this point.
