32 lines
2.1 KiB
Markdown
32 lines
2.1 KiB
Markdown
---
|
|
type: User Story
|
|
title: "US-010: Administer player progression"
|
|
description: Let administrators inspect and safely modify player progression and live progression settings through commands.
|
|
status: done
|
|
---
|
|
|
|
# US-010: Administer player progression
|
|
|
|
As a **server administrator**, I want command-based progression controls so that I can inspect players, correct state, and tune requirements without an inventory UI.
|
|
|
|
## Acceptance criteria
|
|
|
|
- [x] Administrative commands require `spigotbase.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] `/baseadmin progress <player>` displays the player's base, counters, earned path levels, active cooldowns, toggles, and visitor settings.
|
|
- [x] `/baseadmin setlevel <player> <path> <level>` sets an earned path level while enforcing or explicitly granting required preceding levels.
|
|
- [x] `/baseadmin setprogress <player> <path> <amount>` updates the selected counter and consistently evaluates reached tiers.
|
|
- [x] `/baseadmin reset <player> <path>` resets a selected path without silently leaving benefits that require it.
|
|
- [x] `/baseadmin reset <player> all` removes the player's base, progression, active cooldowns, and plugin preferences after confirmation.
|
|
- [x] Administrators can clear personal and visitor cooldowns independently.
|
|
- [x] Administrative commands can update configured block requirements, warm-ups, and cooldowns for each level using validated values.
|
|
- [x] Runtime configuration changes are persisted for subsequent restarts.
|
|
- [x] Lowered progression requirements are evaluated for a player on their next relevant action rather than immediately updating every stored player.
|
|
- [x] Every successful mutation reports exactly what changed, and invalid requests make no partial changes.
|
|
|
|
## Related
|
|
|
|
- [US-009: View progression and unlock notifications](us-009-view-progression-and-notifications.md)
|
|
- [US-011: Configure and persist progression](us-011-configure-and-persist-progression.md)
|