FloodPass
AuthMe 的 Floodgate 自动登录 — Xbox 验证,因此 Bedrock 玩家无需输入密码
简体中文
仅适用于官方 AuthMe。 FloodPass 专为原版 AuthMeReloaded (5.x / 6.x) 构建。请勿在已自带原生 Floodgate 自动登录功能的分支(如 AuthMeReReloaded)上安装此插件 —— 否则功能会重复执行。
功能说明
跨平台服务器通常使用 AuthMe 来保护生存账户。这对 Java 玩家来说运作良好,但通过 Geyser + Floodgate 接入的 Bedrock 玩家在连接建立前就已经通过 Microsoft/Xbox 账户完成了身份验证。让他们再输入密码纯属多余。
FloodPass 正是为了解决这一问题:
- 对于 Bedrock 玩家:永远无需输入任何内容。已注册的账户在加入后约一秒钟自动登录;全新玩家将以随机密码静默注册并立即登录
- 对于 Java 玩家:无任何变化,他们仍按原有方式经过 AuthMe 验证
- 兼容前缀名称:携带 Floodgate 前缀的 Bedrock 用户名(例如
.Steve)可顺利通过 AuthMe 默认的 allowedNicknameCharacters 正则表达式检查,无需修改 AuthMe 配置 —— 仅真正的 Floodgate UUID 会被豁免
- 共存 Premium 账号:若 Bedrock 玩家的 Gamertag 与已注册 Premium 的 Java 账户相同(AuthMe 6.x
/premium + PacketEvents),该 Bedrock 玩家可正常加入,而 Java 账户继续享受无密码的 Premium 登录
- 对于服务器管理员:只需一个 jar 文件,无需更改 AuthMe 配置,一条命令即可管理所有功能;信任决策保留在其应有的位置(Floodgate 的 Xbox Live 验证)
Bedrock 玩家加入时的截图

