☢️ Bleed Mass Actions & Recovery

These commands can affect many members, invitations, or moderation records at once.

They are intended for exceptional maintenance, emergency recovery, or correcting large-scale mistakes—not routine moderation.

Because several actions can be difficult or impossible to reverse, these commands should remain strictly Owner-only.

🔓 Unban Everyone

,unbanall

Begins removing every ban currently applied to the server.

Permission Required: Server Owner

⚠️ This affects the entire ban list.

Possible legitimate uses include:

• recovering from an accidental mass-ban
• rebuilding a server’s ban policy
• correcting catastrophic moderation errors

Do not use this merely to review bans or pardon individual members.

,unbanall cancel

Cancels an active unban-all operation.

Use this immediately if the task was started accidentally or conditions change.

🗑️ Remove All Punishment History

,history removeall [member]

Removes every recorded punishment associated with a particular member.

Permission Required: Administrator

This is substantially more serious than removing one incorrect case.

Use it only when the complete record is genuinely invalid, duplicated, corrupted, or intentionally being cleared for a documented reason.

📜 Individual mistakes should normally be corrected with the single-case removal command instead.

📨 Clear Server Invites

,clearinvites [params]

Removes existing invitations from the guild.

Permission Required: Manage Guild

This can be useful when:

• invite links were leaked
• a raid is using known invites
• access links need to be rotated
• old or uncontrolled invites require retirement

⚠️ Clearing invites may invalidate legitimate links being used elsewhere.

Review important entry links before executing this command.

🚨 Related Mass-Enforcement Tools

,recentban [count] [reason]

Bulk-bans a specified number of recently joined accounts.

Permission Required: Ban Members

,raid [time] [action] [reason]

Acts against members who joined within a specified raid window.

Permission Required: Ban Members

Trusted emergency Custodians may use these only if explicitly authorized, but the Owner should retain final control over their policy and use.

⚖️ Laws of Mass Actions

I. Prefer Individual Actions

Never use a mass command when the same problem can be safely handled member-by-member.

II. Confirm Scope First

Know exactly how many users, records, or links may be affected before executing the command.

III. Preserve Records

Take screenshots, exports, logs, or other records before removing large amounts of moderation information.

IV. Use Cancellation When Available

If an accidental mass task begins, stop it immediately rather than waiting to see what happens.

V. Document Exceptional Actions

Record why a mass operation occurred and what was affected.

VI. Recovery Is Not Erasure

Do not use mass-clearing tools merely to hide inconvenient history or staff mistakes.

📜 Quick Reference

,unbanall — Unban every member ⚠️
,unbanall cancel — Stop the task
,history removeall [member] — Clear all punishment history ⚠️
,clearinvites — Remove server invites ⚠️
,recentban — Bulk-ban recent joins
,raid — Act against a raid window

☢️ Mass actions exist for extraordinary circumstances. Confirm the scope before changing the Archive at scale.