Anti-cheat built for Bedrock players joining your Java server through Geyser/Floodgate.
Java anti-cheats model the Java client. Bedrock players arrive with different movement, touch controls, controllers and timing, so those anti-cheats either exempt them or flag legitimate mobile players. BedrockGuard analyses only Floodgate players and leaves Java players to your existing anti-cheat.
| Check | What it catches |
|---|---|
| Timer | The client runs faster than real time |
| Speed | Moving faster than vanilla allows (Speed effect and ice taken into account), with setback |
| Fly | Ignoring gravity, and hovering motionless in mid-air, with setback |
| Reach | Hitting from more than 3 blocks, with ping compensation (players and mobs) |
| Nuker | Several blocks broken in one tick, or too many per second |
| Scaffold | Blocks placed in mid-air, several per tick, or too fast |
| AutoClicker | Clicking faster than a human can |
| BadPackets | Values no legitimate client can send |
Every threshold is configurable and every check can be turned off. Violation levels decay over time.
ViolationEvent and violation level lookupsUp to 5 Bedrock players analysed at the same time. When one of them leaves, the next Bedrock player takes the free slot. Java players are never affected.
forward-player-ping at false (default): with true, Paper kicks real Bedrock clients/bguard alerts: turn alerts on or off for yourself/bguard info <player>: device, input mode, ping and violation levels/bguard exempt <player> [seconds]: temporarily exempt a player from movement checks/bguard reload: reload the configurationFull version, no player limit: https://payhip.com/b/PlDW4
Native Bedrock menus for what Geyser cannot translate: links, command autocompletion, enchantment levels, custom anvil recipes, villager trades on mobile.
Native Bedrock menus for what Geyser cannot translate: links, command autocompletion, enchantment levels, custom anvil recipes, villager trades on mobile.
