Your cart is empty
Looks like the spiders padded through here. Pick a plugin and it will show up here. Continue shoppingThis module is configured in modules/command-blocker.yml inside the PhoenixLobby folder.
The command blocker stops players from running the commands you list. It also hides them from the tab completion, so a blocked command is never suggested while typing and never completes its arguments either. Open it from Editor > Settings > Command Blocker.
Players with phoenixlobby.bypass.commandblocker keep using every command. The blocker only applies inside the lobby worlds, so a player that walks into a world the plugin is not active in gets the commands back.
With this option, you can edit the list of blocked commands. Entries are matched against the command name only, so the arguments do not matter, and the case does not either.
A * stands for anything, so bukkit:* blocks every command of that namespace and world* blocks worldedit along with worldguard.
An entry without a namespace also catches the namespaced form of the same command, so plugins blocks bukkit:plugins too. The opposite is not true: bukkit:plugins leaves the plain plugins alone.
With this option, you can turn the command blocker off completely without clearing the list.
enabled: true
blocked-commands:
- about
- ver
- version
- icanhasbukkit
- plugins
- pl
- help
- '?'
- bukkit:*
- spigot:*
- paper:*
Your guide to the docs
Ask me anything about Phoenix Lobby. I know these docs inside out, check the latest versions and changelogs, and can read your server logs.
Try asking
Your cart is empty
Looks like the spiders padded through here. Pick a plugin and it will show up here. Continue shopping