Prevent starting server.jar instead of fabric-server-launch.jar

[Tacodiva]

Not sure if this is the right place to suggest this, please refer me to the right place if it isn't.

I think allowing people to launch the server using the vanilla server.jar file with fabric installed is an oversight. Though my own error, I accidentally just typed java -jar server.jar instead of java -jar fabric-server-launch.jar and, due to biome incompatibilities, it destroyed my entire world and I can no longer launch it using fabric. Launching the vanilla server like this can be prevented by simply deleting the main manifest attribute in the server.jar file while installing fabric, or when launching the server through the correct jar for the first time.

[sfPlayer1]

The new server installation method already buries the vanilla server jar a couple folders away, which should make this a rather unlikely

[Tacodiva]

I think because I downloaded the server.jar file separately and put it into the main server directory directly, this didn't happen. When you launch the fabric-server-launch.jar right now with no server.jar present it instructs you to put the server.jar into the server's root directory. Should these instructions be changed? Alternatively, when the server.jar is present in the root directory could it be moved into another directory automatically? I know I'm a bit of a dumb-ass but it feels it should be harder to do what I did.

[modmuss50]

This issue was basically solved by using the server launcher from the website and not the installer.