Release Note

v2.19.0

16 April 2026

New Improvements Fixes

New

  • New /invite command lets anyone add CleanerBot to another server (opens Discord's native add dialog directly), join the support community, or visit the website - all from one convenient card.
  • New /ping command shows a live status panel with aggregate status, component health, uptime, latency, guild count, and user count - the same view as the CleanerBot status channel.
  • New /config share command lets admins generate a share-safe CleanerBot setup summary with AHS settings and public link, preview it privately, post it in-channel, and copy it via attached Markdown export.

Improvements

  • Bulk upload guidance now reflects current behavior: CSV is the recommended path for large imports, strict single-input mode is enforced (ids or file, not both), manual ids input is capped at 250 unique IDs, and Stop Upload handling is clearly documented.
  • Risk-review notices after threshold and decay-related config changes now explain impact more clearly, including that the change is saved and should be reviewed before high-impact automation is enabled or confirmed.
  • Member-targeted announcement cards now include a plain-text affected-member list in code formatting, so members can still identify users when Discord mentions render inconsistently.
  • Manual kick review confirmations now use clearer action wording and disable action buttons immediately after click, so admins get instant feedback while larger kick batches are processing.
  • When CleanerBot leaves a server due to incomplete setup, the goodbye notice is now sent directly to the configured admin as a DM and includes a one-click re-invite button to easily bring the bot back.
  • Server connections to Discord are now redundant. If one connection drops, only a small fraction of servers is temporarily affected instead of all at once.
  • Internal maintenance tasks now run separately from command handling, so the bot stays fully responsive even during background operations.
  • Server data is now stored across independent, isolated infrastructure segments. An issue or maintenance window in one segment no longer affects other servers, and new servers are assigned automatically.

Fixes

  • Fixed a crash in /score_settings that prevented the channel selection picker from loading correctly.
  • Voting on any connected botlist now correctly grants the supporter role and records the vote credit; previously only top.gg votes triggered the supporter flow.
  • /set_decay_score now accepts the full 0-180 range, so manual corrections can match the same inactivity threshold ceiling used across setup and config.