Skip to main content

Commands and Permissions

Geyser features many built-in commands that can be used by players or server owners.

info

When using BungeeCord and Velocity, you will need to use a permission plugin such as LuckPerms on the proxy server to assign permissions to players. Assigning permissions on the backend servers will not work.

Geyser commands & their permissions​

CommandPermissionDescriptiongeyser
Geyser root commandgeyser.commandThe permission required to see/run any Geyser commands.geyser help
geyser ?geyser.command.helpShows help for all registered commands.geyser advancementsgeyser.command.advancementsOpen the Java advancements menu.geyser dumpgeyser.command.dumpDumps Geyser debug information for bug reports.geyser listgeyser.command.listList all players connected through Geyser.geyser nethernetgeyser.command.nethernetShows NetherNet signaling status and diagnostics, for use with external signaling.geyser offhandgeyser.command.offhandPuts an item in your offhand.geyser reloadgeyser.command.reloadReloads the Geyser configurations. Kicks all players when used!geyser settingsgeyser.command.settingsOpens a settings menu allowing you to modify aspects of the world.geyser shutdown
geyser stopgeyser.command.shutdownShuts down Geyser.
This command only works on Standalone.geyser statisticsgeyser.command.statisticsOpen the Java statistics menu.geyser versiongeyser.command.versionShows the current Geyser version and checks for updates.geyser tooltipsgeyser.command.tooltipsToggle showing Advanced Tooltips (F3 + H on Java)geyser extensionsgeyser.command.extensionsLists all currently loaded extensions. This command is only registered if any extensions are loaded.geyser pinggeyser.command.pingShows the ping between the player and the Geyser instance.geyser optionsgeyser.command.optionsOpens the "pause screen additions" dialogue, if sent by the Java servergeyser quickactionsgeyser.command.quickactionsOpens the "quick actions" dialogue, if sent by the Java server.

Permissions for Geyser extensions​

For the following, <id> refers to the extensions' id.

CommandPermissionDescription<id> help
<id> ?geyser.command.exthelp.<id>Shows help for all commands registered by this extension.

Other Permissions​

Besides commands, there are other permissions that are used to guard specific Geyser features.

PermissionDescriptiongeyser.settings.serverAllow players to use the game settings menu. (Also requires player to have op.)geyser.settings.gamerulesDefines whether a user can alter gamerules in the game settings menu. (Also requires player to have op.)geyser.updateWhether this player will receive Geyser update notifications upon joining.

Permissions when using Geyser-Standalone/Geyser-ViaProxy​

Geyser-ViaProxy and Geyser-Standalone feature their own basic permission handler. To edit base permissions, open the permissions.yml file and add or remove permissions that Geyser players should receive when joining. See the file for more information.

You can further customize permission handling by creating a Geyser extension that makes use of Geysers API to deal with permission checking.

Permissions when using Geyser on platforms without permission handlers​

The following affects Geyser-BungeeCord, Geyser-Velocity, and Geyser-Fabric. These platforms unfortunately do not have built-in permission handlers. Because of that, you will need to grant permissions on those platforms manually using permission handlers, such as LuckPerms. Geyser's permission are listed above. For extension permissions, consult their documentation.

Alternatively, you can use LuckLink, a third-party Geyser extension, to automatically register permissions using LuckPerms.

Floodgate commands and permissions​

For Floodgate commands, see here.