Geyser

Geyser does one thing, but a crucial one for a Czech server: it translates communication so that a player from the Bedrock Edition can connect to a Java server — from a phone, tablet, console, or the Windows Store version. The player doesn't need a Java account for that.

The server remains a Java server: plugins, maps, and permissions keep working. Geyser only translates the protocol and appears as a regular player on the server side.

Without Floodgate, players connect with their Bedrock account, which doesn't have the same format as a Java name. They therefore have to register (typically via AuthMeReloaded) and don't have the same name as in Java. Floodgate handles this layer: Bedrock players get a name with a prefix (typically a dot) and connect without registration.

When Geyser is working, you can tell by players with a dot at the beginning of their name in the tab list (if you use Floodgate) and by messages in the console about connections from Bedrock.

Some things Bedrock simply won't display: custom textures, some models, particles, or interface elements. A player on a phone will therefore see a simplified version — it's not a bug, but a property of translation between editions.

For a server, Geyser is a plus because it opens the game to people without a computer. It's worth saying out loud on the website and in the MOTD: that you can play from your phone too is a decisive piece of information for many players.

1. Find out the server version (/version) and whether you are using a proxy (BungeeCord, Velocity). Geyser has versions for both server and proxy.
2. Download Geyser from geysermc.org/download — choose according to your server type (Paper/Spigot directly, or proxy).
3. Upload the .jar to the plugins folder and restart the server.
4. In the console, a message will appear about Geyser and the generated configuration (plugins/Geyser-Spigot/config.yml).
5. In config.yml, check the port for Bedrock (default 19132, UDP protocol) and, most importantly, open it in the VPS firewall — otherwise players will not be able to connect.
6. Add Floodgate (geysermc.org/download) if you want Bedrock players to connect without registration and have their own name.
7. Align the auth-type setting in Geyser with Floodgate so they do not conflict (with Floodgate, a combination of floodgate and online mode is used).
8. Verify it yourself: install Minecraft on your phone, add the server with the address, and try to connect.
9. If a player cannot connect, check the firewall (UDP 19132) and whether Geyser is running in the right place (on the proxy, if you use a proxy).
10. Write on the website, in the MOTD, and in the menu that the server is also available from a phone, and include the address. Without that, people will not find out about it.

The Bedrock port (default 19132) is UDP, not TCP. If you don't open it in the firewall, players won't connect, even if Geyser is fine — so check this first.
When you use a proxy (BungeeCord, Velocity), Geyser belongs on the proxy, and players connect to the proxy address, not the game server.
Without Floodgate, Bedrock players have to register (typically via AuthMeReloaded) and have different names than in Java. Floodgate solves this, but names get a prefix (a dot) — set permissions and the permissions plugin accordingly.
Geyser must be updated when the Minecraft version changes. If players from phone can't connect after updating the game, look for a newer Geyser and Floodgate in the same version.
Bedrock doesn't display everything: custom textures, models, particles, and part of the interface are shown simplified. Players ask about this, it's worth explaining on the website.
Some plugins don't recognize Bedrock players (account verification, statistics). If something doesn't work only from phone, it's not a Geyser error — that plugin didn't count on Bedrock.
Verify that Bedrock players count toward the online player count. If yes, you'll see them in statistics and metrics as well.