AuthRecoveryUI - Modern Login & Register v1.2.4

Version 1.2.4 — Stability & Recovery Flow Fixes

Fixed

• Escape-close on Confirm Email / Recovery / OTP / New Password now follows dialogs.allow-escape-close (fixes soft-lock when players Esc out of auth)
• Session auto-login watcher no longer stops after a failed dialog login — late AuthMe Session or chat /login still closes the dialog
• OTP is deferred until Set Password; wrong/expired codes no longer advance AuthMe under a false “verified” claim
• Unverifiable AuthMe forks (no checkPassword API) get a neutral login hand-off — never claims “password updated”
• SMTP send FAILED clears pending registration state (no leftover password in memory)
• DNS deliverability now also checks AAAA (IPv6-only mail domains)
• /otp and /forgotpassword are blocked when already logged in
• Passwords with spaces are rejected; recovering to the same current password is rejected
• FastLogin late-register clears pending email verification; RecoveryCommandListener no longer double-opens dialogs
• Last wrong registration verification code maps to too-many-attempts immediately (no “0 attempts left”)

Upgrade: replace the JAR, then /authrecoveryui reload (or restart).
No config migration required — new message keys fall back to English defaults if missing from lang files.

Version 1.2.3 — Fixed dialog box​

Note: Version 1.2.1 – 1.2.2 were internal QA builds, not publicly released.
Fixed

• Fixed an edge case where the registration dialog might remain open after a delayed auto-registration by a third-party plugin (e.g., FastLogin). It now automatically closes if the player has logged in, or switches to the login dialog if the account is registered but not yet logged in — matching the existing login dialog behavior.

Version 1.2.0 — Duplicate Email Protection​

Added

• Duplicate-email safety net for registration — an extra layer of protection against the same email being used to register multiple accounts
• Checks AuthMe's own database directly (read-only, no data is modified)
• Runs first, before any email-verification steps begin

Why it matters

• AuthMe has its own built-in protection against duplicate emails, but some AuthMe builds/forks don't reliably enforce it as configured
• Previously, a duplicate email would only be caught after the player completed the entire email-verification process — wasting their time for nothing
• Now it's caught and reported immediately, right from the start

Changed

• check-duplicate-email — toggle this feature on/off
• sqlite-database-file — manually specify the database filename (if auto-detection can't find it)
• email-already-used-message — fully customizable warning message