🚨 Bleed Global Lockdown & Recovery

Bleed’s Global Lockdown system allows the Owner to rapidly restrict or restore access across the server during raids, coordinated disruption, or other serious incidents.

These commands can affect many channels at once and should remain strictly Owner-only.

🔒 Lock the Entire Server

,lockdown all [reason]

Locks all applicable channels across the server.

Permission Required: Manage Channels

Use this only during a genuine server-wide emergency where individual channel lockdowns are insufficient.

Example:
,lockdown all Active raid in progress

⚠️ This can disrupt normal access across Holme immediately.

🔓 Restore the Entire Server

,unlock all [reason]

Unlocks every applicable channel after the emergency has been contained.

Permission Required: Manage Channels

Before using this, confirm that:

• the raid or disruption has ended
• malicious accounts have been removed
• spam has been cleaned
• affected permissions are understood
• reopening all channels is actually safe

🎭 Configure the Lock Role

,lockdown role [role]

Sets the default role Bleed uses when applying lockdown restrictions.

Permission Required: Manage Guild

This is a foundational setting.

Verify the selected role carefully before any emergency occurs so the lockdown system does not accidentally restrict the wrong population.

🛡️ Lockdown Ignore List

Some channels may need to remain untouched during a global lockdown.

,lockdown ignore add [channel]

Adds a channel to the lockdown ignore list.

,lockdown ignore remove [channel]

Removes a channel from the ignore list.

,lockdown ignore list

Displays all currently ignored channels.

These commands require Manage Guild.

Possible channels to consider exempting may include:

• private Owner access
• essential moderation coordination
• emergency staff communication
• critical logging channels

Only exempt channels that genuinely need to remain operational.

⚖️ Laws of Global Lockdown

I. Global Lockdown Is an Emergency Measure

Do not use ,lockdown all to handle ordinary arguments, spam from one person, or disruption limited to one channel.

II. Prefer Narrow Containment

When possible, use a single-channel lockdown before escalating server-wide.

III. Maintain Staff Communication

Ensure you retain a secure place to coordinate response while public areas are locked.

IV. Record the Reason

Every global lockdown should have a clear reason and, where appropriate, an internal record of what triggered it.

V. Do Not Reopen Prematurely

Containment ends only when the threat has actually been addressed.

VI. Audit After Recovery

After using ,unlock all, verify key channels and permissions to ensure normal access was restored correctly.

📜 Quick Reference

,lockdown all [reason] — Lock applicable channels server-wide

,unlock all [reason] — Restore applicable channels

,lockdown role [role] — Set the default lockdown role

,lockdown ignore add [channel] — Exempt a channel

,lockdown ignore remove [channel] — Remove exemption

,lockdown ignore list — View exemptions

🚨 Contain broadly only when the danger is broad. Restore carefully once Holme is secure.