工作原理
- 玩家加入时,FloodPass 以
MONITOR 优先级监听,此时连接的 Floodgate 身份信息已可用
FloodgateApi#isFloodgatePlayer(uuid) 判断这是否为真正的 Bedrock 连接;Java 玩家永远不会被影响
- 在可配置的延迟后(默认 20 tick),AuthMe 完成其自身的加入处理,随后 FloodPass 接管:
- 已注册玩家:
AuthMeApi#forceLogin 在不输入密码的情况下登录账户
- 未注册玩家(如果启用了自动注册):
AuthMeApi#forceRegister 以随机密码注册账户并立即登录
安全基础:Floodgate 身份仅在 Bedrock 客户端使用有效的 Xbox Live 令牌完成 Floodgate 加密握手后才存在。Java Edition 客户端无法伪造该身份,因此无密码登录路径仅向微软已验证的玩家开放。
兼容性
| 组件 |
要求 |
备注 |
| 服务端 |
Spigot / Paper / Purpur / Folia 1.13+ |
Java 8 字节码;较旧的遗留服务端 (1.8+) 通常也能加载,未经测试 |
| Folia |
支持 |
通过反射实现每实体调度器,其他情况回退到全局调度器 |
| Java |
8+ |
JVM 最低版本通常由 AuthMe/Floodgate 构建决定,而非 FloodPass |
| AuthMe |
5.2+ (v3 API) |
仅限官方 AuthMeReloaded;已在 5.6.x 和 6.0.x 上测试。不支持内置 Bedrock 自动登录的分支 |
| Floodgate |
2.x |
加载时必须存在 |
依赖项
| 插件 |
是否必需 |
版本 |
用途 |
| Floodgate |
必需 |
2.x |
通过 Xbox Live 验证 Bedrock 玩家;所有 FloodPass 功能的基础信任源 |
| AuthMe (官方 AuthMeReloaded) |
必需 |
5.2+ |
FloodPass 用于将 Bedrock 玩家登录到的认证插件;不支持内置 Bedrock 自动登录的分支 |
| PacketEvents |
可选 |
2.x |
仅在启用 AuthMe 6.x Premium 验证 (enablePremium) 时需要 |
Geyser 本身不是 FloodPass 的插件依赖 —— Bedrock 连接性可来自任何 Geyser 设置(独立或代理),但 Floodgate 插件必须在此服务器上运行。
安装步骤
- 安装并配置 Geyser 和 Floodgate (2.x),以便 Bedrock 玩家可以加入
- 安装 AuthMe (5.2+);按照 Java 玩家的常规方式进行配置
- 将
FloodPass-x.x.x.jar 放入 plugins/ 目录并重启服务器
- 完成。无需更改任何 AuthMe 设置;两个捆绑的语言文件会在首次启动时自动提取
使用 Bedrock 账户验证:第一次加入时应显示“已注册并自动登录”,下次加入应显示“已自动登录”。
命令与权限
| 命令 |
权限 |
描述 |
/floodpass |
floodpass.admin (默认 OP) |
显示状态(启用、延迟、自动注册) |
/floodpass reload |
floodpass.admin |
重载 config.yml 和当前语言文件 |
别名:/fpass
已知限制
- Bedrock 账号存储在其 Floodgate 前缀名称下(例如默认前缀下的
.Steve)。稍后更改 Floodgate 用户名前缀会破坏现有账号的名称映射,并需要迁移 AuthMe 数据库——或者你可以保持原样:玩家会自动以全新的随机密码重新注册
bypass-nickname-check 通过识别踢出消息中嵌入的模式来认可 AuthMe 的拒绝行为;如果你自定义了 AuthMe 的 invalid_name_characters 消息,请保留 %reg 标签以确保检测功能继续正常工作
- 当 Floodgate
username-prefix 为空时,正版冲突守卫无法区分这两种身份——AuthMe 自身会将两个账号都存储在同一个名称下,这是不受支持的
- AuthMe 的昵称长度限制(
maxNickLength,默认值为 20)不会被绕过;带前缀的 Bedrock 名称(前缀 + 16 字符的游戏名 = 最多 17 个字符)符合默认设置
forceLogin 为 Bedrock 账号绕过 AuthMe 的双因素认证。对于经过 Xbox 验证的身份,这是预期行为,但请注意它同样适用于启用了双因素认证的 Bedrock 账号
- 在带有实验性对话框登录 UI 的 AuthMe 6.x(Minecraft 1.21.6+)上,Bedrock 玩家可能会在延迟自动登录完成之前看到登录对话框短暂闪烁
- AuthMe 的
/premium 命令针对 Java 账号,对普通 Bedrock 玩家会被安全地拒绝(他们的 Floodgate 前缀名称不匹配任何 Mojang 账号);Bedrock 玩家不需要此命令——FloodPass 已经为他们完成了登录,且 premium-conflict-guard 确保与正版账号游戏名发生碰撞的玩家仍可加入服务器
支持
我希望这个插件能帮到大家!我开发它是因为我运营着一个跨平台游玩服务器,并且希望继续使用官方的 AuthMe。如果你遇到任何问题,请留下反馈——谢谢!ouo
FloodPass
Floodgate Auto Login for AuthMe — Xbox-verified, so Bedrock players never type a password
简体中文
Official AuthMe only. FloodPass is built for the original AuthMeReloaded (5.x / 6.x). Do not install it on forks that already ship native Floodgate auto-login (such as AuthMeReReloaded) — the feature would run twice.
What It Does
Cross-play servers usually protect survival accounts with AuthMe. That works well for Java players, but Bedrock players arriving through Geyser + Floodgate have already proven who they are: they signed in with their Microsoft/Xbox account before the connection was even established. Making them type a password anyway is simply unnecessary.
FloodPass solves exactly that:
- For Bedrock players: nothing to type, ever. Registered accounts are signed in automatically about a second after joining; brand-new players are registered silently with a random password and signed in the same way
- For Java players: zero change, they go through AuthMe exactly as before
- Prefix-friendly: Bedrock names carrying the Floodgate prefix (for example
.Steve) pass AuthMe's default allowedNicknameCharacters regex with no AuthMe config change — only genuine Floodgate UUIDs are exempt
- Premium coexistence: a Bedrock player whose gamertag equals a premium-enrolled Java account (AuthMe 6.x
/premium + PacketEvents) joins normally while the Java account keeps its passwordless premium login
- For server owners: one jar, no AuthMe configuration changes, one command to manage everything; the trust decision stays where it belongs (Floodgate's Xbox Live verification)
Screenshot of a Bedrock Player Joining

How It Works
- A player joins; FloodPass listens at
MONITOR priority, by which time Floodgate identity data for the connection is available
FloodgateApi#isFloodgatePlayer(uuid) decides whether this is a genuine Bedrock connection; Java players are never touched
- After a configurable delay (20 ticks by default), AuthMe has finished its own join processing, and FloodPass takes over:
- Registered player:
AuthMeApi#forceLogin signs the account in without a password
- Unregistered player (if auto-register is on):
AuthMeApi#forceRegister registers the account with a random password and signs it in immediately
Security basis: a Floodgate identity only exists after the Bedrock client completed Floodgate's encrypted handshake with a valid Xbox Live token. A Java Edition client cannot forge that identity, so the passwordless path is only ever offered to players Microsoft has already verified.
Compatibility
| Component |
Requirement |
Notes |
| Server |
Spigot / Paper / Purpur / Folia 1.13+ |
Java 8 bytecode; older legacy servers (1.8+) generally load it too, untested |
| Folia |
Supported |
Per-entity scheduler via reflection, global scheduler fallback elsewhere |
| Java |
8+ |
The JVM floor is usually raised by AuthMe/Floodgate builds, not by FloodPass |
| AuthMe |
5.2+ (v3 API) |
Official AuthMeReloaded only; tested against 5.6.x and 6.0.x. Not for forks with built-in Bedrock auto-login |
| Floodgate |
2.x |
Required at load time |
Dependencies
| Plugin |
Required |
Version |
Purpose |
| Floodgate |
Required |
2.x |
Verifies Bedrock players through Xbox Live; the trust basis of every FloodPass feature |
| AuthMe (official AuthMeReloaded) |
Required |
5.2+ |
The login plugin FloodPass signs Bedrock players into; forks with built-in Bedrock auto-login are not supported |
| PacketEvents |
Optional |
2.x |
Only needed when AuthMe 6.x premium verification (enablePremium) is used |
Geyser itself is not a plugin dependency of FloodPass — Bedrock connectivity can come from any Geyser setup (standalone or proxy), but the Floodgate plugin must run on this server.
Installation
- Install and configure Geyser and Floodgate (2.x) so Bedrock players can join
- Install AuthMe (5.2+); configure it as usual for your Java players
- Drop
FloodPass-x.x.x.jar into plugins/ and restart the server
- Done. No AuthMe settings need to change; both bundled language files are extracted on first start
Verify with a Bedrock account: first join should say "Registered and signed in automatically", the next join "Signed in automatically".
Commands and Permissions
| Command |
Permission |
Description |
/floodpass |
floodpass.admin (default OP) |
Show status (enabled, delay, auto-register) |
/floodpass reload |
floodpass.admin |
Reload config.yml and the active language file |
Alias: /fpass
Known Limitations
- Bedrock accounts are stored under their Floodgate-prefixed name (for example
.Steve with the default prefix). Changing the Floodgate username prefix later breaks the name mapping for existing accounts and requires an AuthMe database migration — or you can simply leave it as is: the player is automatically re-registered with a fresh random password
bypass-nickname-check recognizes AuthMe's deny by the pattern embedded in its kick message; if you customize AuthMe's invalid_name_characters message, keep the %reg tag so detection continues to work
- With an empty Floodgate
username-prefix the premium conflict guard cannot tell the two identities apart — and AuthMe itself would store both accounts under the same name, which is unsupported
- AuthMe's nickname length limits (
maxNickLength, default 20) are not bypassed; prefixed Bedrock names (prefix + 16-char gamertag = 17 max) fit the default
forceLogin bypasses AuthMe's two-factor authentication for Bedrock accounts. For an Xbox-verified identity this is the intended behavior, but be aware it applies to Bedrock accounts with 2FA enabled as well
- On AuthMe 6.x with the experimental dialog login UI (Minecraft 1.21.6+), a Bedrock player may see the login dialog flash briefly before the delayed auto sign-in completes
- AuthMe's
/premium command targets Java accounts and is safely rejected for regular Bedrock players (their Floodgate-prefixed name matches no Mojang account); Bedrock players do not need it — FloodPass already signs them in, and premium-conflict-guard keeps gamertags colliding with premium accounts joinable
Support
I hope this plugin helps you all! I built it because I run a cross-play server and want to keep using the official AuthMe. If you run into anything, please do leave feedback — thank you! ouo
- Issues:
- Source:
- License: MIT
评论 0
登录后参与评分
还没有评论,来抢沙发吧