PureAuth 6.2.0 — Progressive Login Lock

PureAuth 6.2.0 introduces a three-stage account protection system for repeated failed authentication. It applies to password, PIN and invalid 2FA attempts while retaining the existing permanent account lock.

Progressive lock stages

• After 3 failed attempts by default, the player is kicked and login is blocked for 30 minutes.
• A second max-attempt kick blocks login for 24 hours.
• A third max-attempt kick permanently locks the account.
• Lock stages and expiry timestamps persist across server restarts.
• Players may join during a temporary lock, but remain hidden, frozen and unable to authenticate until it expires.
• If the timer expires while the player is online, the normal authentication flow resumes automatically.
• /pureauth unlock <player> clears temporary or permanent locks and resets escalation history.

Configurable display and behavior

• Live title, subtitle, actionbar and periodic chat countdowns are available during temporary locks.
• All player commands are blocked while authentication is locked.
• Every new message and display option is configurable in English and Polish.
• New settings control both lock durations, stage-history reset, reminder interval and each display channel.
• Existing max_attempts, account_lock_enabled and kicks_before_lock settings remain supported.

Database, compatibility and fixes

• Added automatic, data-preserving migration for temporary_lock_until.
• Lock escalation is saved atomically in a database transaction.
• Added safe handling for nulls, missing accounts, unavailable databases, invalid values and time overflow.
• Fixed the updater incorrectly treating an older Modrinth release as newer.
• Added semantic version comparison and 5/10-second network timeouts to the updater.
• Built against stable Paper API 26.2.build.117-stable and Velocity API 3.5.1.