Updating doesn't change the start command

[realSZ27]

When the server updates to another version, the .jar will be named differently, but the start command in the service file wont be changed to reflect this.

It would also be good to cleanup the old .jar when updating, and have warnings when the user tries to switch from one server software to another. Examples below. I don't think disallowing these switches is good either because there are some legitimate scenarios where it could work perfectly fine.

Switching from vanilla --> paper/purpur is fully supported. And purpur is a drop-in replacement for paper so switching from paper --> purpur is fully supported. But switching from fabric --> anything else (except manual) is unsupported because many mods change the world. Purpur --> paper works, but you will lose any purpur-specific configuration. And of course the script doesn't know what the manual server .jar is, so it's up to the user to make sure the switch is compatible.

Downgrading minecraft versions doesn't work unless you want to reset your world, or more depending on how far you go back.

Went on a little rant, but it's still kinda related lol.

[keepittechie]

Thanks for your detailed comment! You're absolutely right about the .jar name changes after updates. I'll look into automating the start command in the service file. Cleaning up old .jars during updates is a great idea too; I'll work on that.

Switching server software should definitely come with warnings based on scenarios like vanilla to paper/purpur being supported but fabric to anything else being tricky due to mod changes.

And yes, downgrading Minecraft versions can be a headache, so a warning about potential world resets is smart. Your rant is definitely related and appreciated! LOL It's feedback like this that helps improve the tools and scripts for everyone. I'll work on integrating these ideas into the next update. Thanks again for your insights!

Also if you see anything else, let me know or see if you can come up with a improvement.