AuthRecoveryUI - Modern Login & Register v๊๊Update 1.2.4

Version 1.2.4 — Stability & Recovery Flow Fixes

Fixed:

• Confirm Email/Recovery/OTP/New Password dialogs now respect dialogs.allow-escape-close (previously hard-coded open, risking soft-locks under AuthMe freeze).
• Auto-login watcher now stops only on a successful dialog login — a wrong password still leaves the Session//login safety net active.
• Recovery OTP is now verified via AuthMeApi#checkPassword at Set Password, not submitted early — wrong/expired codes can no longer fake a "verified" state.
• Forks without checkPassword show a neutral hand-off message instead of falsely claiming the password was updated.
• SMTP FAILED clears pending registration state (no leftover plaintext password); DNS checks now include AAAA for IPv6-only mail hosts.
• /otp//forgotpassword block already-authenticated players; null/whitespace passwords show clear errors; recovering to the same password is rejected; FastLogin late-register clears pending email verification; duplicate RecoveryCommandListener dialogs are suppressed; the final wrong code jumps straight to "too many attempts."

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