Geyser and Floodgate Guide for Java–Bedrock Cross-Play

Geyser translates Bedrock client traffic for a Java server, while Floodgate can provide a Bedrock-oriented authentication path. Cross-play is useful, but it does not make the two editions technically identical.

Quick answer

Run a supported Java server, install Geyser in the correct location, expose the required Bedrock UDP port, decide whether Floodgate is appropriate, and test gameplay with real Java and Bedrock accounts.

Why this matters

Protocol translation affects authentication, inventories, forms, movement, combat, resource packs, and plugin assumptions. A successful connection is only the first validation step.

Step-by-step

1. Choose deployment topology

Decide whether Geyser runs on the backend server or a proxy. Networks should document where authentication and player identity are handled.

2. Confirm ports and transport

Java normally uses TCP while Bedrock uses UDP. Allocate and expose the intended Bedrock port without opening unrelated services.

3. Install supported builds

Match Geyser and Floodgate versions to your proxy or server platform. Read release notes before combining them with authentication plugins.

4. Configure identity behavior

Understand username prefixes, UUID handling, linked accounts, and online-mode implications before importing permissions or player data.

5. Test edition differences

Verify join, chat, inventory, portals, forms, anti-cheat behavior, and important plugins from both editions.

What to verify before you finish

• The UDP port is reachable from an external Bedrock device.
• Java and Bedrock identities receive the intended permissions.
• Backups include Geyser and Floodgate configuration.
• Players are told which address and port to use.

Common mistakes to avoid

• Assuming Java mods become available to Bedrock clients.
• Opening the Java port but forgetting Bedrock UDP.
• Changing identity settings after players have accumulated data.
• Skipping mobile and console-specific tests.

Where Seedarc fits

Seedarc Minecraft Hosting provides the game-panel workflow used throughout this guide, including console, files, backups, schedules, databases, and controlled access for collaborators. The useful decision is not whether a feature sounds impressive, but whether it reduces the work and risk involved in the exact workload you are running.

Frequently asked questions

Is this safe to change on a live service?

Plan a maintenance window when changing Floodgate, proxy placement, or identity settings. Those changes can affect stored UUID-based player data and permissions.

What should I do if the change fails?

Return to the last known-good configuration, read the earliest relevant error in the logs, and change one variable at a time. If the issue is specific to the hosting layer, collect timestamps and the affected service ID before contacting Seedarc support.

Next step

Publish a short connection guide for each edition and keep cross-play limitations visible to players before launch. Review Seedarc Minecraft Hosting when you are ready to apply the workflow on Seedarc.