When a server gets raided or brigaded, the attacking accounts have one thing in common far more often than not: they were created minutes or hours ago. Ban-evasion alts are the same story — a fresh account made to get back in. An account-age filter turns that shared trait into a simple, effective gate.
Age as a signal
Discord shows every account's creation date, and CloudMod reads it the moment someone joins. If the account is younger than the number of days you set, it gets handled according to your rule. Older accounts — which is almost everyone legitimate — pass straight through and never notice the filter exists.
Choose how strict to be
You decide both the threshold and the response. Set the minimum age (say, 7 days) and pick what happens to accounts under it:
- Timeout — let them in but muted for a cooling-off window.
- Kick — turn them away; they can rejoin once the account ages past the line.
- Ban — hardest stance, for servers under active attack.
- Review role — assign a restricted role and hold them for manual approval, so a human makes the final call.
Bots are always exempt
Legitimate bots you invite are skipped automatically, so the filter never blocks an integration you added on purpose. It only ever looks at joining users.
Turn it up during a raid, down when it's calm
The review-role option is a good everyday default — nobody gets auto-punished, borderline accounts just wait for a moderator. If you come under active attack, raise the threshold and switch to kick or ban for the duration, then ease it back once things settle.
One layer of several
Account age catches new accounts; Scam Guard catches compromised old ones that start mass-pinging; the honeypot catches auto-posting bots; the word filter catches bad text. Layered together they cover far more than any single rule — and with network-wide bans, one decision protects every server you run.
Getting-started tip
Start with a modest threshold (3–7 days) and the review role action so you can see who it's catching without turning anyone away by mistake. Tighten it only if your review queue shows real abuse slipping through. Give the bot Ban Members, Kick Members, Moderate Members and Manage Roles so every action is available.