Build a Geyser compatibility check before a Bedrock client update

Applies to: Geyser; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

Bedrock clients can update before a server administrator changes anything. Geyser support also changes between builds. Keep a dated compatibility check for the client versions your community uses instead of promising that an old build will support every future release.

Record the starting point

Record the current Geyser build, Java server version, proxy version if present and any ViaVersion components. Save the current plugin files and configuration together. Choose one Java tester and one Bedrock tester with accounts that do not carry valuable trial items.

Work through the change

Read the current Geyser supported-version page and the release or download notes. Confirm the target build supports the actual client and backend combination you plan to test.
Use a separate copy of the service for the upgrade rehearsal. Keep its ports, external integrations and databases separate so the trial cannot admit production players or change their records.
Exercise login, chat, inventory use, a container, a teleport and any required resource pack. Check Java joining too, because a dependency update can affect the shared backend.
Record the exact build and client versions that pass. Plan a short maintenance window for the same tested file set rather than downloading an unrecorded build during the live restart.

Check the result

A useful check produces a repeatable list of working actions and a known recovery set. Include a disconnect and reconnect, because first login alone may miss identity or inventory problems that appear when a session resumes.

If the result differs

If the client version is unsupported, preserve the error and follow the project's release guidance. Adding ViaVersion does not guarantee support for every Bedrock transport or feature. Avoid changing online mode to bypass a protocol-version failure.

Return the staging copy to its saved plugin set if the trial fails. If a live upgrade changes data formats, use the complete matching recovery checkpoint rather than assuming an older JAR can read newer data.

Give a LuckPerms permission an expiry without leaving permanent access

Make a LuckPerms event rank expire while preserving other ranks

Limit a LuckPerms command permission to one Minecraft world

Keep a LuckPerms permission local to one network backend

Move a player along a LuckPerms track without replacing unrelated groups

Fix a LuckPerms prefix priority without changing chat formatting

Remove a direct LuckPerms exception without weakening its parent rank

Apply a small LuckPerms web-editor session to the correct server

Export LuckPerms data before changing its storage configuration

Find an inheritance cycle before it complicates a rank change

Keep default-player permissions separate from staff inheritance

Diagnose LuckPerms edits that reach one backend but not another

Check a player UUID before changing LuckPerms account data

Remove a staff member from one LuckPerms track without clearing their account

Give an EssentialsX rank a fixed home limit

Restrict one EssentialsX warp to an approved player group

Test EssentialsX teleport delay and movement cancellation

Add an EssentialsX cooldown to one utility command

Resolve an EssentialsX command alias conflict without removing either plugin

Check EssentialsX AFK kick exemptions for a staff role

Limit EssentialsX nickname changes without granting formatting control

Give staff a read-only EssentialsX player-information role

Recover from an accidental EssentialsX ignore setting

Restrict EssentialsX repair commands to the intended tool policy

Review EssentialsX command-disabled entries after a plugin change

Test an EssentialsX jail location without trapping a real player

Change the EssentialsX starting balance for new players only

Set EssentialsX maximum and minimum money limits with a boundary test

Change the EssentialsX currency symbol without changing stored money

Test an EssentialsX pay dispute using two controlled accounts

Review EssentialsX worth prices before enabling item selling

Explain an EssentialsX balance leaderboard that looks out of date

Trace an unexpected EssentialsX command charge

Back up EssentialsX money before a player-data migration

Verify a LiteBans temporary ban expires at the intended time

Test whether a LiteBans mute covers a private-message command

Build a LiteBans appeal-review role without punishment access

Check a LiteBans moderator’s maximum punishment duration

Find which plugin handled a ban command on a mixed-plugin server

Verify the server scope of a LiteBans network punishment

Investigate a LiteBans database connection failure without losing history

Reverse one appealed LiteBans punishment while preserving the audit trail

Test an AdvancedBan time layout before staff use it

Check AdvancedBan warnings without accidentally escalating a real player

Give an AdvancedBan helper access to history without ban powers

Check AdvancedBan storage before changing from local files to MySQL

Lift one AdvancedBan restriction after an approved appeal

Locate AdvancedBan correctly on a proxy network

Test SuperVanish visibility with separate staff and player accounts

Check whether a vanished SuperVanish moderator can pick up items

Verify flight is safe when a SuperVanish moderator reappears

Check silent chest inspection without changing container contents

Find a SuperVanish join or player-list information leak

Remove vanish access from a staff role without leaving a hidden account

Check PremiumVanish layered visibility after changing staff ranks

Verify PremiumVanish network vanish across Velocity backends

Check vanished staff interactions before a live investigation

Recognize the PremiumVanish API jar before installing an integration

Give GrimAC alerts to one observer without granting exemptions

Remove a GrimAC exemption and verify when checks resume

Collect a GrimAC prediction log for a false-positive report