ChatCop Spring 2026: Smarter Logs, Per-Provider Controls & AntiScam Fixes
If you caught our March update, you already know ChatCop got a ground-up rewrite — AntiScam, free auto-timeout, per-user log threads, and cleaner /config modals. Since then we’ve shipped a steady stream of fixes and quality-of-life improvements through April and May. Here’s everything that’s landed.
Clearer moderation logs
Usernames in log headers. Log messages now show the author’s Discord username alongside their ID and mention, so moderators can identify repeat offenders at a glance without cross-referencing IDs.
Per-provider mod role pings. You can now assign different mod roles for AImod and AntiScam in /config aimod edit and /config antiscam edit. When a message is flagged, only the relevant role gets pinged — no more waking up your entire mod team for a text toxicity warn when it was an image scam.
Ban button on log messages. Timeout, kick, and delete were already one click away. Ban joins the row (Boost servers can toggle it in /config boost). If the member has already left the server, the button greys out instead of showing a confusing error.
Logs that stay in the right place. On busy servers, when the same user triggered several flags in a row, ChatCop could sometimes update the wrong log message in their thread — leaving moderators looking at outdated info. Logs now stay tied to the correct message as new detections come in.
Per-provider auto-timeout
Auto-timeout is no longer all-or-nothing. In /config aimod edit and /config antiscam edit, you can turn auto-timeout on or off separately for AImod and AntiScam. Want image scams handled automatically but prefer a human eye on text warnings? You can set that up now.
We also fixed two issues moderators may have noticed:
- The same user could be auto-timed out more than once in quick succession when they kept posting flagged content.
- After a moderator used a timeout button on a log, the duration shown in the log could be wrong - especially if the member was already timed out before ChatCop acted.
AntiScam improvements
Scams with @everyone or @here. Some image scams that also mass-pinged the server were slipping past AntiScam entirely. Those messages are now caught like any other scam image.
Scams with several images. A message could include multiple scam images that each looked borderline on their own, so ChatCop only warned instead of deleting. It now treats that pattern more seriously and removes the message when appropriate.
Very large images. Huge image attachments sometimes failed to scan at all. AntiScam handles large uploads more reliably now.
Better accuracy over time. We’ve improved how reported mistakes feed back into detection, so false positive and false negative reports from your team should lead to fewer repeats of the same slip-ups.
Report scams we missed
Report False Negative - right-click any message -> Apps -> Report False Negative. Use it when AntiScam should have caught an image scam but didn’t. You’ll confirm in a short modal (same privacy notice as always).
Works on warnings too. If AntiScam only flagged a message as suspicious instead of deleting it, you can still report it as a miss, useful for scams that looked borderline but were real.
Report False Positive (from March). The button on log messages still lets you flag when AntiScam got it wrong. Reporting is smoother and helps us tune detection for your server.
Reliability & languages
Moderation actions that failed without a clear reason. Timeout, kick, or ban buttons could fail or behave oddly in edge cases. For example, when someone’s account was deleted, when the bot couldn’t reach them, or when role order blocked the action. Buttons now fail gracefully with a clear message, or disable when there’s nothing left to do.
Logs channel and threads. If ChatCop couldn’t create threads in your logs channel (missing permissions), moderation could look broken: no per-user threads, or errors piling up in the background. The bot now handles that situation cleanly, and auto-timeout turns itself off if your setup isn’t workable, so you’re not left thinking it’s active when it isn’t.
Interface in six more languages. The full ChatCop UI is now available in Spanish (Spain and Latin America), French, German, Portuguese (Brazil), and Chinese (Simplified). Buttons and menus that used to look cut off or misaligned in those languages now display properly.
What’s next
We’re expanding /debug with more checks so permission problems (like missing ban or thread rights in your logs channel) show up before they affect moderation.
All of the above is live on ChatCop now. If you’re already using the bot, open /config aimod edit and /config antiscam edit to try per-provider mod roles and auto-timeout.
New here? Start with our March 2026 guide, then add ChatCop to your server and run /debug.
Questions or feedback? Join our Discord community: your reports help AntiScam get better for everyone.