Direct answer
Geyser translates Bedrock connections; Floodgate is one supported way for Bedrock accounts to authenticate without each player owning a Java account. Select authentication based on the current official deployment guide.
Recommended procedure
- Choose whether players will sign in with a Java account or use a supported Floodgate setup.
- If the bridge runs on a Velocity proxy, follow its proxy configuration and deploy authentication components at the positions specified by Geyser documentation.
- Keep proxy/backend forwarding secrets private and restrict direct access to backend servers.
- Test one Bedrock account and one Java account before inviting players.
Why this matters
Geyser protocol translation, Floodgate identity handling and Velocity/Paper player forwarding solve different problems. A successful Bedrock network connection does not guarantee that player identities and inventories are mapped correctly.
How to verify the result
After a clean login, verify the expected username/UUID behavior, inventory and permissions across reconnects and proxy server switches.
Version and compatibility notes
Do not toggle backend online-mode=false as a generic Geyser troubleshooting shortcut. Follow the current official authentication and forwarding instructions.
Official references
These sources were checked for the current MSH revision. Version-sensitive details should always be confirmed against the project documentation for the release you run.
Related guides
Help us improve this article
Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.