Reference

Permissions

Two nodes, what each one gates, and why there is nothing per mode or per difficulty.

There are exactly two nodes in the whole plugin. Everything a player does is behind one of them, and everything an administrator does is behind the other.

Permission	What it gates
`exyliapracticebot.use`	The `/bot` command itself — and therefore the main menu — plus `spawn`, `remove`, `tpme`, `tpto` and `reset`.
`exyliapracticebot.admin`	`/bot reload`, `/bot export` and `/bot import`.

exyliapracticebot.use is checked on the root command as well as on each of its five player subcommands, so taking it away takes away the whole command: a player without it cannot type /bot, cannot open the menu, and therefore cannot reach any of the buttons inside it.

exyliapracticebot.admin does not imply exyliapracticebot.use. An administrator who should also be able to spawn a bot needs both.

Neither node is declared in plugin.yml

The plugin ships no permissions: block, so neither node arrives with a default your permission plugin can read. Until you grant them, they fall back to Bukkit's behaviour for an unregistered node, which is operators only. Grant exyliapracticebot.use to the groups that are meant to have the plugin.

What the menus check

Nothing. The menu files carry no permission of their own, and neither do the actions they are wired to — spawn, remove, tp_to_bot, tp_bot_to_me, open_advanced_settings, reset_settings, set_mode, set_difficulty, toggle, cycle and adjust all run for whoever clicked.

In practice that is the same gate: the only way into the main menu is /bot, which needs exyliapracticebot.use, and the advanced screen is only reachable from the main one. It stops being the same gate the moment you wire one of the practicebot: actions into a menu belonging to another plugin — a hub selector, a kit screen, a cosmetics GUI. That button spawns or removes a bot with no node checked, so put the check on the item in that menu. See Menus.

The same is true of the API: another plugin that spawns a bot through PracticeBotService is not asking about permissions at all. Whether a player may be given a bot in a duel is that plugin's question, not this one's. See API.

Nothing per mode, nothing per difficulty

There is no node for Crystal PvP, none for Extreme, none for any piece of equipment, and none for the advanced settings screen. A player who may use the plugin at all may pick every mode at every difficulty and tune every slider the menu exposes. Gating a mode behind a rank is not something this plugin does — if you need it, remove the item from the menu file rather than looking for a node.

Examples

Giving the plugin to everybody and the admin half to staff:

/lp group default permission set exyliapracticebot.use true
/lp group staff permission set exyliapracticebot.admin true
/lp group staff permission set exyliapracticebot.use true

Taking the plugin away from one group while leaving it for the rest:

/lp group survival permission set exyliapracticebot.use false

Restricting where bots may be spawned is configuration rather than permissions: worlds in config.yml is the list of worlds a spawn is accepted in, and it applies to everybody. See Configuration.

Something missing on this page? Tell us on Discord