Plugins that work well with Bedrock cross-play

If your server lets Bedrock players in through Geyser, most plugins keep working, because to the plugin a Bedrock player is a normal player. A few things behave differently. Here is a short checklist.

Names with a dot

Floodgate adds a dot in front of Bedrock names, so Steve becomes .Steve. Anything that mentions a player by name needs the dotted version: whitelists, /op, LuckPerms commands, CoreProtect lookups and claims. When a command says a player "was not found", the missing dot is the usual reason.

Menus and inventories

Chest-style menus (shops, kits, warps) work, but they look different and are harder to use with touch controls. If you use a menu plugin, test it on a phone before you rely on it. Many menu plugins have a Bedrock-friendly form mode that Floodgate can show, which is easier to tap.

Building tools

WorldEdit commands work from the console and in game, but the wand and visual helpers rely on Java mods, so Bedrock players get commands only. Keep building tools for staff on Java.

Claims and protection

GriefPrevention, CoreProtect and similar plugins work the same: they see a player placing and breaking blocks. Bedrock players can use a golden shovel to claim, though the controls feel different on a console, so show new players how.

Chat and Discord

DiscordSRV sees Bedrock chat like any other chat. Bedrock players' names appear with the dot, which is a handy way to tell them apart in Discord.

Resource packs

Geyser can send a pack to Bedrock players, and it can require it. Java resource packs do not carry over by themselves, so a server that depends on a custom pack for its look needs a Bedrock version of it.

Test with a real device

The quickest way to find the odd plugin is to join from a phone yourself. Do it once after every big change, and you will catch the problems before your players do. See how to let Bedrock players join for the setup.