FAQ
Geyser works as a translator, translating both the incoming and outgoing packets to a format both the client and server can understand. With this being said, it emulates a Minecraft: Java Edition client, so the server actually thinks you're joining from Java Edition. Regardless of the server or what plugins it has installed, you can join it with Geyser (as long as the server supports the latest vanilla (unmodified) Minecraft version).
Redstone, along with any other mechanics like commands, farms, etc., will work exactly like Java Edition since joining a Java Edition server and Geyser does not modify server behavior.
No, Geyser and all related projects are completely free and open-source, licensed under the MIT license.
Geyser should generally work fine with plugins, as we emulate a Java client. There are exceptions, though:
-
TCPShield requires
only-allow-proxy-connectionsdisabled without a paid plan. However, any paid plan will allow the support of Geyser - please contact their support for help setting this up.
Floodgate can cause issues with plugins as it modifies the login process. Please note that any offline mode authenticator plugins are only here for documentation; Geyser does not support offline mode usage.
- DynamicBungeeAuth produces invalid credentials for Bedrock players.
-
ExploitFixer thinks that Floodgate users are UUID spoofing - disable the
uuidspoofsetting in ExploitFixer's config. - JPremium alters the UUID of a player, causing Floodgate not to be able to get the Bedrock data from its map.
-
ProtocolSupport sometimes causes issues with Floodgate sayingProtocolSupport now works with the latest Floodgate.Invalid packet id: 27. Use ViaVersion instead if this keeps occurring - ProtocolSupportBungee changes how the login process works and therefore breaks the floodgate injection code.
- SayNoToMcLeaks prevents Floodgate from finishing its login system.
If you come across any more, please let us know via Discord.
This is a non-complete list of what platform each plugin version of Geyser is for, and the standalone version can be used for any as it isn't a plugin.
- Geyser-Spigot works with:
- Geyser-Bungee works with:
- BungeeCord
- Waterfall
- Any other forks of the above
- Geyser-Velocity works with Velocity
- Geyser-Sponge works with SpongeVanilla or SpongeForge
You only need Geyser and/or Floodgate on the BungeeCord server, as long as not using the Floodgate API. In this case, Floodgate is needed on the "backend" servers as well.
Generally, the IP that Bedrock players will join with is your Java IP and the defined port in your Geyser config in the bedrock section under port. For example, if the IP address Java players join with is test.geysermc.org, and the bedrock port is set as 19132, Bedrock players should join with the IP test.geysermc.org and port 19132.
You can add Bedrock resource packs to your Geyser installation in the packs folder of wherever the Geyser config is located. Bedrock clients will automatically download and load those resource packs. There is currently no automatic Java-to-Bedrock resource pack conversion, but you can convert any Java resource pack https://rtm516.github.io/ConvertJavaTextureToBedrock/ and add that to your server.
You can use the command /geyser offhand, which will swap the item in their main hand and offhand.
If there is a prefix on Floodgate players, you must include the prefix in the name. Floodgate also replaces all spaces in names with underscores, so be sure to replace any spaces with underscores when executing the command. If this does not work, put double-quotes around the name.
Example: /tp "*<bedrock_username>"
There are two ways you can do this. The first way is to turn off the whitelist using /whitelist off, then get the Geyser player to join, then run /whitelist add "*<bedrock_username>", then turn the whitelist back on using /whitelist on. (If using this method for a Bedrock account linked to an existing, whitelisted Java account, there is no need to also whitelist the Bedrock account; you may link the accounts then immediately turn the whitelist back on.) The second way is to add the player's UUID as given by Floodgate to the whitelist.json file and then run /whitelist reload.
Use this page. If this doesn't work, then try this method:
First, you'll need to get the XUID of the player. There are several third-party websites to find this, for example, this one (unaffiliated with Geyser). Make sure to choose "Hexidecimal." You'll need to enter the player's Xbox Gamertag, and, once submitted, and it should display the XUID in the format of xxxxxxxxxxxxxxxx. To turn the XUID into a UUID that Java Edition can recognize, you need to put the XUID in this format: 00000000-0000-0000-xxxx-xxxxxxxxxxxx. If formatted right, Java Edition should accept it as a UUID.
While yes, you can remove the prefix. It is generally recommended not to remove the prefix to prevent situations where a user's java and bedrock username are the same (ex: Bedrock Username: JohnDoe, Java Username: JohnDoe). While they have different UUIDs, they have the same username, which may cause conflicts with commands that involve a player name. If you want to remove the prefix to use commands, Try adding quotation marks around the name. Example: /tp "*<bedrock_username>"
No; Floodgate is only required if you wish to allow Bedrock clients to join without authenticating to Java servers. Without the Floodgate plugin, Geyser can either authenticate to Mojang in online mode, or join without authentication in an offline mode server (though this is unsupportable and dangerous as anyone can join your server and is against Mojang's EULA).
This is a Bedrock client issue caused by Bedrock being 32-bit and Java being 64-bit. For more information read here.
No, this is a translation tool to allow Bedrock players to connect to Java servers. It does not work the opposite way.
Yes, you can use Geyser as a plugin or a mod for your Minecraft server software running on Pterodactyl. There is also an official egg for the standalone version. It supports auto-updating and has all config options easily editable. You can find it here, download the JSON egg, and import it into your panel.
Unfortunately, Ngrok is TCP-only, so you will not be able to use Geyser with Ngrok. As an alternative, you can use playit.gg, which supports both TCP and UDP.
If the server has ViaVersion and/or supports the latest Minecraft version, yes. However, we are unable to support older versions of Minecraft due to a limitation in our Java support library.
The short answer: if a vanilla client can join the server, then so can Geyser.
The long answer: currently, there is no way for Geyser to translate the features that most mods add (blocks, items, etc.). Therefore, servers that require mods to be installed clientside are unsupportable through Geyser.
Geyser MC Auto Updater is an option at this time to auto-update Geyser through the command line. Note that this project is unaffiliated with Geyser.
GeyserUpdater (GitHub page/Spigot page) is a Spigot/BungeeCord plugin option for auto-updating. Please note that this plugin is also unaffiliated and unsupported by Geyser, and users should redirect support for the plugin to its Discord.
You sure can! Buycraft supports Java & Bedrock players via the Offline store mode (Recommended to be used with Floodgate)
(Currently, Buycraft does not support special symbols like * or -, so you'll have to change the Floodgate prefix to _ or remove it entirely.)
- Buycraft-> Create Webstore
- Select Game-> Minecraft Offline
- Continue-> Click "Create my Webstore"
- Name your server & Select currency-> Continue
- Select Game Server-> Continue
- Download the plugin version that best suits your server.
- Execute the secret command from your server's console
Your store is now set up to support Bedrock & Java players.
(Please note, if you are using a prefix with Floodgate, Bedrock players will have to enter the prefix.)
As mentioned above, bedrock players must include the prefix in their name
- Goto the admin page
- Expand settings on the left
- Click webshop
- Make sure 'Require premium accounts' is Off
- Then, if you are using floodgate in each package, make sure it uses the player's name in any commands, not their UUID
We aim to support any of the bedrock languages; see here for our Crowdin page, and below is a list of all the language codes. We also can add support for more languages, and please request them in the Discord server if you are willing to translate them. (Enabled clientside via https://www.curseforge.com/minecraft/mc-addons/translations-for-minecraft)
| Name | Code |
|---|---|
| Bulgarian | bg_bg |
| Czech | cs_cz |
| Danish | da_dk |
| German | de_de |
| Greek | el_gr |
| British English | en_gb |
| American English | en_us |
| Spanish | es_es |
| Mexican Spanish | es_mx |
| Finnish | fi_fi |
| Canadian French | fr_ca |
| French | fr_fr |
| Hungarian | hu_hu |
| Indonesian | id_id |
| Italian | it_it |
| Japanese | ja_jp |
| Korean | ko_kr |
| Dutch | nl_nl |
| Norwegian Bokmål | nb_no |
| Polish | pl_pl |
| Brazilian Portuguese | pt_br |
| Portuguese | pt_pt |
| Russian | ru_ru |
| Slovak | sk_sk |
| Swedish | sv_se |
| Turkish | tr_tr |
| Ukrainian | uk_ua |
| Chinese Simplified (China) | zh_cn |
| Chinese Traditional (Taiwan) | zh_tw |
| Name | Code |
|---|---|
| Afrikaans | af_za |
| Belarusian | be_by |
| Hebrew | he_il |
| Hindi | hi_in |
Redned started Geyser in July 2019. In May 2020, CubeCraft acquired the GeyserMC brand. This means that they govern the project (though at this time, they govern lightly). CubeCraft does not own the code of Geyser.