Documentation

Radar is a security bot for Discord. It watches your server around the clock, stops the common ways servers get wrecked, and keeps a record of what happened so you can see it later. This page walks through adding it, setting it up, and running each part of it. If you only read one section, read First-time setup. That gets you protected in about two minutes.

1. What Radar does

Most servers get damaged in one of a few ways. A moderator's account gets stolen and starts deleting channels. A raid of fresh accounts floods in. Someone drops a link that phishes half your members. Radar covers those cases, and it keeps working when your staff are asleep.

Each part of Radar is a module you turn on when you want it:

• Anti-Nuke catches mass deletes and bans and stops the account doing them.
• Anti-Raid reacts to sudden join spikes.
• Automod filters messages: invites, links, spam, banned words.
• Verification makes new members pass a captcha before they can talk.
• Logging writes every security and moderation event to a channel you pick.
• Safeguard screens members against Roblox risk signals, for servers that need it.

Everything is off until you switch it on, so adding Radar never changes how your server behaves on its own. You decide what runs.

2. Adding Radar

Open the invite from the home page or the "Add to Discord" button, pick your server, and keep the permissions Radar asks for. It needs a fairly high role to do its job. To ban an account that is deleting channels, Radar has to sit above that account in the role list, so drag the Radar role near the top once it joins. If Radar sits below the person causing trouble, Discord will not let it act.

A few permissions matter more than the rest: Ban Members, Kick Members, Manage Roles, Manage Channels, and View Audit Log. Radar reads the audit log to work out who did what. Without it, Anti-Nuke is mostly blind.

3. First-time setup

Run /setup in your server. It walks you through the basics:

• a log channel where Radar posts what it sees and does;
• a staff role so Radar knows who your moderators are;
• which modules to turn on to start.

You can change any of it later with /config or on the dashboard. To flip a single module, use /config module:<name> state:<on/off>. To set the log channel, use /config modlog:#channel. Running /config on its own shows you the current state of everything at a glance.

Set the log channel to somewhere only staff can read. Radar posts account IDs and enforcement details there, and you do not want members watching that feed.

4. The dashboard

Sign in at the dashboard with Discord. You will see every server where you have Manage Server and Radar is present. Pick one and you can edit every module without touching a command: thresholds, the action each module takes, exemption lists, log channel, and staff role. Changes save straight away and the bot picks them up within a second or two.

The dashboard also holds your audit history. That is the searchable record of every action Radar and your staff took, with who did it, when, and why. Free servers keep a rolling window of it. Premium keeps far more. See Premium.

5. Anti-Nuke

Anti-Nuke is the module that saves you when a trusted account turns hostile. It counts destructive actions per account over a short window: channel deletes, role deletes, bans, kicks, mass role changes. When an account crosses the limit you set, Radar acts on it right away, before the damage spreads.

You choose what "acting on it" means. The usual options are:

Add your genuine admins and other trusted bots to the exemption list so a real cleanup does not trip the alarm. Keep that list short. Every account on it is an account Radar will not stop.

6. Anti-Raid

A raid is a burst of accounts joining at once, usually to spam or to overwhelm your mods. Anti-Raid watches your join rate. When too many accounts join inside a short window, it switches the server into a defensive mode you configure. It can hold new joiners for verification, kick accounts below a minimum age, or block accounts flagged as bots.

Account age is the single most useful setting here. Raids run on throwaway accounts made minutes earlier, so a minimum age of a few days stops most of them and rarely bothers a real member. Tune the join threshold to your normal traffic. A server that gets ten joins a minute needs a higher trigger than one that gets ten a week.

7. Automod

Automod reads messages as they arrive and applies the filters you turn on. Radar does not store message contents. It checks the message, acts if it needs to, and moves on.

• Invites stops other servers' invite links.
• Links catches URLs, with an emphasis on known phishing and scam domains.
• Spam catches fast repeated messages and copy-paste floods.
• Words matches a banned-word list you set.

Each filter has its own action: delete the message, warn the member, time them out, or kick. Start with delete and a warning. You can always tighten it once you see what your server actually gets. Add your announcement and partner channels to the exemptions so your own invite links survive.

8. Verification

Verification puts a gate in front of your server. A new member joins, gets a limited view, and has to pass a captcha to unlock the rest. Bots and scripted raid accounts almost never get through, and a real person clears it in a few seconds.

Set it up with a verified role that has your normal member permissions, and lock your real channels behind that role. Unverified members land in a small holding area with just the captcha. Pair this with Anti-Raid and a raid mostly stops at the door.

9. Logging

Logging is the module you will be glad you turned on the day something goes wrong. It posts structured events to your log channel: bans, kicks, timeouts, role changes, channel edits, and every automatic action Radar takes. Each entry says who did it, to whom, and why.

The same events land in your dashboard audit history, where you can search and scroll back through them. The channel is for watching things live. The dashboard is for going back and working out what happened.

10. Safeguard

Safeguard is an optional module for communities with younger members. When you turn it on, it tries to resolve a member's linked Roblox account, checks public signals like group memberships against known risk indicators, and gives the account a risk score. You decide what happens next.

You can have Safeguard act on a high score on its own, or have it only flag the member and leave the call to your staff. A risk score is a signal, not a verdict. It works from public data that can be wrong or out of date, so review-only is the safer setting for most servers. You are responsible for how you handle a flag and for giving members a fair way to appeal.

11. Moderation commands

Radar carries a full set of moderation tools so you do not need a second bot for the basics:

Every one of these commands respects your staff role and Discord's own permissions, and every one writes to your log. If a moderator bans someone, you will see who did it.

12. Roles and members

These tools handle the day-to-day churn of members and roles:

• Auto-roles hand a role to every member as they join, so newcomers land with the right access.
• Antialt looks for alt accounts by account age and other signals and can block or flag them. Set the minimum age to match how strict you want to be.
• Mass-role adds or removes a role across everyone who already has another role, which saves you clicking through hundreds of members by hand.

Auto-roles and antialt are premium features. See below.

13. Premium

Free covers the core: Anti-Nuke, Anti-Raid, Automod, Verification, the dashboard, and a rolling week of audit history. That is enough to keep most servers safe.

Premium adds the deeper controls and longer memory:

• per-module custom actions and finer thresholds;
• alt-account detection and auto-roles;
• mass-role operations;
• a much longer audit window;
• priority when you need help.

While your subscription is active you can turn Premium on in as many servers as you run. There is no slot limit. Billing goes through Stripe, your card never touches our servers, and you can cancel any time and keep Premium until the period you paid for ends. See the Premium page for current pricing.

14. Network blacklist

Radar keeps a network-wide blacklist of accounts that have attacked servers or shown a serious cross-community threat. A blacklisted account can be blocked from using Radar in any server that runs it. Radar's founders control this list. No command, dashboard page, or server manager can add to it or read it, which is the point: it only works if a bad actor cannot see or edit it. If you think your account was blacklisted by mistake, contact us and ask for a review.

15. Staff and permissions

Radar reads two things to decide who may run a command: your Discord permissions and the staff role you set in /setup. A moderator needs the matching Discord permission for the action, so someone without Ban Members cannot ban through Radar even if they can see the command.

On the dashboard, access follows Manage Server. Anyone with Manage Server on a server can configure Radar there. The separate network admin panel is for platform staff and uses its own role system, which does not affect your server.

16. Troubleshooting

17. Getting help

If something here did not answer your question, join the support server and ask. Premium servers get answered first. Found a bug or a security issue? Tell us in the support server or by email, and please do not post a live exploit in public.