2.0 KiB
2.0 KiB
type, title, description, status
| type | title | description | status |
|---|---|---|---|
| User Story | US-006: Administer player harvest progression | Let administrators inspect, correct, and reset player crop progression safely through commands. | done |
US-006: Administer player harvest progression
As a server administrator, I want command-based controls for crop progression so that I can inspect players and correct their state safely.
Acceptance criteria
- Administrative commands require
spigotharvest.admin, which server operators receive by default. - Administrative player arguments safely resolve online players and previously known offline players.
- Player state remains keyed by UUID while retaining the latest known name for lookup and display.
/harvestadmin status <player> [crop]displays the selected player's crop levels, level-local progress, and any active operation./harvestadmin setlevel <player> <crop> <0|I|II|III|IV|V|VI|VII|VIII|IX|X>sets that crop's level and resets its level-local progress./harvestadmin setprogress <player> <crop> <amount>sets level-local progress and consistently evaluates any reached levels, carrying excess progress forward./harvestadmin reset <player> <crop>resets only the selected crop to Level 0 with zero progress./harvestadmin reset <player> all confirmresets all crop progression only after explicit confirmation.- A reset or level reduction cancels the player's active operation when that operation would exceed the resulting entitlement.
- Every successful mutation reports exactly what changed.
- Invalid requests make no partial changes and provide friendly usage guidance.
- Permission-aware autocomplete offers subcommands, online and known offline players, supported crops, valid levels, and reset confirmation.