How to link a Java and Bedrock account with Floodgate
Let players use one identity on both editions: Floodgate account linking shares the Java name, UUID, inventory and permissions with Bedrock.
Updated · 2 min read
If someone plays on both Java and Bedrock, they can link the two accounts so the server treats them as the same player. When linked, the Bedrock player joins with the Java username, UUID and skin, so they keep the same inventory, homes and permissions on either edition.
How linking works
Floodgate supports two kinds of linking:
| Type | Where links are stored | Setup |
|---|---|---|
| Global linking | GeyserMC's central service, shared by all Floodgate servers | On by default |
| Local linking | Your own server's database | Needs extra configuration |
Most servers just use global linking. A player links once and it works on every server that has it enabled.
Global linking (recommended)
Global linking is enabled by default in plugins/floodgate/config.yml:
player-link:
enabled: true
enable-global-linking: true
To link, a player follows the instructions on the GeyserMC global linking page, which involves joining GeyserMC's linking server from both editions and confirming with a code. See global linking on the GeyserMC wiki for the current steps and address.
After linking, they simply rejoin your server from Bedrock. They appear under their Java name with no Floodgate prefix.
Local linking
Local linking keeps links on your server only, with the linkaccount and unlinkaccount commands. It needs enable-own-linking: true and a database backend for Floodgate. Floodgate offers a file-based SQLite option, which works fine on Schokr; Schokr has no built-in MySQL, so if you want a shared database across a network, use an external provider.
Because the setup differs between Floodgate versions, follow the local linking guide on the GeyserMC wiki.
Important things to know
- Data does not merge. A linked Bedrock player uses the Java account's data. Anything they built up as
.Name(inventory, homes, permissions) stays with the old Floodgate UUID and is not visible while linked. Link early, or move items to the Java account first. - Whitelist and bans: after linking, whitelist and ban the Java name. See whitelist Bedrock players.
- Permissions: assign LuckPerms groups to the Java account. See LuckPerms permissions for Bedrock players.
- Skins: the Java skin is used.
Requiring a link
Floodgate has a require-link option under player-link. When enabled, Bedrock players who have not linked a Java account cannot join. Use it only if you want every Bedrock player to also own Java.
Unlinking
With global linking, players unlink through GeyserMC's linking service. With local linking, they run unlinkaccount on your server. After unlinking, the Bedrock player goes back to their prefixed Floodgate identity.
Troubleshooting
- Link not taking effect: have the player fully leave and rejoin; check
player-linkis enabled. - Linked player lost their items: they are now on the Java UUID. Unlink to reach the old Floodgate data, or restore from a backup.