Test mode, raid reports, the staff PIN and a recovery key
Try Bastion's judgement before it acts, see exactly who came in during a raid, and keep control if a staff account or the owner's account is lost.
Added
- Test mode for Anti-Nuke, Automod, the Join Gate and Anti-Raid: Bastion decides as normal, does nothing and says what it would have done. The dashboard warns you while Anti-Nuke is only testing
- Raid reports: every account that joined in a raid, the invite each one used and what Bastion did, kept for 30 days. /raid cleanup kicks, bans or unbans all of them at once
- The shared raid list: servers that opt in warn each other about accounts removed in raids. No server is named on it, and entries go after 30 days
- A raid alert can make everyone who joins verify until it ends
- A honeypot channel, and a check for the same message posted by several different accounts
- A web page check for verification. On Pro it can spot second accounts and VPNs without ever storing an IP address
- An AI check for scam images on Pro, where the installation is set up for it. Only the picture is sent, and only a fingerprint of it is kept so the same picture isn't checked twice
- Staff PIN on Pro: a personal 6 digit code before dangerous commands, now covering /softban, /cleanup, /raid cleanup, /unban, case edits and every part of /lockdown. A first PIN starts working after 24 hours, or at once with /pin approve
- The owner recovery key, with /recovery status and /recovery remove. A recovery owner now sees the server in their server list
- Hidden lockdown on Pro: hide every channel from members and post updates in one read-only channel
- Temporary bans, /softban, /cleanup and /purge with filters
- Your own questions on the appeal form on Pro
Changed
- The same message from many accounts now needs 5 different accounts for plain text. A message with a link, invite or mention still takes 3
- A hidden lockdown no longer needs the Administrator permission. Bastion keeps its own access to each channel it hides and gives it up again afterwards
- The VPN check on the web page starts switched off, so nothing is checked until you choose what should happen
- Signing in on the web verification page now asks Discord only who you are, and no longer creates a Bastion account
- A member on an IPv6 connection is let in when the VPN check can't cover them, and staff get a note in the verification log
- A raid cleanup acts on the accounts Bastion flagged. Acting on everyone who joined during the raid is a separate choice for the server owner
- Only the server owner can put Anti-Nuke in test mode, and it switches itself off after 24 hours
- An exempt bot is only let off deleting channels it made itself. Its ceiling starts at 20 and the owner can set it from 5 to 60
- A recovery's 48 hour wait starts once someone has been told. Cancelling keeps the key and locks it for 7 days
- A custom bot name can contain a word like system inside a longer word, such as Ecosystem
- Your data download and account deletion now cover every kind of record, and the privacy policy lists them all
Fixed
- Nickname cleaning now says which permission the Bastion role is missing instead of doing nothing
- A temporary ban can no longer be placed on someone who is already banned
- A thread opened inside the honeypot channel is deleted and nobody is punished for what was said in it