docs(design): complete initial harvest stories
Release / release (push) Successful in 4m14s
CI / build (push) Successful in 53s

This commit is contained in:
dmg
2026-08-14 18:27:09 -04:00
parent e0a9413cb2
commit d35c0197f5
9 changed files with 121 additions and 99 deletions
@@ -2,7 +2,7 @@
type: User Story
title: "US-006: Administer player harvest progression"
description: Let administrators inspect, correct, and reset player crop progression safely through commands.
status: in-progress
status: done
---
# US-006: Administer player harvest progression
@@ -11,18 +11,18 @@ As a **server administrator**, I want command-based controls for crop progressio
## 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 confirm` resets 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.
- [x] Administrative commands require `spigotharvest.admin`, which server operators receive by default.
- [x] Administrative player arguments safely resolve online players and previously known offline players.
- [x] Player state remains keyed by UUID while retaining the latest known name for lookup and display.
- [x] `/harvestadmin status <player> [crop]` displays the selected player's crop levels, level-local progress, and any active operation.
- [x] `/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.
- [x] `/harvestadmin setprogress <player> <crop> <amount>` sets level-local progress and consistently evaluates any reached levels, carrying excess progress forward.
- [x] `/harvestadmin reset <player> <crop>` resets only the selected crop to Level 0 with zero progress.
- [x] `/harvestadmin reset <player> all confirm` resets all crop progression only after explicit confirmation.
- [x] A reset or level reduction cancels the player's active operation when that operation would exceed the resulting entitlement.
- [x] Every successful mutation reports exactly what changed.
- [x] Invalid requests make no partial changes and provide friendly usage guidance.
- [x] Permission-aware autocomplete offers subcommands, online and known offline players, supported crops, valid levels, and reset confirmation.
## Related