Geyser bridges Bedrock clients to a Java server. It is powerful and also a support surface — version pins matter.
When it fits
- Friends on consoles/mobile who cannot run Java.
- You are willing to keep Geyser + Floodgate updated with the server.
When to skip
- Everyone can run Java.
- You run a heavy modpack (Bedrock parity is poor).
Ports
| Path | Port |
|---|---|
| Java players | 25565/TCP (or allocation) |
| Bedrock via Geyser | Often 19132/UDP (confirm in Geyser config + panel allocation) |
VERIFY whether your Chapter22 plan/egg exposes 19132. If not, ask support before advertising Bedrock joins.
Setup sketch (Paper)
- Install Geyser (and usually Floodgate) as plugins.
- Open/allocate UDP 19132 if required.
- Match Geyser’s supported Java version to your jar.
- Test with one Bedrock client before inviting everyone.
Related guides
Frequently Asked Questions
Is Geyser included by default?
Not always — treat it as optional. VERIFY it is offered on your egg before promising Bedrock support.
Which extra port?
Bedrock commonly needs 19132/UDP in addition to Java 25565/TCP.
When should I skip Geyser?
If everyone already owns Java, a pure Java SMP is simpler and more stable.
Need help?
If you are stuck after following this guide, open a ticket from the Chapter22 client area with the exact error, the port or DNS change you made, and whether the service listens locally (ss / Resource Monitor) but fails externally.
Build the server. Grow the community. Start your next chapter.