Fixing Anticheat Kicks for Bedrock Players on Geyser

Why do Bedrock players get kicked by an anticheat?

Bedrock players usually get kicked because a check written for Java clients misreads movement, mining, or input that Geyser translates into Java packets. Confirm which check fired, adjust that check for Bedrock players, and test the change on staging before production.

Geyser is the translation layer that lets Bedrock clients join a Java server. Floodgate identifies which connected players came from Bedrock, so other plugins can treat them differently. Per GrimAC docs, Geyser players are exempt. Other anticheats handle this differently, so read each vendor's documentation instead of assuming the same behavior.

How do I confirm which check caused the kick?

A kick from a network timeout or proxy disconnect looks different from a check kick. Compare the disconnect reason before you blame the anticheat. When the reason points to a check, follow these steps.

• Note the player's name, the kick message, and the exact time.
• Open the anticheat alert log and find the check name and violation level for that player at that time.
• Confirm the player's platform. Floodgate marks Bedrock accounts, so follow the Floodgate setup guide to check how your server reports them.
• If possible, reproduce the same action with a Java test account on staging.
• If only Bedrock accounts trigger that check, the check is the likely cause. Record it before you change anything.

What evidence should I keep for a Bedrock kick?

Keep the alert timestamp and the player's recent actions together. A flag that fires after a menu interaction, a form, or a fast block placement reads differently from one that fires during a clean fight. Staff reviewing the case later need that context to decide whether the flag reflected a real violation.

Store the case with the check name, violation level, client platform, and the Geyser and Floodgate versions in use. Without those versions, a fix that works today may be impossible to explain after the next update.

What should I check in Geyser and Floodgate?

Run Geyser and Floodgate versions that match each other and your server software. Read the Geyser setup guide and the Floodgate wiki for the current settings. This article does not list their configuration keys, because those change between releases.

If you run a proxy with backends, keep the Geyser and Floodgate setup consistent across the proxy and each backend that accepts Bedrock players. A mismatch there can make one backend behave differently from the others.

How do I set a FairPlay Bedrock exemption?

The FairPlay configuration reference lists Bedrock eligibility as a policy area in config.yml and gives the example setting bedrockCheck=true. Back up the generated file, then change only the Bedrock eligibility option for the check you need to adjust.

Apply the change per check where you can. A broad exemption removes coverage for every Bedrock account, which is harder to justify in a staff review.

How do I exempt Bedrock accounts with LuckPerms?

Place Bedrock accounts in a dedicated group. How you assign them depends on your login setup. Many networks use a Floodgate-aware plugin or a naming rule. Then grant only the exemption node that your anticheat's permission reference lists for the check you are tuning.

/lp creategroup bedrock-players
/lp group bedrock-players permission set <exemption-node-from-permissions-docs> true
/lp user <bedrock-test-account> parent add bedrock-players

How do I update Geyser, Floodgate, and the anticheat safely?

Update the three together in staging, then rerun your Bedrock test. Version skew between a Geyser release and an anticheat check is a common reason a fix stops working after an update.

Read the release notes for each plugin. Keep a copy of the previous jars and config files so you can roll back one layer at a time.

• Stop the staging server and copy the current plugins folder and config files.
• Update Geyser and Floodgate to matching releases for your server software.
• Update the anticheat, keeping PacketEvents at the release its docs recommend.
• Start the server and read the console for errors on each plugin.
• Join with a Bedrock test account and a Java test account, then repeat the action that caused the kick.

What have we not verified?

We have not tested any Geyser, Floodgate, or anticheat release combination, and this article makes no claim about accuracy or false-positive rates on Bedrock traffic. Your own staging run with Bedrock accounts is the evidence that counts.

Use the vendor docs for each anticheat. Where a vendor does not document Bedrock handling, test it before you open the server to Bedrock players.