docs(design): define spawn plugin user stories

2026-08-08 13:03:11 -04:00
commit a01f36db86
11 changed files with 291 additions and 0 deletions
@@ -0,0 +1,31 @@
+---
+type: User Story
+title: "US-006: Configure plugin behavior"
+description: Let operators tune cooldown tiers and run the plugin with clear validation, messages, permissions, and durable state.
+status: backlog
+---
+
+# US-006: Configure plugin behavior
+
+As a **server operator**, I want safe configuration and durable state so that Trigger Spawn behaves predictably across worlds and restarts.
+
+## Acceptance criteria
+
+- [ ] The one-kill cooldown is independently configurable and defaults to 28,800 seconds.
+- [ ] The two-kill cooldown is independently configurable and defaults to 14,400 seconds.
+- [ ] The three-kill cooldown is independently configurable and defaults to 3,600 seconds.
+- [ ] Configured cooldowns must be positive and representable safely by the plugin.
+- [ ] Invalid required configuration prevents partial initialization and produces a clear server log message.
+- [ ] Player-facing messages use clear built-in wording, readable colors, and friendly duration formatting.
+- [ ] Ordinary players do not require a plugin permission node to execute `/spawn`; eligibility is controlled by progression, grants, cooldowns, and bans.
+- [ ] Administrative commands require `triggerspawn.admin`.
+- [ ] Server operators receive `triggerspawn.admin` by default.
+- [ ] Boss progress, grants, bans, cooldown timestamps, latest known names, and per-world spawn settings persist across clean restarts.
+- [ ] Persisted data is handled defensively so corrupt or invalid records do not silently grant access.
+
+## Related
+
+- [US-001: Earn progressive spawn access](us-001-earn-progressive-spawn-access.md)
+- [US-003: Configure each world's spawn area](us-003-configure-world-spawn-area.md)
+- [US-004: Grant and remove spawn access](us-004-manage-spawn-access.md)
+- [US-005: Ban and unban spawn access](us-005-manage-spawn-bans.md)