2.1 KiB
2.1 KiB
type, title, description, status
| type | title | description | status |
|---|---|---|---|
| User Story | US-005: Administer Leaf | Give administrators command-based control over global and per-player Leaf behavior. | backlog |
US-005: Administer Leaf
As a server administrator, I want to control Leaf globally and per player so that I can support players, prevent misuse, and suspend protection for server events.
Acceptance criteria
- Administrative commands require
leaf.admin, which server operators receive by default. /leaf enabled <on|off>globally enables or disables Leaf.- Global disablement immediately suppresses Leaf-managed Resistance, prefixes, and onboarding reminders without erasing player opt-in choices.
- Global enablement immediately restores protection and prefixes for eligible online opted-in players.
/leaf player <name|uuid> statusreports the player's identity, saved opt-in choice, active-protection state, lock state, and first-join time./leaf player <name|uuid> enabled <on|off>changes the player's saved opt-in choice and immediately reconciles their online effect and prefix./leaf player <name|uuid> locked <on|off>controls whether that player can change their own saved choice.- A locked player receives a clear explanation when
/leaf onor/leaf offis denied. - PvP-triggered opt-out remains authoritative even for a locked player.
- Player targets resolve online names, previously known names, and UUIDs without confusing two players who used the same name.
/leaf strength <1-5>changes the live Resistance level and immediately updates protected online players.- Administrative autocomplete is permission-aware and suggests valid subcommands, known player targets, properties, levels, and
onoroffvalues for the current argument position. - Every successful mutation reports exactly what changed, and invalid requests make no partial changes.