BitAspire Wiki

Permissions & Conditions

Shared rules for permission-gated entries, priority, groups, conditions, and plugin hooks.

Permissions and conditions

Several BitAspire configs use the same matching pattern: define multiple entries, give each entry a permission or condition, and let priority decide the winner.

Common matching keys

KeyMeaning
permissionPermission required for this entry. Empty or missing often means fallback behavior.
priorityHigher numbers win when several entries match.
groupOptional grouping label used by features that resolve rank-like entries.
conditions.permissionsList of permissions that can select a profile.
defaultFeature-specific fallback flag.
enabledMaster toggle for a section or entry.

Typical profile pattern

profiles:
  default:
    priority: 0
    conditions: {}

  staff:
    priority: 100
    conditions:
      permissions:
        - "example.staff"

In this model, staff wins over default only when the permission condition matches.

Typical permission entry pattern

join:
  default:
    public: '&7Welcome &e{player}&7!'

  staff:
    permission: join.staff
    priority: 100
    public: '&cStaff &f{player} &7joined.'

Use the fallback entry for everyone, then add higher-priority entries for staff, members, or special groups.

Plugin hooks

Some sections depend on optional plugins. Common examples:

PluginCommon role
PlaceholderAPIExternal placeholders in text.
VaultPermission groups, chat metadata, prefixes, suffixes, and economy/chat integrations.
DiscordSRV or webhooksDiscord-facing output.
AuthMe, nLogin, OpeNLoginLogin-aware join/spawn flow.
SuperVanish, PremiumVanish, CMI, EssentialsVanish-aware behavior.

Optional means the plugin can load without it, but the related hook may not do anything until the plugin is present.

Operational advice

  1. Keep one fallback entry with low priority.
  2. Give special entries explicit permissions.
  3. Avoid equal priorities unless the feature documents deterministic tie-breaking.
  4. Prefer descriptive permission nodes such as sirplus.scoreboard.staff.
  5. Test with a real player account that has only the target permissions.

Last updated on

On this page