dmg/spigot-creeper-fear
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

feat(progress): track persistent creeper kills

Browse Source
This commit is contained in:
dmg
2026-08-08 14:07:35 -04:00
parent f9ad2d9461
commit 0bde7a6ae2
30 changed files with 1142 additions and 38 deletions
Download Patch File Download Diff File Expand all files Collapse all files
design/user-stories/us-006-configure-aura-progression.md
+7 -7
View File
@@ -1,7 +1,7 @@
---
type: User Story
title: "US-006: Configure aura progression"
description: Let administrators safely configure and persist aura thresholds, multipliers, and feedback.
description: Let administrators safely configure and persist per-rank requirements, multipliers, and feedback.
status: backlog
---
@@ -11,17 +11,17 @@ As a **server administrator**, I want to configure progression and aura behavior
## Acceptance criteria
- [ ] Configuration provides documented defaults for all six cumulative kill thresholds and damage multipliers.
- [ ] Rank thresholds are non-negative and strictly increasing.
- [ ] Configuration provides documented defaults for the six per-rank kill requirements and six unlocked-rank damage multipliers.
- [ ] Rank requirements are positive integers.
- [ ] Damage multipliers are finite and non-negative.
- [ ] Progress boss-bar duration and player-facing rank messages are configurable.
- [ ] `/creeperaura threshold <rank> <kills>` validates, applies, and persists a threshold change.
- [ ] `/creeperaura threshold <rank> <points>` validates, applies, and persists the points required to unlock that rank.
- [ ] `/creeperaura reload` safely loads externally edited configuration without requiring a server restart.
- [ ] Threshold-management and reload commands require documented administrative permissions.
- [ ] Invalid configuration is rejected with actionable diagnostics while the last valid configuration remains active.
- [ ] Changing thresholds never automatically removes an already unlocked rank or grants a new rank immediately.
- [ ] After a threshold change, the player's next qualifying kill evaluates newly satisfied progression and can grant the next eligible rank immediately.
- [ ] Existing progress within the player's retained rank is displayed against the updated next threshold.
- [ ] Changing requirements never automatically removes an unlocked rank, grants a new rank, or discards current-tier progress.
- [ ] After a requirement change, the player's next qualifying kill can grant at most the next rank when its requirement is satisfied.
- [ ] Rank advancement resets current-tier progress to zero rather than carrying excess progress forward.
- [ ] Configuration-command changes survive plugin and server restarts.
## Related