v3.24.1 - Discord-Bot changelog | SCNX

v3.24.1 - Discord-Bot changelog | SCNX

CustomBot v3.24.1 is the biggest update of the year:

Included in this update

Anti-Nuke Protection

New module in Early Access

New module (Early Access): Anti-Nuke Protection - a best-effort safety layer that watches for destructive server actions and responds using rules you control.

Anti-Nuke is a mitigation layer, not a backup or guarantee: it only works while the bot is online, and some Discord actions cannot be fully reversed. Enable it from the module catalog and read the setup guide and important limitations in the documentation .

New module for everyone

New module: Message Quotes - make conversations easier to follow by turning a Discord message link into a readable quote in the current channel.

Displayed attachment images are uploaded to your scnx file library when attachment archival is enabled. They count against your file-storage quota ; use the global Disable attachment archival setting to opt out. Enable Message Quotes from the module catalog .

Module previously in Early Access now available for everyone

Chess has left Early Access - it is now available to every server, on every plan. Play a complete game against another member or the bot inside a Discord thread, with a freshly drawn board after every move and a leaderboard that tracks the winners. Enable it from the module catalog and challenge someone today.

Live Messages has left Early Access - it is now available to every server, on every plan. Post messages that display live server statistics such as member counts, online members, boosts, channels and more, and let the bot keep them updated automatically. Enable it from the module catalog .

Moderation & Security

đŸšĢ Fully configurable spam detection

The anti-spam system is now split into individual detectors that you can enable, tune and act on separately - no more one-size-fits-all rules. Alongside the classic message-rate, duplicate-message, mention and mass-mention checks, you can now catch:

Each detector has its own enable toggle , threshold , timeframe and action . You can also automatically delete detected spam messages - set a global default and override it per detector; auto-delete cleans up the entire offending burst across every channel it landed in. A global auto-delete switch lets you turn message removal on or off everywhere at once. For example, mute a user on a mass-mention burst but only quietly delete an emoji flood - each detector reacts the way that kind of spam deserves.

đŸŽšī¸ Custom moderation levels

The four fixed Moderator-Level role fields are replaced with moderation levels you define yourself . Create as many named levels as you like and give each one exactly the capabilities it should have - warn, mute, kick, ban, lock, channel-mute, quarantine, clear messages, lift punishments, bypass anti-spam, report immunity, lockdown control and more. Give your Trial Mods warn and mute but hold back ban and lockdown, and hand a dedicated anti-raid role nothing but lockdown control - each role gets exactly the power its job needs, and nothing more.

Your existing Level 1-4 setup is migrated automatically and keeps working exactly as before; the old fields disappear once your levels have been carried over.

â†Šī¸ Lift punishments in one click

Moderation log messages and the mod-actions view can now show a Lift punishment button that reverses a mute, ban, quarantine or warning with a single click - you are asked for a reason, and the action is undone. This is opt-in via a new toggle and is permission-gated, so only staff allowed to perform that action type can lift it. Perfect for the moment an appeal is accepted or you realise you actioned the wrong member - undo it right there in the log.

📝 Customizable and public moderation logs

Every moderation log message type now has its own editable template with the full embed editor, so your logs can look and read exactly how you want. Drop your appeal-form link into every ban notice, or match each message to your server's own voice. On top of that, you can send a separate, differently-worded public log to a second channel per action type - keep the detailed internal log private while sharing a friendly notice with your community. Enable it for only the action types you want - a heads-up on mutes alone, or a full public ledger of every ban for a transparent, accountable server.

The anti-spam chat notification also gained richer placeholders ( detector type , count , threshold ) and per-detector message overrides.

đŸ“Ĩ Record native Discord moderation

Bans, unbans, kicks and timeouts carried out with Discord's own built-in tools can now be recorded into the bot's moderation database and log channel, so your history and stats stay complete no matter how an action was taken. Optionally, the affected user receives a DM about it. This is opt-in and applies to live actions only. A member's warning and infraction counts stay accurate even when half your team reaches for Discord's right-click Ban instead of the bot.

âąī¸ Change how long a punishment lasts

A new /moderate edit-duration command - and an Edit duration button and modal in the mod-actions view - let you shorten or extend an active temporary mute, ban or quarantine after the fact. The affected user is notified of the change by DM. Extend a temp-ban on a member who keeps evading it, or cut a mute short once they have cooled off - no need to lift and re-apply.

📸 Attach several proof images to a case

Evidence is no longer limited to a single screenshot. You can attach multiple proof images to a moderation action - up to ten - both when you act (the right-click Warn / Mute / Kick / Ban actions now take evidence too) and afterwards, via an opt-in Add proof button that now sits directly under each moderation log message (and in the mod-actions view) or the /moderate add-proof command. Images are picked in a single upload field, and the log message updates itself in place, showing everything together as a gallery.

Handy when a rule-break spans several messages, when a report includes screenshots from more than one channel, or when you simply want the full receipts on file for later appeals. Reports get evidence too: both user reports and message reports now have an optional image-upload field, on top of the reported message's own attachment.

đŸ‘Ĩ Tag involved users on a case

Sometimes a case involves more than one person. You can now link additional users to a moderation action as involved parties - the member who reported it, a second account caught up in the same incident, or a witness whose context might matter later. It is opt-in and reference-only: tagged users appear on the case for context and are never punished or notified.

Add them with the new involved option when you take an action, the /moderate involve command, or the user picker in the mod-actions view. Because the involved-users list is a normal log placeholder ( %involved% ), you decide whether these names show only in your internal log or also in a public one.

âœī¸ Correct a case's reason

Mistyped a reason, or want to clarify why an action was taken? An opt-in Edit reason button - shown under each moderation log message and in the mod-actions view - and a /moderate edit-reason command - let you rewrite a case's reason after the fact. The change is recorded as a case event for accountability, and the log message updates itself in place.

đŸˇī¸ Custom case titles

Give each case a short, custom title - for example 'Insulting several users' - separate from the (often longer) reason. It is opt-in: turn it on in the config and the title becomes a required field on the warn, mute, ban, kick, quarantine and channel-mute commands and their right-click modals.

If you are not seeing custom titles in your log messages yet, ensure you've updated the title to use the %title% parameter.

Staff Management System

YouTube-Notifications

TikTok-Notifications

📱 TikTok notifications are back

TikTok creator notifications work again. Because of TikTok's API restrictions, notifications now only work for creators who have connected their TikTok account to SCNX. Ask the creator to complete the SCNX creator-claim flow once - after that, notifications start flowing automatically, with no bot restart needed.

Automatic Publishing

Quality of life improvements

Recommended articles