Disconnect players before unloading plugins

[NonSwag]

Is your feature request related to a problem?

My general problem is that players get kicked for server closed after the plugins got disabled
this causes the problem of PlayerQuitEvent/PlayerKickEvent not being called
This can lead for example to something like data not being stored or so

Describe the solution you'd like.

I'd love to see the player disconnect logic being handled before the plugins unload

Describe alternatives you've considered.

Right now when dealing with this problem I (or plugin devs in general) have to handle everything onDisable or kick the player

Other

[NonSwag]

I don't really want to create a pr for this because first I want to get some input on this
maybe there is a good reason for this idk

[lynxplay]

Duplicate of #6911 and #9679.

Generally not something we can takle till hardfork imo, can keep discussion in the respective PR given how terribly low priority this is.

[Combustible]

This is a critical problem for us as well - so we just hack around it in our paper fork. Not ideal, and certainly not a PR I'd like to submit here... but this patch has worked for us for years now:

https://github.com/TeamMonumenta/monumenta-paperfork/blob/main/patches/server/0004-Monumenta-Move-player-saving-to-before-disabling-plu.patch

Would love to see this changed someday. Until this is fixed it's difficult to reliably build a plugin that alters how player data storage works.

@NonSwag perhaps this will help you if you happen to already use a customized paper jar.

[Combustible]

Oh, it looks like the above referenced #9679 does basically this same thing, I should have checked before commenting.

[NonSwag]

The problem with this is that the behavior for certain plugins COULD possibly change or even break them which is a total no-go in production but thanks for your input