Coming from another bot

Before you start

If you already use a security bot such as Wick, most of the ideas here will be familiar. Only the names differ. The thing to avoid is a gap with no protection, or an overlap where two bots fight each other.

Moving from Wick? The Wick bot alternative page compares the two side by side.

Settings can't be imported from another bot. You don't need them. Picking a security level sets everything sensibly in one step.

The safe order

1. 1

   Write down what you rely on

   Note your old bot's whitelist, log channel, verification channel, member role and any blocked words. Five minutes now saves guessing later.

2. 2

   Invite Bastion

   Add it to the server. Follow getting started.

3. 3

   Put Bastion's role at the top

   Above the old bot's role as well. See the setup guide.

4. 4

   Run /setup and pick a level

   /setup makes the Quarantined role and a private log channel. Then pick a level in the dashboard. Balanced is right for most servers.

5. 5

   Switch off the old bot's protection

   Turn off its anti-nuke, anti-spam and join checks in its own dashboard. Do this before the two overlap for long.

6. 6

   Copy across what you noted

   Set your log channel, trusted people, moderator roles and blocked words.

7. 7

   Move verification

   Run /verification setup in your verify channel and delete the old bot's verify message. See verification.

8. 8

   Remove the old bot

   Kick it, then delete any roles it left behind, such as its own quarantine or muted role.

9. 9

   Run /status

   Check your security score and fix anything listed.

Words you may know by another name

Things that work differently

• Settings live in the dashboard. There are no setup commands to learn beyond /setup and /verification setup. See the dashboard.
• There's one trusted list. No tiers and no per-module whitelists. A person is trusted or they aren't. Roles can't be trusted, only people.
• Automod has ignore lists for roles and channels, for anything that should skip spam checks but still be watched by anti-nuke.
• Verification never leaves Discord. No private messages, no web page and no QR code. Tell your members, as they may be used to something else.
• Quarantine is the default punishment, not a ban, so mistakes are easy to undo.
• Slash commands only. There's no prefix.

What doesn't come across

• Old warnings and cases. Bastion's case history starts at number 1.
• Members stuck in the old bot's quarantine or mute role. Release them with the old bot before you remove it, or fix their roles by hand afterwards.
• The old bot's backups. Make a fresh one with /backup create if you have Pro.

Your other bots

Bots that create or delete channels quickly, such as ticket bots, may set off anti-nuke on the first busy day. If your old security bot had them whitelisted, do the same here. The steps are in troubleshooting.