> For the complete documentation index, see [llms.txt](https://hayston.gitbook.io/flp-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hayston.gitbook.io/flp-wiki/compatibility-and-integrations/bedrock.md).

# Geyser and Floodgate

Geyser lets Bedrock players connect to Java servers. Floodgate lets Bedrock players join supported servers without a Java account. FLP does not replace them: install and configure them using the [Geyser](https://geysermc.org/wiki/geyser/setup) and [Floodgate](https://geysermc.org/wiki/floodgate/setup) guides first.

## How players log in

| Setup                    | Player login                                                                                                                              |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
| Geyser + Floodgate       | FLP's Bedrock policy can allow automatic registration or login. Support depends on the backend authentication plugin                      |
| Geyser without Floodgate | Login depends on Geyser's authentication settings. When a player logs in with a premium Java account, FLP can treat them as a Java player |

A matching username alone does not prove ownership of a premium Java account. Do not grant premium passwordless login to an unverified player.

In a proxy network, configure Bedrock policy on the proxy; see [Velocity](/flp-wiki/configuration-reference/velocity.md) or [BungeeCord](/flp-wiki/configuration-reference/bungeecord.md). The backend still needs a compatible authentication plugin. For AuthMe, see the [version comparison](/flp-wiki/compatibility-and-integrations/authme.md). Back up account data before changing Floodgate's player-name prefix: a name change can affect existing accounts.

## Fabric support

Velocity with Fabric/EasyAuth currently supports automatic login only for qualifying Floodgate players **without a linked Java account** and with an existing EasyAuth account. The account must be fully registered and its name and UUID must match the player; the proxy must also allow automatic login.

This setup does not currently create Bedrock accounts automatically, support linked Floodgate account login, or convert Bedrock accounts to premium Java accounts. If login fails, do not disable identity checks or invent a UUID; check the account and proxy settings first. See the [Fabric guide](/flp-wiki/install-and-deploy/fabric.md) for installation requirements.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hayston.gitbook.io/flp-wiki/compatibility-and-integrations/bedrock.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.