Skip to content

2.2.2

Choose a tag to compare

View all tags
@dmccoystephenson dmccoystephenson released this 25 Oct 01:48
v2.2.2
c1f0991
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

2.2.2

For a server running v2.2.1, this is a drop-in bug-fix release. Notifications, config keys and stored data work the same as before. Two things in the console change: a Discord webhook URL that could never deliver is now reported at startup, and the usage-reporting notice names the endpoint you have actually configured.

Changes

Discord notifications

  • A discord.webhook-url with no host (for example https:///api/webhooks/...) or a port outside 1–65535 is now rejected at startup. The warning names the key, and Discord is skipped. Before, such a URL passed startup and then failed on every player join with a misleading error such as "Failed to select a proxy". Hostnames containing an underscore are still accepted. (#93)

Usage reporting

  • The startup notice shown while usage reporting is on now names the server set in usage-reporting.endpoint. Before, it always named the bundled default. (#86)

Reliability

  • Notifier loading has moved into its own component, with tests covering each smtp.* key and checking that a failing channel does not stop the others when a player joins. What gets loaded, what gets logged and how notifications are sent are all unchanged. (#81, #83, #90)

Version

v2.2.1 → 2.2.2 — PATCH. Mechanical floor from comparing the two jars: PATCH.
Judgment: The only behaviour changes are fixes. #93 makes startup reject Discord webhook URLs with no host or an out-of-range port. Those URLs already failed on every join, so no working configuration is affected and the failure now just shows up earlier with a clearer message. #86 makes the startup log name the endpoint the client actually uses, and #81 is a refactor that keeps loading behaviour the same. There are no new config keys, data, commands, permissions or API 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).

Install with Dan's Plugin Manager: /dpm get <plugin>. How stable releases are made: Release channels.

drafted by Claude on behalf of Daniel Stephenson

Assets 3
Loading