Masspurge

Masspurge is used to delete messages from a selected user across supported channels.

It is useful after spam, raids, repeated rule-breaking, or cleanup where a normal channel purge is not enough.

What Masspurge does

Masspurge can:

• Search supported text and announcement/news channels.
• Find messages from a selected user.
• Delete messages Lockie has permission to remove.
• Show progress while it runs.
• Report what was deleted and what was skipped.
• Keep staff informed through moderation logs.

Permissions required

Lockie needs:

• View Channel in every channel being checked.
• Read Message History in every channel being checked.
• Manage Messages in every channel where messages should be deleted.
• Send Messages and Embed Links where the progress summary is posted.

The moderator also needs permission to use the command.

Supported channels

Masspurge is designed for channels where message cleanup makes sense, such as:

• Text channels
• Announcement or news channels, if supported by the bot version

It may skip unsupported channels, inaccessible channels, threads, or channels where Lockie lacks permissions.

Progress and summary

Like Massban, the improved Masspurge flow should keep one progress message updated rather than spamming the channel.

A good summary should show:

• Action
• Moderator
• Target user
• Successful deletes
• Failed or skipped items
• Channels checked
• Time taken

Why messages may not delete

Common causes:

• Lockie cannot view the channel.
• Lockie is missing Manage Messages.
• The message is too old for Discord bulk delete behavior.
• The channel type is unsupported.
• The message was already deleted.
• Discord rate limits slowed the action.

Best practices

• Run Masspurge from a staff channel.
• Keep logs enabled.
• Avoid starting multiple large cleanup jobs at once.
• Review skipped channels after the job finishes.
• Use normal /purge for small single-channel cleanup.

Troubleshooting

If Masspurge does not remove messages:

1. Confirm Lockie has Manage Messages in the affected channels.
2. Confirm Lockie can Read Message History.
3. Confirm the messages are from the selected user.
4. Check whether messages are too old for bulk delete behavior.
5. Review the summary for skipped channels or failures.

See Troubleshooting for permission errors.