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

Command	Permission	Description
geyser Geyser root command	geyser.command	The permission required to see/run any Geyser commands.
geyser help geyser ?	geyser.command.help	Shows help for all registered commands.
geyser advancements	geyser.command.advancements	Open the Java advancements menu.
geyser dump	geyser.command.dump	Dumps Geyser debug information for bug reports.
geyser list	geyser.command.list	List all players connected through Geyser.
geyser offhand	geyser.command.offhand	Puts an item in your offhand.
geyser reload	geyser.command.reload	Reloads the Geyser configurations. Kicks all players when used!
geyser settings	geyser.command.settings	Opens a settings menu allowing you to modify aspects of the world.
geyser shutdown geyser stop	geyser.command.shutdown	Shuts down Geyser. This command only works on Standalone.
geyser statistics	geyser.command.statistics	Open the Java statistics menu.
geyser version	geyser.command.version	Shows the current Geyser version and checks for updates.
geyser tooltips	geyser.command.tooltips	Toggle showing Advanced Tooltips (F3 + H on Java)
geyser extensions	geyser.command.extensions	Lists all currently loaded extensions. This command is only registered if any extensions are loaded.

Permissions for Geyser extensions

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

Command	Permission	Description
<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.

Permission	Description
geyser.settings.server	Allow players to use the game settings menu. (Also requires player to have op.)
geyser.settings.gamerules	Defines whether a user can alter gamerules in the game settings menu. (Also requires player to have op.)
geyser.update	Whether 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.

• Install LuckPerms on the platform where you've installed Geyser (BungeeCord/Velocity/Fabric).
• To allow Geyser to automatically register permission defaults, install the LuckLink Geyser extension by downloading the LuckLink.jar and adding it to Geyser's extensions folder.
• Restart the server, and permissions should be automatically registered.

Floodgate commands and permissions

For Floodgate commands, see here.