Welcome

What uxmAuth does, who it is for, and where to read next.

An offline-mode server lets anybody join under any name. uxmAuth puts a door in front of it: a player registers a password the first time and logs in with it after, a player who owns the name at Mojang proves it and walks in, and a Bedrock player Floodgate vouched for walks in too. Behind the door sit sessions, address bans, a captcha, a second factor, mail recovery, and the staff tools to run it.

What it does

Part	What it gives you
The waiting room	A dialog before the world, a frozen player, or an empty login world
Passwords	Rules, a common-password list, a breach check, Argon2id and three more algorithms
Sessions	A player back from the same address skips the password
Premium names	Four ownership rules, four UUID schemes, four ways to settle a name two players want
Bedrock	Floodgate players in without a password, or with a native form
Protection	Address bans, connection and account limits, filters, countries
Captcha	A code as text or drawn on a map
Second factor	An authenticator app or a code by mail, backup codes, required for staff
Mail and recovery	A linked address, a forgotten password, the login code by mail
Effects	Titles, bars and sounds for every moment of the door
Staff tools	Info, history, alerts, Discord, console-only commands, purge
Website table	A website's login table kept beside the plugin's own
A network	Velocity and every server behind it as one door, with signed claims

Every screen, command and line a player reads can be changed, in seven languages.