Whitelist for Geyser: Fix Whitelist Issues for Bedrock Players

Mastering the Whitelist for Geyser: A Seamless Solution for Bedrock-Java Crossplay Running a Minecraft server that welcomes both Java and Bedrock players through Geyser and Floodgate is a fantastic way to unite your community. But anyone who has tried to enforce a whitelist on such a hybrid setup...

Download Whitelist for Minecraft 1.9

Original name: Whitelist

Minecraft: 1.9

FileVersionLoaderSize
Whitelist-2.1.jar1.9—28 КБDownload

Mastering the Whitelist for Geyser: A Seamless Solution for Bedrock-Java Crossplay

Running a Minecraft server that welcomes both Java and Bedrock players through Geyser and Floodgate is a fantastic way to unite your community. But anyone who has tried to enforce a whitelist on such a hybrid setup knows the pain: the vanilla whitelist command simply doesn't play nice with offline-mode accounts or Bedrock identities. You end up juggling UUIDs, temporarily disabling security, or manually editing JSON files. There is a smarter way. A lightweight plugin originally built for personal use now solves this exact headache, and it does so with elegant simplicity.

The UUID Mismatch That Breaks Vanilla Whitelists

Minecraft's built-in /whitelist add command is designed for premium Java accounts. It immediately tries to resolve a username to a Mojang UUID and stores that in whitelist.json. For an online-mode Java server, this works perfectly. However, when you introduce Geyser with Floodgate, Bedrock players don't have Mojang UUIDs—they use Floodgate's own UUID format. Similarly, if your server runs in offline mode, even Java players lack verified UUIDs. The result? The command either fails outright or stores a UUID that will never match the player trying to connect. Your whitelist becomes useless, and you're forced into risky workarounds.

Introducing the Whitelist for Geyser Plugin

This plugin overrides the standard whitelist system entirely, replacing it with a username-first approach that adapts to any player type. Instead of demanding a UUID upfront, it allows you to whitelist a plain username. The magic happens when that player actually joins the server: the plugin detects their real UUID (whether from Mojang, Floodgate, or offline mode) and automatically updates the whitelist entry. No more guessing, no more manual whitelist.json edits. It is purpose-built for servers that combine Geyser, Floodgate, and offline mode, but it works equally well as a more forgiving whitelist manager for any Java server.

How the Plugin Works Under the Hood

The logic is refreshingly straightforward. When you run /whitelist add PlayerName, the plugin stores that name with a blank UUID. The moment the player logs in, their actual connection UUID is captured and replaces the placeholder. From that point forward, the entry behaves like a traditional whitelist record—only now it is guaranteed to be correct. If you already have an active vanilla whitelist when you install the plugin, it automatically imports all existing players and disables the built-in system, so you lose nothing during the transition.

This design means you never have to disable your whitelist just to let a new Bedrock player join. Keeping the whitelist on at all times maintains your server's security while still allowing a smooth onboarding experience. It's a small change that eliminates a huge administrative burden, especially for public servers that frequently add new members.

Commands at Your Fingertips

The plugin introduces a clean set of commands that feel familiar yet are tailored to the hybrid environment. Here's what you can do:

  • /whitelist – Displays all available commands and their usage.
  • /whitelist add <username1> <username2> ... – Adds one or more players by username. Separate multiple names with a space.
  • /whitelist addUUID <UUID> – Directly whitelists a specific UUID. Currently limited to one at a time.
  • /whitelist remove <username1> <username2> ... – Removes players from the whitelist using their usernames.
  • /whitelist removeUUID <UUID> – Removes a specific UUID from the whitelist.
  • /whitelist list – Lists all whitelisted entries. If a UUID was added but the player hasn't joined yet, it shows "UUID:" followed by the raw identifier.

Notice that the add and remove commands handle multiple usernames at once, making bulk operations fast. The UUID-specific commands give you fine-grained control when you need to whitelist a known identifier before the player ever connects, which can be useful for certain automated setups.

Why This Approach Is a Game-Changer

Traditional whitelist management on Geyser servers often forces admins to turn off the whitelist, let the new player join, add them with a command, and then re-enable the whitelist. That brief window leaves the server exposed to anyone who might stumble upon the IP. With this plugin, the whitelist stays active the entire time. You simply add the username, and the player can walk right in. It's safer, faster, and removes the guesswork around which UUID format to use.

Another subtle advantage is the automatic import feature. If you've already spent time curating a whitelist, you won't have to start over. The plugin seamlessly migrates your existing entries and takes over the job. It's a drop-in replacement that respects your prior work.

Installing and Integrating the Plugin

Getting started is as simple as placing the plugin's .jar file into your server's plugins folder and restarting. Because it requires no configuration files or permission tweaks, it's ready to use immediately. For server owners who prefer a more visual and streamlined modding experience, a modern launcher can make the process even smoother. For instance, the foxygame.net launcher allows you to browse and install plugins directly from its menu, saving you from manual file transfers and ensuring everything stays up to date. That kind of convenience is a real time-saver when you're juggling multiple server mods and mechanics.

Once installed, the plugin automatically detects any existing whitelist and disables the vanilla system. You can then start using the new commands right away. There's no need to adjust any Geyser or Floodgate settings—the plugin works alongside them without conflicts.

Keeping Your Community Safe and Accessible

A whitelist is often the first line of defense against griefers and unwanted visitors, especially on family-friendly or private servers. The Whitelist for Geyser plugin ensures that this defense works flawlessly for every player, regardless of their platform. By removing the UUID barrier, it makes crossplay servers genuinely inclusive without compromising security. Whether you're running a small realm for friends or a large public network, this tool lets you focus on building and playing instead of wrestling with player data.

If you've ever found yourself staring at a whitelist.json file trying to figure out which UUID belongs to which Bedrock player, this plugin will feel like a breath of fresh air. It turns a messy, error-prone process into a one-command task. Give it a try, and you'll wonder how you ever managed your Geyser server without it.