Geyser + Floodgate: Bedrock <-> Java crossplay for Minecraft

Install Geyser and Floodgate on your Paper/Spigot/Velocity Minecraft server at VeryCloud so Bedrock players (Switch, Xbox, mobile, Win10/11) can join your Java server without a Java account.

Introduction

Geyser is a proxy translating Bedrock protocol to Java in real time. Floodgate, by the same author (GeyserMC), lets Bedrock players connect without needing a Java account — that's what turns a neat hack into a real community feature.

On your VeryCloud Wisp Minecraft server, installation takes 10 minutes.

Prerequisites

• An active Paper / Spigot / Velocity server at VeryCloud
• Access to Wisp Files
• A free UDP allocation (default Bedrock port: 19132)

Step 1: Allocate the Bedrock port

In Wisp:

1. Open Network on your Minecraft server
2. Create Allocation → port 19132/udp
3. Any UDP port works but 19132 is what Bedrock clients try first

💡 Bedrock is UDP, not TCP like Java. Pick the right protocol.

Step 2: Download Geyser and Floodgate

Official download: https://geysermc.org/download

Step 3: Upload plugins

In Wisp → Files → /plugins/:

1. Upload Geyser-Spigot.jar (or variant) and floodgate-spigot.jar
2. Save

Step 4: First boot

Restart the server. At boot, Geyser and Floodgate generate their configs:

/plugins/Geyser-Spigot/config.yml
/plugins/floodgate/config.yml
/plugins/floodgate/key.pem  <-- IMPORTANT: shared key

Step 5: Configure Geyser

Edit /plugins/Geyser-Spigot/config.yml:

bedrock:
  address: 0.0.0.0
  port: 19132
  motd1: "VeryCloud MC"
  motd2: "Java + Bedrock crossplay"
  server-name: "VeryCloud"

remote:
  address: auto
  port: 0
  auth-type: floodgate

passthrough-motd: false
passthrough-player-counts: true

Key points:

• bedrock.port must match the UDP allocation from step 1
• remote.auth-type: floodgate enables auth without a Java account
• passthrough-player-counts: true: Bedrock list shows real player count

Step 6: Configure Floodgate

Edit /plugins/floodgate/config.yml:

key-file-name: key.pem
username-prefix: "."
replace-spaces: true

The username-prefix: "." adds a dot before Bedrock player names. They'll appear as .BedrockName on Java side, avoiding name conflicts.

⚠️ With a proxy (Velocity, BungeeCord), key.pem must be shared across all backends. Copy to each at /plugins/floodgate/key.pem.

Step 7: Test connection

From Minecraft Bedrock:

1. Multiplayer → Servers → Add server
2. Server Address: VERYCLOUD_IP
3. Port: 19132
4. Save then Join

Step 8: Bedrock resource packs (optional)

For custom native Bedrock packs, place them in /plugins/Geyser-Spigot/packs/.

Troubleshooting

Bedrock players don't see the server

• UDP port 19132 properly forwarded and allocated
• Geyser actually started (check console: Started Geyser on...)
• Test from another network (mobile 4G)

"Could not connect to server" Bedrock-side

• Microsoft geo-restriction: player must be signed into a Microsoft account in the Bedrock client
• Port may not be open. Test with MCStatus

Bedrock names conflict with existing Java players

• Configure a more distinctive username-prefix in Floodgate

Performance drops on Bedrock connection

• Geyser converts every packet, it's CPU-intensive. Allocate more RAM/CPU

Useful commands

/geyser reload     # reload without restart
/geyser dump       # view connected Bedrock players
/floodgate         # Floodgate stats

Conclusion

With Geyser + Floodgate, your VeryCloud Minecraft server accepts Bedrock players without them buying Java. Best way in 2026 to broaden your community, especially casual or family servers.

Going further: Geyser on Velocity (multi-server config), custom Bedrock packs, monitoring conversion overhead.

Resources

• GeyserMC — Official Site
• Geyser GitHub
• Floodgate GitHub
• Geyser Wiki — Setup