/leaf on
/leaf off
/leaf status
/leaf enabled <on|off>
/leaf effect <resistance|strength> <1-5>
/leaf strength <1-5>  # Deprecated Resistance alias
/leaf player <name|uuid> status
/leaf player <name|uuid> enabled <on|off>
/leaf player <name|uuid> locked <on|off>

Administrative commands require leaf.admin, granted to server operators by default.

Compatibility

Leaf prefixes the standard Spigot display name (used by standard chat), player-list name, and a dedicated leaf_protected main-scoreboard team for overhead names. Legacy & color codes are supported. Leaf does not move players out of an existing scoreboard team, and per-viewer/custom scoreboards may not show its overhead prefix. Chat or tab-management plugins may replace Leaf's decorated names. During cleanup, Leaf removes exact copies of its configured prefix while preserving surrounding name formatting; another plugin should therefore not intentionally use identical prefix text.

Spigot identifies potion effects by type but does not expose their owning plugin. Leaf tracks the exact infinite, quiet Resistance and Strength effects it successfully installed and removes them only while each visible effect still matches. A distinct level, duration, or presentation is preserved. Spigot cannot distinguish an externally supplied effect with an identical fingerprint; Leaf therefore does not claim or later remove an identical effect that was already active when reconciliation ran.

Releases

Gitea Actions checks pushes and pull requests and stores a development JAR. Pull requests validate conventional commits. Main-branch conventional commits drive semantic releases after the repository defines a RELEASE_TOKEN with contents-write permission.