Java + Bedrock

Last updated 9 September 2026. Report a discrepancy through the GeoNations Discord.

Java and Bedrock players use the same survival world, economy, claims, and rules. This page covers the places where the Bedrock client requires a different connection setting or interaction.

Most server plugins produce interfaces for Java clients. Bedrock support therefore uses translated interfaces for menus, holograms, chest shops, custom text, and the player list. If an interface displays raw formatting or unreadable text, open a ticket and include the Bedrock version and a screenshot.

Connection

Enter the port manually. Bedrock does not use the DNS record that supplies the Java connection port.

Geyser translates the Bedrock connection for the Java server, and Floodgate allows the connection without a Java account. No account link is required. Bedrock versions outside the range supported by the installed Geyser version are rejected with a version message.

Player names

Bedrock names include a server prefix so they cannot conflict with Java account names. Spaces in a gamertag are also converted to underscores. When entering a player name in a command, copy it exactly as displayed in the player list. The original profile name may not resolve as an online player.

The displayed Bedrock name works with /pay, /tpa, /trade, and chest shop signs. Chest shop name validation accepts both Java and Bedrock names.

Chat actions and links

Bedrock clients cannot activate clickable chat actions. A chat line that acts as a button on Java appears only as text on Bedrock.

Everything a click would have done is reachable by typing. Where a message offers you a click, look for the command in it and type that instead.

The same limitation applies to links. /map prints the live map address. Java can open it as a chat link, while Bedrock displays it as text that must be entered into a browser.

Region names in commands

Region names cannot contain spaces at all — they are written with underscores from the start, and it never converts back. So a region displayed with a space in its name is only reachable in commands with an underscore. Accepting an invite, typed in full:

/lands invites accept Their_Region_Name

Capitalisation does not matter, but the underscores are required. A name entered with spaces may fail without displaying an error. This applies to Java as well, although Java players may be able to accept the invitation through a clickable chat action.

Touch controls

On the default touch layout, tapping to attack or interact can drop whatever you are holding. Players lose swords in fights this way and assume they were stolen.

To prevent this, open Settings, select Touch, and choose D-Pad or Crosshair instead of the default tap layout.

Chest menus and item descriptions

The menus opened by /menu, /guide, /shop, /ah, /wars, and /lands use chest interfaces and can be used on Bedrock.

Java displays item descriptions when the pointer hovers over a menu item. On Bedrock, press and hold the item to display the same description.

Movement checks

Geyser translates Bedrock movement before it reaches the Java server. Gravity and speed simulation checks are disabled for Bedrock because the translated movement does not match the Java movement model reliably. Other anticheat checks remain enabled.

Player list layout

Java displays the player list in fixed columns. Bedrock cannot render that layout, so it receives a plain sorted list with the same header and footer. This is a display difference and does not indicate a different rank, account state, or permission set.

Decorative small capital characters were also removed from the shared menus because the Bedrock font displays some of them as empty boxes. If menu text appears as blank squares, include the affected menu in a ticket.