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

feat(protection): add configurable Strength effect
Release / release (push) Successful in 2m26s
Details
CI / build (push) Successful in 56s
Details

Browse Source
This commit is contained in:
dmg
2026-08-10 22:58:18 -04:00
parent e064c7398c
commit 5609a0a656
17 changed files with 279 additions and 71 deletions
Download Patch File Download Diff File Expand all files Collapse all files
design/user-stories/us-006-configure-and-persist-leaf.md
+4 -3
View File
@@ -11,15 +11,16 @@ As a **server operator**, I want Leaf settings and player state to be validated
## Acceptance criteria
- [x] Configuration supports the global enabled state, Resistance strength, leaf prefix, onboarding duration, and player-facing messages.
- [x] Configuration supports the global enabled state, Resistance and Strength levels, leaf prefix, onboarding duration, and player-facing messages.
- [x] Resistance strength defaults to level I and accepts only Minecraft Resistance levels I through V.
- [x] Runtime changes made through `/leaf enabled` and `/leaf strength` are persisted for subsequent restarts.
- [x] Strength defaults to level I and accepts only Minecraft Strength levels I through V.
- [x] Runtime changes made through `/leaf enabled` and `/leaf effect` are persisted for subsequent restarts.
- [x] UUID-keyed player state persists the latest known name, saved opt-in choice, administrative lock, and first-join timestamp.
- [x] Date-times use RFC 3339 UTC notation with a `Z` suffix.
- [x] State is saved safely so that a failed write does not replace valid persisted state with a partial document.
- [x] Invalid required configuration prevents partial plugin initialization and produces a clear server log message.
- [x] Corrupt or invalid player records are handled defensively and cannot silently grant protection or privileges.
- [x] Removing Leaf-managed Resistance does not remove a distinct Resistance effect that Leaf does not own when the API provides enough information to distinguish it.
- [x] Removing Leaf-managed Resistance or Strength does not remove a distinct corresponding effect that Leaf does not own when the API provides enough information to distinguish it.
- [x] Unknown forward-compatible configuration and player-state fields are preserved where practical.
## Related