0892d19ded
After we kick a player, then an async process of shutting down that player's connection is initiated, and their player data is flushed to the database AFTER that. If we remove the player data at the same time as kicking, it's not actually removed, but the auth IS removed, so we have a bunch of player data left behind that we don't realize, and there's no mod-API way to enumerate them. For now, just disallow this use case. The time between calling /kick and /destroy_player should be sufficient to avoid the race condition, at least, for now.
This mod is a dumping ground for minute features that are too small to warrant their own mod, are obvious features that should probably have just been included in base, and are limited to certain audiences (admins and moderators) and so are generally safe to enable always.
Currently includes:
- Adds a
/destroy_playercommand that completely deletes a player's account, including auth info. This can be useful for some games like e.g. NodeCore, where player "ghosts" are cleaned up and their items drop if the account is destroyed, or just for general cleanup. - Moderators and admins (privs/basic_privs priv owners) can always log in and bypass the user limit, making it still possible for admins to access the server during a botting attack.