Skip to content

Permission Management

Innectic edited this page Nov 8, 2026 · 5 revisions

Permission rules and priority

Rules can allow (true), deny (false), or be unset. Unsetting removes a direct rule so inheritance or Bukkit defaults can decide.

/permissify player setpermission Innectic example.permission false
/permissify player check Innectic example.permission
/permissify player unsetpermission Innectic example.permission

Priority

  1. Direct player rules override group rules.
  2. Between active memberships, higher-weight groups win.
  3. Denial wins equal-weight permission conflicts.
  4. Inside a group, its own rules override inheritance.
  5. Conflicting parents use their weights, with denial winning ties.

Main-group selection is separate: equal-weight memberships choose an alphabetical main group, while a denial from another equal-weight membership can win a particular node.

Explanations

/permissify player check <player> <permission> shows the winning explicit rule, direct/group source, inheritance path, membership weight, expiry and main group.

For online players, it also shows Bukkit's actual result. Bukkit permission children, defaults, operator status and other plugins can affect that result. Offline players have no live Bukkit result. No explicit rule does not necessarily mean denied access.

Permission lists mark denial with a leading minus sign. They show resolved explicit rules, not every permission Bukkit might supply through defaults or children.

See Group Management and Player Management for commands.

Clone this wiki locally