Massban
Massban is used when staff need to ban multiple users in one controlled flow.
It is useful for raids, compromised account waves, spam groups, or cleanup after a major incident.
What Massban does
Massban can:
- Accept multiple user IDs or targets depending on your version.
- Ban users in sequence.
- Respect Discord rate limits.
- Show progress while it runs.
- Track successful bans.
- Track failed or skipped users.
- Post a final summary.
- Create moderation logs and cases.
Permissions required
Lockie needs:
- Ban Members
- View Channel and Send Messages where the command is used
- Embed Links if summaries use embeds or components
- A role above the users being banned
The moderator also needs permission to use the command.
Progress messages
Lockie's improved massban flow starts with an initial progress message, then updates it while the action runs. This avoids sending too many messages and makes it easier for staff to follow the job.
The final summary should make it clear what happened.
Common fields include:
| Field | Meaning |
|---|---|
| Action | The moderation action, usually Massban. |
| Moderator | The staff member who started it. |
| Reason | The reason used for the bans. |
| Delete History | Whether message history deletion was requested. |
| Successful | Number of users banned successfully. |
| Failed or Skipped | Number of users that could not be banned or were skipped. |
| Taken | How long the action took. |
Why a user may fail or be skipped
Common causes:
- The user is already banned.
- The user ID is invalid.
- Lockie's role is too low.
- Lockie is missing Ban Members.
- Discord rejected or rate limited the action.
- The target is protected by Discord role hierarchy.
Best practices
- Use a clear reason.
- Double-check IDs before confirming.
- Use delete history carefully.
- Watch the final summary.
- Review failed or skipped users after completion.
- Avoid running multiple massban jobs at the same time.
Troubleshooting
If Massban is not working:
- Check Lockie's role position.
- Confirm Lockie has Ban Members.
- Confirm the command was used by authorized staff.
- Read the final failed or skipped count.
- Check the moderation log channel.
See Troubleshooting for permission errors.