🔨 Bleed High-Level Enforcement

These commands sit above ordinary moderation because they can permanently harden punishments, alter staff status, define ban behavior, or configure core moderation infrastructure.

They should remain strictly Owner-only.

🔒 Hardban

,hardban [member] [reason]

Keeps a member banned through Bleed’s hardban system.

Requires: Administrator + Antinuke Admin

Use this for members who must remain banned and should not be casually restored through ordinary moderation workflows.

,hardban list

Displays all currently hardbanned members.

Use this when reviewing permanent or highly restricted bans.

🛡️ Remove Staff Access

,stripstaff [member]

Removes staff roles from a member.

Requires: Administrator

This should be reserved for situations such as:

• staff removal
• compromised staff accounts
• serious misconduct by staff
• emergency containment

A Custodian should never be able to strip another Custodian’s authority.

🔨 Default Ban Purge

,ban purge [delete history]

Sets the default amount of message history deleted when a member is banned.

Requires: Manage Guild + Ban Members

This affects future ban behavior, so choose the default carefully.

Avoid automatically deleting more history than necessary, especially when messages may still be relevant to moderation evidence.

⚙️ Moderation Setup

,setup

Starts Bleed’s moderation-system setup process.

Requires: Administrator

Use this when initially configuring or substantially rebuilding Bleed moderation.

,setupmute

Configures muted roles and the channel permissions associated with them.

Requires: Manage Guild + Manage Channels

This should align with the muted, image-muted, and reaction-muted roles already defined in Bleed’s core settings.

🪪 Forced Nicknames

,forcenickname [member] [name]

Forces a member to retain a selected nickname.

Requires: Manage Guild + Manage Nicknames

,forcenickname list

Displays all currently forced nicknames.

Use this only when there is a legitimate moderation or safety need, such as repeatedly inappropriate or impersonating nicknames.

Do not use it simply to control harmless member identity or expression.

🔎 Permission Inspection

,permissions [member] [channel]

Checks the permissions a member has within a selected channel.

Requires: Manage Roles + Manage Channels

This is useful when diagnosing:

• unexpected access
• moderation-role problems
• jail or mute failures
• channel visibility issues
• permission conflicts

⚖️ Laws of High-Level Enforcement

• Hardbans should be exceptional, not routine.
• Staff removal belongs to the Owner alone.
• Preserve evidence before changing ban-history deletion settings.
• Forced nicknames require a legitimate moderation reason.
• Test moderation infrastructure after setup changes.
• Use permission inspection before making broad role or channel changes.
• Never grant these tools merely for convenience.

📜 Quick Reference

,hardban — Apply a persistent ban
,hardban list — Review hardbans
,stripstaff — Remove staff roles
,ban purge — Set default ban-history deletion
,setup — Configure moderation system
,setupmute — Configure mute infrastructure
,forcenickname — Enforce nickname
,forcenickname list — View forced nicknames
,permissions — Inspect channel permissions

🔨 High-level enforcement exists to protect the structure of Holme when ordinary moderation is no longer enough.