01 What Geyser and Floodgate each do
Geyser lets a supported Bedrock client communicate with a Java server. Floodgate addresses authentication for Bedrock players who do not have a paid Java account; it is not the translation layer itself. Use the official Geyser setup selector ↗ to choose the deployment that matches Paper/Spigot, a mod loader, proxy or standalone server.
This does not mean every Java modpack becomes playable from Bedrock. A pack that requires Java client-side gameplay mods has a different requirement from server-only additions. Before renting “crossplay hosting,” identify the players’ platforms and required mods, then ask the provider which actual Geyser deployment and client versions it supports.
02 Check the transport before following a UDP-only tutorial
The documentation checked on October 31, 2026 describes NetherNet, with TCP for discovery/signaling and UDP for gameplay on the configured Geyser port. Older RakNet-based instructions may mention UDP only. Follow the instructions for your installed Geyser build and Bedrock version; a network rule copied from an older guide can be incomplete.
| Check | What must match |
|---|---|
| Java listener | The actual Java server endpoint. |
| Bedrock/Geyser listener | The allocated port and transport for this deployment. |
| Router or hosting allocation | Every protocol required by the chosen transport. |
| Other applications | No conflicting service on a port Geyser needs. |
The current setup example uses 19132, but rented hosting may allocate another value. Ask for the real allocation. Do not open arbitrary ranges or change the Java port to the Bedrock port merely because their numbers look familiar.
03 Install one compatible deployment and restart cleanly
- Back up the Java server and record the current working configuration.
- Use the official selector to download the build for your server platform.
- For Paper/Spigot, the project documents placing Geyser-Spigot.jar in plugins and restarting.
- Configure the generated file with the actual allocated Bedrock endpoint and selected authentication method.
- If using Floodgate, follow its matching platform instructions and keep its private key material private.
- Restart through the normal service or game panel, then inspect the logs for the chosen build.
Do not fix an authentication error by indiscriminately disabling account checks on a public backend. Proxy deployments need the project’s matching forwarding and network-isolation setup. For name/identity confusion, read the UUID guide before moving player files.
04 Separate a Java failure from a Bedrock failure
First prove a Java player can join the intended world. Then test a supported Bedrock client locally where applicable, followed by a player outside your network. For console devices, use the project’s documented console connection guidance; do not promise that every console exposes an arbitrary-address field.
If Java works but Bedrock fails, collect the Bedrock build, Geyser build, transport, allocated endpoint, authentication mode and log error. A new Geyser release may require a different protocol-compatibility component; consult the live supported-version page instead of freezing one version number into a permanent tutorial. If both clients fail, return to basic server acceptance before reinstalling crossplay components.