In this PR, the administrator of the server can choose between several strategies for the authentication:
database: when a player enters /login my@email.com passphrase, the server checks if the player exists in the database and checks if the password is correct (I use bcrypt for hashing passwords)
file: Passwords are stored in a file
open: everyone can play on the server
Add support of configuration files (mainly used for the database authentication strategy), see authmod.cfg
Add support of sonarcloud for static analysis tools
/login my@email.com passphrase
, the server checks if the player exists in the database and checks if the password is correct (I use bcrypt for hashing passwords)