Commands and permissions
=== 🛡️ Commands 🛡️ ===
All Anarchy Stabilizer commands start with the base command /as.
Aliases: You can also use /anarchystabilizer or /astabilizer instead of /as.
/asor/as helpDescription: Displays basic plugin information (like version and author) and lists the available subcommands with their descriptions. This is the primary way to see command usage in-game.
Permission:
anarchystabilizer.command.baseDefault Access: Everyone (
true)
/as reloadDescription: Reloads the
config.ymlfile from disk. This applies any changes you have made to the configuration without requiring a full server restart. Very useful for testing and tuning settings live.Permission:
anarchystabilizer.command.reloadDefault Access: Operators only (
op)
(More subcommands may be added in future updates!)
=== 🛡️ Commands 🛡️ ===
=== 🛡️ Permissions 🛡️ ===
Anarchy Stabilizer uses a permission system to control access to its commands. It is recommended to use a dedicated permissions plugin (like LuckPerms, or any other Vault-compatible plugin) to manage these permissions for different player groups or ranks.
Below is a list of all permission nodes currently used by the plugin:
anarchystabilizer.command.baseDescription: Grants access to the base
/ascommand, which typically displays help information (available subcommands, plugin version).Default:
true(All players have this permission by default, allowing them to see basic help. You can override this with your permissions plugin if desired).
anarchystabilizer.command.reloadDescription: Grants access to the
/as reloadsubcommand, allowing the user to reload the plugin'sconfig.yml. This is typically reserved for administrators or trusted staff.Default:
op(Only server operators have this permission by default. You will need to grant this node explicitly to non-op staff ranks using your permissions plugin).
(More specific permission nodes might be added in the future, for example, to bypass certain limits or access new commands.)
=== 🛡️ Permissions 🛡️ ===
Last updated