Sol's AuthLogin

Sol's AuthLogin System v1.3.1

Changelog:

• Authentication is now disabled by default for the local owner of an integrated single-player world. Dedicated-server players and remote guests joining an opened-to-LAN world remain protected as before.
• Players who want authentication in an integrated world can enable general.security.enableInSingleplayer in solsauthlogin-common.toml.
• Fixed a server crash or save during authentication potentially replacing a player's real inventory with an empty auth-state inventory. AuthLogin no longer clears or masks the live inventory; its movement, interaction, container, pickup, drop, damage, chat, and command protections remain active.
• Fixed players sometimes returning to the authentication spawn instead of their previous location after lag, rapid reconnects, or a server crash.
• Return locations are now saved before the auth teleport, written atomically, backed up safely, and recovered from backup if the main file is damaged.
• Original game mode and movement abilities now survive reconnects and server restarts while authentication is incomplete. Survival, Creative, Adventure, and Spectator are restored accurately.
• Password attempts, duplicate-login protection, remembered server sessions, and client auth tokens no longer cross between differently capitalized usernames.
• Auth recovery records are cleared only after the restored player data has been saved successfully.
• Server shutdown now restores active auth restrictions before the final player save whenever possible.
• If AuthLogin cannot safely save the player’s return location or recovery state, it disconnects them before applying authentication restrictions. The player should rejoin; if the problem repeats, contact the server administrator. This safeguard prevents an unsafe auth-state save and does not itself indicate that player data was lost.

Upgrade notes:

• Existing credentials and configuration carry over. Credential lookup keys are migrated automatically to each account's originally stored capitalization; no password reset or manual migration is required.
• Existing config files automatically receive enableInSingleplayer = false.
• Install matching v1.3.1 jars on the server and clients where the client mod is required.