Plugin commands not working: unknown command or no permission

When a plugin command fails, the message tells you which problem you have. "Unknown command" means the plugin is not loaded or the command name is different. "You do not have permission" means the plugin is working but the player lacks the permission node.

"Unknown command. Type /help for help."#

1. Run plugins in the console. If the plugin is missing or shown in red, it did not load. See plugin not loading.
2. Check the exact command name in the plugin's documentation. Some plugins use a short prefix, such as /lp for LuckPerms or /rg for WorldGuard regions.
3. Two plugins can register the same command. Use the namespaced form to choose one, for example /essentials:home versus another plugin's /home.
4. Commands with two slashes (such as //set in WorldEdit) are typed exactly like that.

"I'm sorry, but you do not have permission to perform this command."#

The plugin is loaded, but the player does not have the permission node. Operators usually have every permission, so it typically affects regular players and staff ranks.

Find the node

• Look at the plugin's documentation for its permission list. Nodes look like essentials.home or worldedit.region.set.
• Or let LuckPerms show you. Run this in the console, then have the player try the command:

lp verbose on

LuckPerms prints each permission it checks and whether it passed. Turn it off with lp verbose off.

Grant the node

Give it to a group so every member gets it:

lp group default permission set essentials.home true

Or to a single player:

lp user Steve permission set essentials.fly true

See LuckPerms basics for groups and ranks.

Works for operators only#

If a command works when you are an operator but not for others, it is always a permission issue. Give the specific nodes to a group instead of giving players operator status. Operators can run every command, including ones that can damage the server.

The command runs but nothing happens#

• Check the console at the moment the command is run. An error there points to a bug or a bad config.
• Some commands are disabled in certain worlds by the plugin's config (look for disabled-worlds or similar).
• WorldGuard regions can block actions such as building or using items even when the command itself is allowed.
• After editing a plugin config, restart the server or use the plugin's own reload command. See configuring plugins.

Running commands from the console#

In the Schokr console, type commands without the leading slash, for example lp user Steve info. Commands that need a player position (like sethome) only work in game.

Related#

• EssentialsX basics
• Install plugins on Paper