31 lines
1.7 KiB
Markdown
31 lines
1.7 KiB
Markdown
---
|
|
type: User Story
|
|
title: "US-005: Administer player progression"
|
|
description: Let authorized administrators inspect and modify online or offline player progression.
|
|
status: backlog
|
|
---
|
|
|
|
# US-005: Administer player progression
|
|
|
|
As a **server administrator**, I want to inspect and modify player progress so that I can support players and correct mistakes.
|
|
|
|
## Acceptance criteria
|
|
|
|
- [ ] `/creeperaura progress <player>` reports another player's kills, rank, next threshold, and remaining kills.
|
|
- [ ] `/creeperaura set <player> <kills>` sets a non-negative lifetime kill total and reconciles the player's rank to that explicit administrative value.
|
|
- [ ] `/creeperaura add <player> <kills>` adjusts a player's kill total without allowing a negative result.
|
|
- [ ] Inspection and modification work for known offline players as well as online players.
|
|
- [ ] Players are resolved to stored UUIDs so name changes do not create duplicate progression records.
|
|
- [ ] Administrative changes are persisted immediately.
|
|
- [ ] An online affected player's boss bar and rank state are updated after a change.
|
|
- [ ] Administrative commands require distinct, documented permissions suitable for inspection and modification.
|
|
- [ ] Unauthorized use does not disclose another player's progression.
|
|
- [ ] Invalid player names, ambiguous identities, invalid numbers, and storage failures produce clear responses without partial changes.
|
|
- [ ] Successful administrative changes are written to the server log with the actor, target, old value, and new value.
|
|
|
|
## Related
|
|
|
|
- [Check personal progress](us-004-check-personal-progress.md)
|
|
- [Configure aura progression](us-006-configure-aura-progression.md)
|
|
- [User-story catalog](index.md)
|