Tell people to restart instead of reload.

[Kichura]

Problem Description

When using /reload confirm to restart all plugins at once, this has a side-effect of breaking mostly all plugins such as ViaVersion which can result in an unstable server state and that restarting the server instead resolves the problem [mostly] every single time,

And this has been an issue not only here but also in the discord's support channel aswell.

Solution Description

Have the reload command be replaced with a message telling the user that reloading the server is not supported and that they have the option to just restart the server instead as it is considered safer for usage.

Alternatives

Continue telling people not to run that command or kindly request them to use a permission system to get rid of it instead.

Additional Info

This "feature" request can be classified as ridiculous since there are multiple alternatives available for usage which is either patch the spigot/paper server or use a permission system instead to get rid of the command,

However one key thing that can be taken note of is that ProtocolSupport (for example) already does this kind of method and that it could be considered here aswell.

[florianreuth]

I think just not allowing any bukkit commands is not a good solution, if someone types /reload and wonders why plugins like ViaVersion break, the next thing he will try is to restart the server and find out anyway that /reload is not really stable, I think some platforms like Paper already notify you that /reload is unstable anyway.

[RaphiMC]

Noone should ever do /reload anyway. In the early days of bukkit this might have been fine, but most plugins nowadays are too complex to survive a full server reload. Server owners can still use plugin managers to selectively reload a single plugin if they really need. Disallowing the /reload command makes sense if its only outcome is a broken server state anyway.

[Kichura]

I think just not allowing any bukkit commands is not a good solution, if someone types /reload and wonders why plugins like ViaVersion break, the next thing he will try is to restart the server and find out anyway that /reload is not really stable, I think some platforms like Paper already notify you that /reload is unstable anyway.

While notifying the user that it's unstable can make sense on one hand, on the other hand most people tend to just ignore the advice and reload regardless just to end up complaining to us about it as soon as via* begins struggling about it which is why i brought this one in the first place.

[Kichura]

Noone should ever do /reload anyway. In the early days of bukkit this might have been fine, but most plugins nowadays are too complex to survive a full server reload. Server owners can still use plugin managers to selectively reload a single plugin if they really need. Disallowing the /reload command makes sense if its only outcome is a broken server state anyway.

ViaVersion could request people to use the third party's own reloading approach to restart the respective config(s) in case those fail or just ask for restart instead if it's the case about jar updatings instead for example. (Although idk how many people use the former's approach though)