Permissions

Default: true (everyone)

These work out of the box for any player, with no permissions plugin at all.

Staff-only nodes

"Do to others" nodes

A recurring pattern: the base node covers acting on yourself, the .others variant covers acting on another player. Both default to op.

/heal all and /feed all also require the respective .others node — "all" is treated as acting on other players, not yourself.

Bypass nodes

Skip a teleport's movement-cancellable warmup countdown entirely.

Private warps

as.warp.*        # access to every private warp
as.warp.<name>   # access to one specific private warp, e.g. as.warp.vault

Granted per-warp through your permissions plugin — these aren't pre-registered in plugin.yml since the actual set of warps is dynamic and created at runtime with /setwarp.

Remapping permission nodes

config.yml's permissions: section lets an admin repoint what node a command actually checks, without touching plugin.yml or rebuilding the plugin:

permissions:
  ban: alphasystem.ban
  unban: alphasystem.unban
  invsee: alphasystem.invsee
  whois: alphasystem.staff.whois
  socialspy: alphasystem.staff.socialspy
  maintenance: alphasystem.staff.maintenance
  # ... 40+ more entries, one per remappable command

In code, this is a single helper every remappable command routes through:

public boolean hasConfigPermission(CommandSender sender, String key, String defaultNode) {
    return sender.hasPermission(getConfig().getString("permissions." + key, defaultNode));
}

Change the value on the right of any entry to have that command check a completely different node — useful if your permissions plugin's naming convention doesn't match alphasystem.*, or if you want to fold several Alpha-system commands under one existing group node. Not every command is remappable this way — a handful of simple always-op utility commands (like the gamemode shortcuts) check a hardcoded node directly instead.