Pre-launch Ordering isn’t open yet. Email us and we’ll tell you when it is

Wispdock home Get your server

Java, Bedrock and crossplay with Geyser

Java and Bedrock share a name but not a network protocol, so neither can join the other’s servers on its own. Geyser bridges the gap on a Java server.

Wispdock’s control panel isn’t built yet. Where a step says “in your control panel”, use whatever your host gives you for files, the console and start/stop. The Minecraft side works the same everywhere.

Crossplay starts with a Java server and a bridge; native Bedrock hosting is a separate setup with different software support.

The two editions

  • Java runs on Windows, macOS and Linux. It has mods, plugins and third-party launchers. Default server port: TCP 25565.
  • Bedrock runs on phones, tablets, consoles and the Windows Bedrock app. It has add-ons and Marketplace content, but no Java mods. Default server port: UDP 19132.
  • If everyone in your group plays Bedrock, a plain Bedrock server is simpler. If it’s a mix, or you want plugins, run Java with Geyser.

How Geyser and Floodgate work

Geyser translates between the Bedrock and Java protocols, so Bedrock players can join a Java server. It runs as a plugin on Paper, on a proxy such as Velocity, or as a mod on Fabric and NeoForge.

Floodgate lets those Bedrock players join with just their Microsoft account, without owning Java Edition, while the server keeps online-mode=true.

Set it up on Paper

  1. Download the Spigot/Paper builds of Geyser and Floodgate from geysermc.org.

  2. Stop the server, put both jars in plugins and start it once so they create their config files.

  3. Open plugins/Geyser-Spigot/config.yml. The Bedrock port is 19132 by default. If your host gives you a different UDP port for Bedrock, set it there. Check that the auth type in the same file is floodgate.

  4. In your control panel, make sure that UDP port is open for the server, then restart.

  5. Bedrock players add the server with the same address and the Bedrock port.

Bedrock player names

Floodgate puts a prefix in front of Bedrock names so they can’t clash with Java names. The default is a dot, so the Bedrock player Steve shows up as .Steve. Use that name with /op and /ban, and /fwhitelist add for the whitelist.

Floodgate also supports linking a Java and a Bedrock account, so one person keeps one inventory on both.

What doesn’t carry over

  • Content mods. A Forge or NeoForge mod that adds blocks or items needs the mod on the client, and Bedrock can’t load Java mods. Geyser works best on Paper, or with mods that only run on the server.
  • Some mechanics feel different to Bedrock players, combat and some redstone timing among them, because they play Java rules through a translation layer.
  • Custom items and resource packs need extra setup to show up correctly on Bedrock.
  • Console players need a workaround to join any custom server. Ask us before you plan around them.

Frequently asked questions

Can Bedrock players join a Java server?

Not on their own. With Geyser installed on the Java server they can, and Floodgate lets them sign in with just their Microsoft account, without owning Java Edition.

Which port do Bedrock players connect to?

The Bedrock port set in Geyser’s config.yml, which is UDP 19132 by default. Java players keep using the normal TCP port, usually 25565.

Why does a Bedrock player’s name start with a dot?

Floodgate adds a prefix so Bedrock names can’t clash with Java names. The default prefix is a dot, so use .Steve with /op, /ban and /fwhitelist add.

Do Java mods work for Bedrock players?

Mods that add blocks or items don’t, because they need the mod on the client and Bedrock can’t load Java mods. Mods that only run on the server are fine.

Still stuck? Send us the details and your latest.log.