- You must own/manage the server in order to add Floodgate. If you do not own the server, Floodgate does not allow you to bypass logging into Java servers that require a Mojang Java account.
- You must either be running Geyser as a plugin, or be running Geyser Standalone. Floodgate does not replace Geyser.
floodgate-spigot.jarcannot be installed on CraftBukkit/Bukkit servers.
Any reference to Spigot here also refers to any compatible server software such as Paper.
For BungeeCord/Velocity setups: you only are required to install Floodgate on the BungeeCord or Velocity proxy unless you want to use the Floodgate API on the backend servers - see below for the installation process.
Note: Installing Floodgate on the backend servers will allow Bedrock player skins to display without the Bedrock player having to switch backend servers.
- Download the Floodgate plugin from here and add it to your plugins folder on your frontend server.
floodgate-spigot.jarfor Spigot, Paper, etc
floodgate-bungee.jarfor BungeeCord, Waterfall, etc
- Change the
auth-typein the Geyser config to
- Restart/start up the server.
ONLY do this step if using Geyser Standalone:
- Copy the
key.pemfile in the Floodgate config folder to the same directory as Geyser Standalone. DO NOT DISTRIBUTE THIS KEY TO ANYBODY! This key is what allows for Bedrock accounts to bypass the Java Edition authentication, and if anyone gets ahold of this, they can wreak havoc on your server.
Installing Floodgate also on Spigot servers behind BungeeCord or Velocity
This is only needed when you want to use the Floodgate API on your Spigot server(s) behind a proxy.
- Install Floodgate on the proxy and on all backend servers as per the previous instructions
ip_forwardin your BungeeCord
config.ymlif using BungeeCord
- Start the proxy server.
- Edit the Floodgate config on your proxy server and set
- Copy the
key.pemfile in the proxy Floodgate config folder to all Spigot servers’ Floodgate config folder. DO NOT DISTRIBUTE THIS KEY TO ANYBODY! This key is what allows for Bedrock accounts to bypass the Java Edition authentication, and if anyone gets ahold of this, they can wreak havoc on your server.
- Restart the Spigot servers and proxy server.
Changing/disabling the prefix
Please note: we do not recommend removing the prefix unless you are certain that no one will share a username between a Java and Bedrock player. Duplicated usernames will cause weird situations, like being unable to teleport to one of the players.
In your Floodgate config, change
username-prefix to whichever prefix you desire - you can set it to
"" and there will be no prefix.
On some older Paper servers (or any forks that use them), you may need to also shut down your server and delete your
usercache.json file located in the same folder as your server jar to prevent users who already joined from having the old prefix. See this issue for more information.
Obtaining UUIDs for Floodgate players
Check your server logs, or use this page. If this doesn’t work, then try this method:
First, you’ll need to get the XUID of the player. There are several third-party websites to find this, for example, this one (unaffiliated with Geyser). Make sure to choose “Hexidecimal.” You’ll need to enter the player’s Xbox Gamertag, and, once submitted, and it should display the XUID in the format of
xxxxxxxxxxxxxxxx. To turn the XUID into a UUID that Java Edition can recognize, you need to put the XUID in this format:
00000000-0000-0000-xxxx-xxxxxxxxxxxx. If formatted right, Java Edition should accept it as a UUID.
If you’re using the Bukkit version of Floodgate, download the Placeholder plugin here. Using the placeholders shouldn’t require additional setup other than having PlaceholderAPI installed. See the section above on installing Floodgate on backend servers if you wish to use this on BungeeCord.
If you’re using the Bukkit version of Floodgate, there is an unofficial plugin that adds Skript support here.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.