Creative Logger

Critical fix — bot presence could take a server down

If you run 1.3.0 with `bot.presence.enabled: true`, please update. Not using bot presence? You are unaffected, and nothing else in the plugin changed. The gateway connection that makes the bot appear online leaked an HTTP client every time it reconnected, and nothing stopped several connections existing at once — so one dropped connection could snowball into more. On the server that reported this, that reached ~77,000 Discord connections in 12 hours and 5,014 leaked threads, until the JVM could no longer create a thread: the server's main thread died while the process stayed up with its ports open, so it still answered pings and looked perfectly healthy, but nobody could join and even stop no longer worked. Discord separately reset that bot's token for connecting too often — which 1.3.0 then reported as "your token is invalid", sending the admin to look in the wrong place. What changed: - One HTTP client, reused and properly shut down. Reconnecting now costs nothing. - One connection attempt at a time. A superseded connection is closed instead of left running. - Real backoff — 15 seconds doubling up to 15 minutes, and only cleared once a connection has been healthy for 10 minutes, so a flapping connection backs off like any other failure. - Presence switches itself off instead of retrying forever: after 10 failures in a row, or more than 20 attempts in an hour, it stops with one clear console line telling you logging is unaffected and that /creativelog reload will try again. It is only the online indicator — it must never cost you a server. - Close codes are read properly. A rejected token stops immediately, and the message now allows for a token Discord has reset rather than one you mistyped. Rate limiting waits it out. A connection that stops answering heartbeats is recognised as dead instead of sitting there looking online. - /creativelog status and the setup menu's Discord Bot item now show what presence is actually doing — connected, reconnecting in 60s, or stopped and why — instead of only whether the option is ticked. Can't update right away? Set bot.presence.enabled: false and restart. Webhook logging and bot-channel sending are unaffected; presence is purely the online indicator. If Discord reset your bot token, generate a new one in the Discord developer portal and paste it in — no plugin version can restore the old one.

Notes

No config changes: updating is just swapping the JAR, and your existing config.yml is untouched. Verified on Paper 1.21.11, 26.1.2 and 26.2 — full test suite green, including a new suite that drives a local stand-in gateway to prove the reconnect behaviour, and a 71-minute soak confirming presence stops itself with no thread growth.