Skip to content
Docs menu: Ping flood lockdown

Protection

Ping flood lockdown

In short

If members send 50 pings within 5 seconds, Bastion locks every channel and tells your staff. Ten minutes later it unlocks them again. It's free and off until you switch it on.

What it does

A ping flood is several accounts pinging people as fast as they can. Automod times each one out, but ten accounts can still land a lot of pings before the last one is stopped.

Ping flood lockdown watches the whole server, not one person. When the pings add up, it locks every channel so no more can be sent.

Turn it on

  1. Open Automod in the dashboard

    Automod itself must be switched on.

  2. Open Advanced settings

    Find the group called Ping flood lockdown.

  3. Switch on Lock the server on a ping flood

    The three numbers appear underneath.

  4. Press Save

    The defaults suit most servers. Leave them unless you have a reason.

Settings

SettingWhat it doesDefault
Lock the server on a ping floodSwitches it on or off.Off
This many pingsHow many pings set it off. 5 to 500.50
WithinHow close together they must be. 1 to 120 seconds.5 seconds
Unlock again afterHow long the lock lasts. 0 to 240 minutes. 0 keeps it locked until someone runs /lockdown end.10 minutes

How pings are counted

  • Each person or role pinged in a message counts as one ping.
  • A ping of @everyone or @here counts as one more.
  • Pings from every ordinary member are added together, across every channel.
  • Staff aren't counted. That means the owner, trusted people, anyone with Manage Messages or Administrator, and your moderator roles.
  • Roles and channels Automod ignores aren't counted.
  • Roles you've allowed to ping lots of people, or to ping @everyone, aren't counted for those pings. See Exceptions for one thing on the Automod page.
  • Bots and webhooks aren't counted.

For example, 10 accounts each send one message that pings 5 people. That's 50 pings. If it happens inside 5 seconds, the server locks.

What happens

  1. Every channel locks

    It's the same lock as /lockdown start. Nobody can send messages in any channel Bastion can edit. See lockdown.

  2. Your staff are told

    An alert called Ping flood: server locked goes to your log channel. It pings your alert roles, if you chose any. A case is saved.

  3. The flooders are dealt with

    Automod still times out each account that overheated. The lock gives it time to finish.

  4. The channels unlock

    After 10 minutes Bastion puts every channel back the way it was and posts Lockdown ended. It checks twice a minute, so the unlock can be a few seconds late.

To unlock sooner, run /lockdown end. The unlock time is saved, so a restart of the bot doesn't leave your server locked.

Things to know

  • If the server is already locked, nothing changes and no second alert is posted.
  • If someone runs /lockdown start while a ping flood lock is on, the lock becomes theirs. It no longer unlocks by itself.
  • If panic mode starts during a ping flood lock, the panic decides when the channels unlock.
  • Only the channels are unlocked automatically. Single channel locks, the join lock and staff power lockdown are left as they are.
  • Bastion needs Manage Channels and Manage Roles to lock a channel. If it can't lock any, the alert says so.
  • A long flood is reported once a minute at most.

TipPick an alert role on the Logs page. Without one, the lock happens but nobody gets a notification. See logs.

My server locked itself.

Check your log channel. If the alert says Ping flood, wait for it to unlock or run /lockdown end. If it says panic mode, see panic mode.

It locked during an event with lots of pings.

Raise This many pings, or give your event hosts a role under Roles that can ping lots of people on the Automod page.

Is this Pro?

No. It's free.

Does it work if the Pinging lots of people filter is off?

Yes. It counts pings on its own. Automod as a whole must be on.

Who can change it?

Anyone who can open the dashboard, the same as the rest of the Automod page.

Last updated