Repository navigation
3.5.2
3.5.2
This release changes no plugin behaviour for a server running v3.5.1. It corrects the bundled config.yml comments on usage reporting, including one that wrongly implied a key with no value turns reporting off. Existing config.yml files keep their old comments unless you update them yourself.
Changes
Usage reporting
- The
config.ymlcomments now state that command events include the command's name (#178). - The
config.ymlcomments now distinguish the ways a key can be empty:key: ''turns reporting off, while deleting the key or leaving it with no value falls back to the bundled key and leaves reporting on (#178).
Upgrade notes
If you tried to turn reporting off by deleting usage-reporting.key or leaving it with no value, reporting is still on. To turn it off, set key: '' or use the reporting switch in the same usage-reporting section.
Version
v3.5.1 → 3.5.2 — PATCH. Mechanical floor from comparing the two jars: PATCH.
Judgment: Session: Ledger. The only shipped change is to comments in the bundled config.yml, which now describe existing behaviour more accurately; the new tests pin that behaviour and the version change is routine. No command, permission, config key meaning, storage format or API behaviour changes, so the patch floor stands.
- no interface or storage difference observed between the jars
Verification
Verified on a real Spigot server before publication; this release carries the exact jar that was verified.
- boot gate run: booted twice on a fresh Spigot server running Minecraft 1.19.4 (11 assertions passed).
- boot gate run: booted twice on a fresh Spigot server running Minecraft 1.21.11 (11 assertions passed).
- boot gate run: booted twice on a fresh Spigot server running Minecraft 26.2 (11 assertions passed).
- boot gate run: booted twice on a fresh Spigot server running Minecraft 26.3 (11 assertions passed).
- save-compatibility gate run: data written by
v3.5.1was loaded by this release across 5 restart cycles with nothing lost (32 assertions passed).
Install with Dan's Plugin Manager: /dpm get <plugin>. How stable releases are made: Release channels.
drafted by Claude on behalf of Daniel Stephenson