Importance: 6/10
Problem:
I've had a moment where my friend accidentally killed all mobs in my server. In that case, it would be nice to have a kill option to immediately stop the server to prevent it from autosaving and make it return to the latest autosave for example. I miss this functionality right now in AutoPlug itself and the AutoPlug plugin for Spigot (am using Purpur, a fork of Paper and yet Paper is a fork of Spigot) and it'd be nice to have so I don't for example need to restore a 15 minute old backup so we can keep progress lose to max. 5 minutes. This is good to have for more things, in case things in the launch of the server may get glitched but the client would still respond.
Solution:
Add a command to kill the Minecraft Java instance itself and to kill the final Java instance for the server + AutoPlug itself. (So like you'd have .st and stop (both) you could do the exact same for killing the processes by force).
Importance: 6/10
Problem:
I've had a moment where my friend accidentally killed all mobs in my server. In that case, it would be nice to have a kill option to immediately stop the server to prevent it from autosaving and make it return to the latest autosave for example. I miss this functionality right now in AutoPlug itself and the AutoPlug plugin for Spigot (am using Purpur, a fork of Paper and yet Paper is a fork of Spigot) and it'd be nice to have so I don't for example need to restore a 15 minute old backup so we can keep progress lose to max. 5 minutes. This is good to have for more things, in case things in the launch of the server may get glitched but the client would still respond.
Solution:
Add a command to kill the Minecraft Java instance itself and to kill the final Java instance for the server + AutoPlug itself. (So like you'd have
.standstop (both)you could do the exact same for killing the processes by force).