Commands

/heads

Permission: headdb.open (class-level @CommandPermission, applies to every subcommand). Player-only (@Default method takes a Player). Opens the heads-main menu blueprint via plugin.menus().computeAndOpen(player, "heads-main"). If opening fails (e.g. the blueprint isn't loaded), sends unexpected-error and logs the exception.

/heads search <term>

Permission: headdb.open. Player-only. Runs plugin.heads().search(term) (see Overview — indexing & search) then opens the heads-list menu blueprint, passing the matched heads in as the open parameter heads. Unlike the search-heads action, both a search failure and a menu-open failure send unexpected-error (a messages.yml key) and log the exception.

/heads reload

Permission: headdb.open + heads.reload (method-level @CommandPermission, added on top of the class-level node). Available to any CommandSender (not player-only). Calls plugin.loadConfiguration(), re-reading config.yml, categories.yml, messages.yml, and every menus/dialogs blueprint. Sends plain (non-messages.yml) feedback lines: "Reloading heads plugin...", then "Reloaded heads plugin!" on success or "Failed to reload heads plugin: <message>" on failure (also logged).

Permission summary

See also

• Actions — search-heads, the action equivalent of /heads search, meant for wiring inside a menu's own search-input flow rather than typed chat input.

• Configuration — Menu & dialog blueprints — where heads-main and heads-list must be authored.