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.

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.