Floodgate
Companion to GeyserMC. Allows Bedrock players to join without a Java account by using Xbox Live authentication.
AdminWhat is Floodgate?
Floodgate is GeyserMC's companion that removes the Java-account requirement for Bedrock players. Normally a Java server authenticates every player against Mojang; Floodgate instead authenticates Bedrock players through Xbox Live, then hands them to the server as recognised players (prefixed, by default, with a dot) without them needing to own Java Edition. It transfers their skin, supports linking a Bedrock account to a real Java account, and provides a Bedrock form API. It is essentially mandatory for any public cross-play server that does not want to gate Bedrock users behind a Java purchase.
Who it's for: Cross-play servers running Geyser that want frictionless Bedrock access — the standard second half of a Geyser cross-play install. It is built and maintained by GeyserMC Team and sits in the admin category.
Key features of Floodgate
- Xbox Live authentication
- Bedrock player prefixing
- Skin transfer
- Linked account support
- Whitelist integration
- Form API for Bedrock
How to install Floodgate
Floodgate runs on Spigot, Paper or Velocity servers. Maintained in lockstep with GeyserMC by the same team for current Spigot/Paper and Velocity versions.
- 1Stop your server, or have it ready to restart. Always back up your world and plugins folder before adding a new plugin.
- 2Download Floodgate.jar (a build matching your server version) and place it in your server's /plugins folder.
- 3Floodgate requires GeyserMC — install that plugin first or Floodgate will not start.
- 4Start the server fully. Floodgate generates its configuration files on first launch — stop the server, edit them to taste, then start again.
- 5Confirm it loaded by checking the console for Floodgate on startup, or by running one of its commands in-game.
Note: Floodgate requires GeyserMC — install both. Drop Floodgate into /plugins and restart; it generates a key file that, on a proxy network, must be copied to every backend server so they trust the same Bedrock authentication. Decide your username prefix and linking settings in its config.
Floodgate commands and permissions
Main commands
/fwhitelist- Manages whitelisting for Bedrock (Floodgate) players, which uses their Bedrock identity rather than a Java UUID.
/floodgate- Shows Floodgate status and version information.
Permission nodes
floodgate.command.fwhitelist- Allows managing the Bedrock-aware whitelist.
Floodgate FAQ
What does Floodgate do that Geyser does not?
Geyser translates the protocol so Bedrock clients can connect; Floodgate handles authentication so those Bedrock players do not need a paid Java account. Geyser gets them to the door, Floodgate lets them in without a Java login. You install both for account-free cross-play.
Do I need both Geyser and Floodgate?
Geyser is required; Floodgate is optional but almost always wanted. Without Floodgate, Bedrock players must own and link a Java account to join. With Floodgate, they join using their Xbox Live account alone, which is what most public cross-play servers want.
Why do Bedrock player names start with a dot?
Floodgate prefixes Bedrock usernames (a dot by default) to avoid clashes with Java usernames, since the two are separate namespaces. The prefix is configurable. It signals which players are on Bedrock and keeps their identities distinct in permissions and chat.
How does account linking work?
Floodgate supports linking a Bedrock account to a Java account so a player who has both keeps one identity, inventory and ranks across editions. Linking is initiated with the configured link command/flow; once linked, the player is recognised the same regardless of which edition they log in from.
On a network, why must the Floodgate key be shared?
Floodgate uses a key to sign and verify Bedrock authentication data. On a proxy network every backend must hold the same key so they all trust the proxy's Floodgate authentication. Copy the generated key file from the proxy to each backend server, or Bedrock players are rejected downstream.
Features
- Xbox Live authentication
- Bedrock player prefixing
- Skin transfer
- Linked account support
- Whitelist integration
- Form API for Bedrock
Commands
/fwhitelist/floodgatePermissions
floodgate.command.fwhitelist