How to update Geyser and Floodgate

Download the latest Spigot builds of Geyser and Floodgate, stop your server, replace the old jars in the plugins folder, and start it again. Your config.yml files and Floodgate's key.pem stay in place, so your settings carry over.

When to update#

• Bedrock players suddenly see "Outdated server" after a Bedrock update.
• geyser version in the console says a newer build is available.
• A new Minecraft Java version is out and you have updated Paper.
• You hit a bug that a newer build fixes.

Because Bedrock clients update automatically on most devices, it is a good habit to update Geyser every week or two, or whenever a Bedrock update lands.

Step by step#

1. Back up. Create a backup or snapshot of your server first. Snapshots are a quick safety net if something goes wrong.
2. Download the latest Spigot builds of Geyser and Floodgate from geysermc.org/download.
3. Stop the server from the console.
4. In the file manager, open plugins/ and delete the old Geyser-Spigot.jar and floodgate-spigot.jar. Do not delete the Geyser-Spigot or floodgate folders; they hold your config.
5. Upload the new jars to plugins/.
6. Start the server and watch the console. Both plugins should load and Geyser should report the port it is listening on.
7. Run geyser version to confirm you are on the newest build.

If a jar name includes a version number, make sure only one copy of each plugin is in the folder. Two Geyser jars at once will cause errors.

Config changes between versions#

Geyser occasionally adds or renames config options. Usually it keeps your existing values and the new options use defaults. If an update changes the config format significantly, the release notes and the console will say so. Read the startup log after updating for any warnings.

Settings worth re-checking after a big update:

bedrock:
  address: 0.0.0.0
  port: 25571   # your Bedrock port

Updating extensions#

If you use Geyser extensions (in plugins/Geyser-Spigot/extensions/), such as a friends-list broadcaster for console players, check that they have a release compatible with the new Geyser and update them at the same time.

Updating on a BungeeCord network#

Update Geyser and Floodgate on the proxy, and Floodgate on every backend server, so all copies match. See Geyser on a BungeeCord network.

Automating it#

You can automate restarts with Schedules, but downloading new jars is still a manual step on a plugin setup. Some server owners use an auto-update plugin; if you do, pick a well-maintained one and still keep backups.

For version background, see Geyser version compatibility.