Minecraft: Java and Bedrock Crossplay on Your Server

Crossplay is a single toggle in your server settings. Three things to know before you flip it: it needs at least 5 GB of memory, it needs a Minecraft version the crossplay software supports (the toggle tells you if yours is not supported yet), and it runs on the Paper server type.

1. Open Minecraft (Bedrock) and go to the Servers tab.

2. Scroll down and choose Add Server.

3. Enter any name, then the Bedrock address and port from your Haptic dashboard. The port is different from the Java one, so make sure to use the Bedrock row.

4. Save and join. That is it, no extra account needed.

Consoles do not have an "add a server address" screen, so they need a one-time workaround. This is a limitation Microsoft, Sony, and Nintendo put on the console versions of Minecraft; every server host has the same constraint.

• BedrockConnect (DNS method, recommended): change your console's primary DNS to a BedrockConnect server (keep the secondary as 8.8.8.8), restart Minecraft, and open any Featured Server. You get a server list where you can enter your Haptic Bedrock address and port. Follow the current instructions from the BedrockConnect project or the GeyserMC console guide, since the DNS addresses can change over time.

• Xbox only (friend-session tools): community tools like MCXboxBroadcast can make a server appear in the Friends tab. These are self-hosted tools for advanced users; the DNS method above is the one we recommend and can help with.

If a console player is the only one who cannot join while phones and PCs can, it is almost always their join method or your whitelist. How Xbox, PlayStation, and Switch friends join your server walks through the DNS step and the whitelist command in full.

• Names have a . in front. A Bedrock player named Steve Jr shows up as .Steve_Jr (spaces become underscores). The dot prevents clashes with Java accounts and is how you can tell who is on Bedrock.

• Whitelist: a whitelisted server rejects Bedrock friends even when their address is correct, and they just see a generic connection failure. Bedrock players cannot be added with the normal whitelist, or from the dashboard roster, because Bedrock accounts are not Java accounts. Open your server's Console and run fwhitelist add TheirGamertag, with no dot in front, even though they appear in your player list as .TheirGamertag.

• Commands: include the dot when targeting a Bedrock player, for example /tp .Steve_Jr. If a command complains about the name, wrap it in quotes: /tp ".Steve_Jr".

• Skins: Bedrock players' skins are visible to everyone, including Java players.

• Account linking (optional): players who own both editions can link them by joining the server link.geysermc.org (in Minecraft, from both editions) and running /linkaccount, so they keep one identity and one inventory whichever edition they play from. Steps in the GeyserMC linking guide.

Minecraft Bedrock updates itself automatically on phones and consoles. Once in a while, a brand-new Bedrock version comes out before the crossplay software supports it. During that window (usually hours, occasionally a day or two), freshly updated Bedrock players may see an "outdated server" style error and cannot join.

If Bedrock players suddenly cannot join right after a Minecraft update on their device, restart your server first. If it persists a day later, check status.haptic.gg or message us.

The same logic applies in the other direction: when a new Java version releases, we may hold crossplay servers on the previous version briefly until the crossplay software supports the new one.

Crossplay is at its best on vanilla-ish survival servers. A few things do not translate perfectly:

• How it works: Bedrock players are translated into Java players by Geyser, the open-source standard used across the industry, plus Floodgate so they can log in with their Microsoft account (no Java purchase needed).

• Resource packs do not carry over. Java resource packs on your server will not show for Bedrock players (Bedrock uses its own pack format).

• Some plugins clash. The vast majority of plugins work fine, but a few that hook into logins or check UUIDs (certain auth or anti-cheat plugins) can block Bedrock players. If Bedrock players get kicked at login on a plugin-heavy server, tell us which plugins you run. The conflicts are well known and usually fixable with a setting.

• Small gameplay differences. Bedrock combat has no built-in attack cooldown display (the crossplay layer shows an indicator), some UI screens look different, and heavily custom content from mods may not appear correctly for Bedrock players.

• Xbox achievements stay off while playing on a crossplay server. That is a Minecraft rule for third-party servers, not something we control.

• Chat reporting is off. Bedrock players cannot sign chat messages the way Java accounts do, so we configure crossplay servers to accept unsigned chat automatically. Java players may see a small "chat messages can't be verified" notice; that is cosmetic and standard on every crossplay server. If Bedrock players cannot chat at all, restart your server: the setting is applied at startup. Details in Bedrock players can't chat.

1. Double-check the address and port. Bedrock needs the port from your dashboard's Bedrock: row, not Java's default.

2. Restart the Minecraft app on the player's device. This fixes a surprising number of cases, especially on mobile.

3. Did Bedrock just update? See the section above. Restart your server to pick up the latest crossplay version.

4. On a console? Make sure they are using the console join method above; consoles cannot join by typing an address directly.

5. "Unable to connect to world" with everything else correct: have the player try another network, for example a phone hotspot. Some routers and ISPs handle Bedrock's connection type (UDP) poorly.

Message us on Discord or email support@haptic.gg with the player's device type and the exact error message, and we will help you track it down.