BlazeBans/Permissions

Permission reference

Every node BlazeBans checks, grouped by what it lets someone do. Run `/blazebans permissions` in game for the same list from the running server.

Nothing defaults to true. The two lockdown bypass nodes default to op; everything else has to be granted.

Administration

Node	Grants
`blazebans.admin`	Full access. Bypasses scope checks, hierarchy, and exemptions. Owners only
`blazebans.command.help`	`/blazebans` and `/blazebans help`
`blazebans.command.reload`	`/blazebans reload`
`blazebans.command.settings`	`/blazebans settings`, the per-staff notification menu
`blazebans.command.editor`	`/blazebans editor` and `/blazebans trust`
`blazebans.command.addons`	`/blazebans addons`
`blazebans.command.dump`	`/blazebans dump`
`blazebans.command.import`	The import commands
`blazebans.update.notify`	Update notifications on join

/blazebans version needs no permission.

Punishing

Node	Grants
`blazebans.command.ban`	`/ban`, `/tempban`
`blazebans.command.mute`	`/mute`, `/tempmute`
`blazebans.command.warn`	`/warn`
`blazebans.command.kick`	`/kick`
`blazebans.command.ipban`	`/ipban`, `/tempipban`
`blazebans.command.ipmute`	`/ipmute`, `/tempipmute`
`blazebans.command.punish`	`/punish`, which applies a ladder step
`blazebans.command.punishgui`	`/punishgui`. Also needs `blazebans.command.punish`

Revoking and editing

Node	Grants
`blazebans.command.unban`	`/unban`, `/pardon`
`blazebans.command.unmute`	`/unmute`
`blazebans.command.unwarn`	`/unwarn`
`blazebans.command.editpunishment`	`/editpunishment`
`blazebans.command.staffrollback`	`/staffrollback`, bulk revocation

Reading records

Node	Grants
`blazebans.command.history`	`/history`, `/namehistory`, all five list commands, and all four check commands
`blazebans.command.lookup`	`/lookup`
`blazebans.command.timeline`	`/timeline`
`blazebans.command.profile`	`/blazebans profile`
`blazebans.command.staffprofile`	`/blazebans staffprofile`
`blazebans.command.staffhistory`	`/staffhistory`

blazebans.command.history is the broadest of these. Granting it alone gives trial staff read access to everything without any ability to act.

Proof

Node	Grants
`blazebans.command.proof.view`	`/proof view`
`blazebans.command.proof.add`	`/proof add`
`blazebans.command.proof.remove`	`/proof remove`
`blazebans.proof.bypass`	Skipping a template's proof requirement

Alts and IP

Node	Grants
`blazebans.command.alts`	`/alts`
`blazebans.alts.details`	The full alt view rather than a summary
`blazebans.alts.exempt`	Not appearing in alt lookups, in either direction
`blazebans.ip`	The `--ip` flag and the IP toggle in the punish GUI
`blazebans.see.ips`	Seeing real addresses, when `privacy.show-ip-to-staff` is on

Lockdown

Node	Default	Grants
`blazebans.command.lockdown`	`op`	`/blazebans lockdown`
`blazebans.bypass.lockdown`	`op`	Joining while locked down
`blazebans.command.chatlockdown`	`op`	`/blazebans chatlockdown`
`blazebans.bypass.chatlockdown`	`op`	Talking while chat is locked

Grant the two bypass nodes to your whole staff team ahead of time. Discovering during an incident that only the owner can get in is a bad way to find out.

Modifiers

Node	Grants
`blazebans.silent`	The `--silent` and `-s` flags
`blazebans.reason.custom`	Free-text reasons. Withhold it to force template-only punishing
`blazebans.staff.notify`	Punishment broadcasts and staff alerts

Scope

Node	Grants
`blazebans.scope.global`	Issuing and revoking global punishments
`blazebans.scope.server.<id>`	Punishments scoped to that specific server

Punishing on your own server is always allowed without a scope node. See Servers and scope.

Immunity

Node	Grants
`blazebans.bypass.ban`	Cannot be banned
`blazebans.bypass.mute`	Cannot be muted
`blazebans.bypass.warn`	Cannot be warned
`blazebans.automod.bypass`	Not filtered by AutoMod
`blazebans.mute.commands.bypass`	Blocked commands still work while muted

Staff weight

blazebans.weight.<number>, where the number is 0 to 1000.

A staff member can punish someone only when their own weight is at or above the target's. The highest weight found on an account wins.

If you run LuckPerms, use staff-hierarchy.group-weights in settings.yml instead. It reads primary and inherited groups directly and is one place to maintain rather than one node per rank. See Hierarchy and exemptions.

Duration tiers

blazebans.duration.<tier>, where the tier names come from your own duration-limits.tiers configuration.

The shipped tiers are blazebans.duration.junior, blazebans.duration.moderator, and blazebans.duration.admin. Rename them, add more, or remove them. Staff holding none are unlimited. See Duration limits.

Addons

The addons ship with their own nodes.

Voice chat:

Node	Default	Grants
`blazebans.addon.voicechat.voicemute`	`op`	`/voicemute`, `/vmute`, `/gag`, `/checkvoicemute`
`blazebans.addon.voicechat.voiceunmute`	`op`	`/voiceunmute`, `/vunmute`, `/ungag`
`blazebans.addon.voicechat.notify`	`op`	Voice mute notifications
`blazebans.addon.voicechat.bypass`	`false`	Cannot be voice muted
`blazebans.addon.voicechat.reload`	`op`	Reloading the addon

Ban effects:

Node	Default	Grants
`blazebans.addon.baneffects.reload`	`op`	Reloading the addon
`blazebans.addon.baneffects.preview`	`op`	Previewing an effect

Suggested sets

Trial staff. Read only.

txt

blazebans.command.history
blazebans.command.lookup
blazebans.command.timeline
blazebans.command.profile
blazebans.command.proof.view
blazebans.staff.notify

Moderator. Punish, revoke, and investigate.

txt

blazebans.command.ban
blazebans.command.mute
blazebans.command.warn
blazebans.command.kick
blazebans.command.punish
blazebans.command.punishgui
blazebans.command.unban
blazebans.command.unmute
blazebans.command.unwarn
blazebans.command.history
blazebans.command.lookup
blazebans.command.timeline
blazebans.command.profile
blazebans.command.proof.view
blazebans.command.proof.add
blazebans.command.alts
blazebans.staff.notify
blazebans.silent
blazebans.duration.moderator
blazebans.weight.50

Senior staff. Adds IP tools, editing, and lockdown.

txt

blazebans.command.ipban
blazebans.command.ipmute
blazebans.ip
blazebans.alts.details
blazebans.command.editpunishment
blazebans.command.staffhistory
blazebans.command.staffprofile
blazebans.command.proof.remove
blazebans.command.lockdown
blazebans.command.chatlockdown
blazebans.bypass.lockdown
blazebans.bypass.chatlockdown
blazebans.duration.admin
blazebans.weight.100

Administrator. blazebans.admin, plus blazebans.command.staffrollback and blazebans.scope.global if you want those explicit rather than inherited.

Two things worth knowing

blazebans.admin bypasses more than commands. It also bypasses scope checks, staff hierarchy, and group exemptions. Someone with it can punish anyone. Keep it with owners.

Console bypasses almost everything. Permissions, hierarchy, group exemptions, and scope. The only thing console respects is exempt.players, which is why that list is the way to protect an account absolutely.