Duration limits

In settings.yml:

duration-limits:
  tiers:
    - permission: "blazebans.duration.junior"
      max: "7d"
    - permission: "blazebans.duration.moderator"
      max: "30d"
    - permission: "blazebans.duration.admin"
      max: "permanent"

Each tier is a permission node and a maximum. Grant one node per rank.

max uses the same duration syntax as commands. permanent or 0s means no cap.

BlazeBans finds every tier whose node the staff member holds, and uses the highest maximum among them.

That means holding several nodes gives you the longest, not the shortest. An admin who inherits the junior node from a parent group still gets permanent, which is what you want from an inheriting permission system.

Staff holding none of the nodes are unlimited. That is worth stating plainly: adding a duration-limits block does not restrict anyone until you also grant the nodes.

A punishment over the limit is refused with a message naming the maximum. It is not silently shortened to the cap.

That is the right behaviour. A moderator who meant to ban for a year and quietly got seven days will not notice, and the player will be back before anyone realises.

The three shipped tiers are only defaults. Rename them, add more, or use fewer:

duration-limits:
  tiers:
    - permission: "blazebans.duration.trial"
      max: "1d"
    - permission: "blazebans.duration.helper"
      max: "3d"
    - permission: "blazebans.duration.mod"
      max: "14d"
    - permission: "blazebans.duration.srmod"
      max: "90d"
    - permission: "blazebans.duration.admin"
      max: "permanent"

Any node name works. Matching it to your rank names makes the permission setup readable later.

Bans, mutes, IP bans, and IP mutes: anything with a duration.

Warns and kicks have no duration and are unaffected.

Template durations are checked the same way. A moderator capped at 30 days cannot apply a 60-day template, and gets the same refusal.

There is no correct answer, but there is a reasonable shape: a new moderator should be able to handle the day-to-day, and escalation to a permanent ban should involve someone more senior.

The point is not the exact numbers. It is that a permanent ban should be a decision someone senior makes deliberately, rather than the default anyone can reach for.

Duration limits and staff weight answer different questions.

Weight decides who can be punished. Duration decides how long for.

Both are checked. A moderator with weight 50 and a 30-day cap can punish anyone below weight 50, for up to 30 days. Grant them together, one pair per rank, and the permission setup stays easy to reason about.

--preview shows what would happen without writing anything:

/ban Steve 60d Cheating --preview

If the duration is over your cap, the refusal comes back the same as it would on a real punishment. That is a safe way for a new moderator to find their own limit.

blazebans.admin is not checked against duration tiers, so administrators are unlimited whether or not they hold a tier node.

Console is unlimited.