Docs / Guides / Stop raids, spam and scams

Stop raids, spam and scams

In short

You will have Sentinel running with spam and scam filters tested then switched on, raid protection tuned, anti-nuke checked and a test case in your history.

Before you start, give the bot Manage Channels and Manage Roles. Only dashboard managers of the server can run setup.

1. Turn on Sentinel

On your server's Services page, turn on the Sentinel Moderation switch.

What turning it on does
  • While it is off, every moderation command answers "The Sentinel Moderation service is switched off in this server." and the automod does nothing. If you have Manage Server, a button under that answer switches it on.
  • The first time a server turns it on, Sentinel also switches on anti-nuke (with quarantine, restore and the hold), escalating timeouts and a message log. The message log keeps deleted and edited messages for 30 days.

2. Run setup

Open Sentinel and click Run setup on Home. Give the bot any permission that shows a cross, then wait for the Readiness check to say "Ready to run setup."

What the check looks for and how setup reports back
  • The check looks for "The bot is in this server", "It can create the log channels (Manage Channels)" and "It can create the Quarantined role (Manage Roles)".
  • Under What happened, every step shows Done, Skipped or Failed with its reason. An error is almost always a missing bot permission.
  • See Set it up for everything setup creates.

3. Choose how strict

On the Setup page, pick Relaxed, Standard or Strict. Leave Act right away off, then click Run setup and confirm.

What the levels and Act right away do
  • Relaxed: spam and known scam links.
  • Standard: balanced protection for most communities.
  • Strict: for servers that get raided or targeted.

With Act right away off, the new filters start in Testing. The bot notes in the mod log what each filter would have done, without touching anyone. How strict on Home can change the level later.

4. Add your moderators

Open Settings and check Moderator roles in the Your team card. If setup found no moderator roles, add them here. Check the Mod log channel on this page too.

Without moderator roles

Until you add moderator roles, only Administrators can run the staff commands.

5. Switch spam and scam filters on

Open Spam & scams. Read the Testing notes in the mod log for a while, then switch Spam & scams from Testing to On.

How the filters and testing work
  • The choice has three settings: Off, Testing and On.
  • Filters shows a card for each filter with its own switch. A filter opens in a side panel with its checks, actions, channels, skipped roles and a Try it box that tests a sample message.
  • Switching to On ends every filter's own test. To keep one filter testing, open it after the switch and turn on Test this filter on its own.
  • More filters adds a ready-made pack in one click.

6. Tune raid protection

Open the Raids page and check that Raid protection is on. In How it works, set how many accounts must join within a minute to start raid mode. Then set how many minutes it lasts and what happens to new accounts during a raid.

Defaults, raid levels and starting one by hand

Raid protection is on by default. Raid mode starts itself at 10 joins a minute by default and ends after 30 minutes by default. With 0 minutes it stays on until someone ends it.

The levels:

  • Soft: a 10 second slowmode.
  • Hard: a 30 second slowmode and every new join quarantined, kicked or banned, with a DM to every admin.
  • Lockdown: @everyone cannot post in text channels except Sentinel's log channels, verification is at its highest and new joins are kicked.

Delete the invite a raid came through removes the invite that brought a group of look-alike accounts. Your vanity link is never touched.

The page's Right now buttons start or end Soft, Hard or Lockdown by hand. So do /raidmode and Lock down on Home. See /raidmode and /lockdown.

7. Check anti-nuke

On the Anti-nuke page, open Advanced. Under Never sets it off, add the accounts and roles you trust completely.

What anti-nuke watches and who can change it

Anti-nuke watches for a hijacked staff account. It looks for one account that:

  • creates or deletes channels or roles in bulk
  • bans or kicks in bulk
  • creates, changes or deletes webhooks
  • adds a bot
  • hands out dangerous permissions
  • changes the server name, vanity link or owner

By default, mass damage gets the account quarantined and Sentinel puts back what it can. A single risky change, such as one bot added or one dangerous permission handed out, is put back and alerted. The account keeps its roles.

Moderator roles are deliberately not exempt, because a hijacked moderator account is the case it exists for. Only an owner or an extra owner can change these settings. A manager can switch anti-nuke on but never off.

8. Optional: Make new members verify

Turn on the Welcome switch on the Services page first. Then, on Welcome's Verification page, press Check what changes in the Set it up for me card. Read the list and press Set it up.

What setup makes and the raid switches
  • Members already in the server keep their access.
  • Setup makes an Unverified role and a #verify channel that only Unverified members, staff roles and the bot can see. It also makes a Verified role when none is picked.
  • It hides the other channels it can change from Unverified members, turns verification on and posts the verification message.
  • Undo setup deletes only what setup made and puts back the permissions it changed on your own role.
  • While verification is on, the card is replaced by One-click setup at the top of the page.

The raid switches are in the During a Sentinel raid card on the same page. The Raids page links there under Welcome during a raid.

  • Hold greetings during a raid is on by default.
  • Everyone verifies during a raid is off by default. It makes every new member pass the gate while raid mode is on. It needs verification on with a channel and a verified role.

See Welcome setup.

9. Check that it works

Run /warn on a test account with a reason, then /history on the same account. Open History on the dashboard.

What you should see
  • The reply "Warning issued to @member. Case #N", where N is the server's next case number. Filters in Testing take case numbers too, so it is not always 1.
  • A warn DM to the test account and a "Warning Issued" card in #sentinel-logs.
  • /history shows the case and the warning count. History lists the case under Cases.
  • Home shows your shields with Lock down at the top.

Next

Was this page helpful?
YourBot docs Reference tables are generated from the code that is running. Ask in Discord