👑 Bleed Role Management

Bleed’s Role Management system allows the Owner to create, edit, assign, remove, restore, and mass-manage Discord roles.

Because role hierarchy directly affects access, identity, and authority throughout Holme, these commands should remain Owner-only. Several require Manage Roles, while mass operations also require Manage Guild.

👤 Individual Role Management

,role [member] [role]

Modifies a member’s role.

,role add [member] [role]

Adds a role to a member.

,role remove [member] [role]

Removes a role from a member.

,role restore [member]

Restores roles previously associated with a member.

,temprole [member] [duration] [role]

Temporarily grants a role.

,temprole list

Lists active temporary roles.

➕ Create & Edit Roles

,role create [color] [role]

Creates a new role with an optional color.

,role edit [role] [name]

Renames an existing role.

,role delete [role]

Permanently deletes a role.

⚠️ Treat role deletion as a Destructive action.

,role icon [url] [role]

Sets a role icon.

,role color [colour] [role]

Changes a role’s color.

,role color gradient [colour] [second colour] [role]

Sets a gradient role color where supported.

,role hoist [role]

Toggles whether the role appears separately in the member list.

,role mentionable [role]

Toggles whether members may mention the role.

,role topcolor [colour] [member]

Changes the color of a member’s highest applicable role.

👥 Mass Role Operations

,role humans [role] [flags]

Adds a role to all human members.

,role humans remove [role]

Removes a role from all humans.

,role bots [role]

Adds a role to all bots.

,role bots remove [role]

Removes it from all bots.

,role has [role] [assign role]

Gives a new role to everyone who already has another specified role.

,role has remove [role] [remove role]

Removes a role from members matching another role.

,role cancel

Cancels an active mass-role operation.

⚠️ Mass commands can affect large portions of the server. Verify both roles before execution.

📋 Role Inspection

,dump [role] [flags]

Produces a list of members who possess a selected role.

Useful for audits before changing or deleting roles.

📌 Sticky Roles

Sticky roles are automatically reapplied when a member rejoins.

,stickyrole add [member] [role]

Creates a sticky-role assignment.

,stickyrole remove [member] [role]

Removes it.

,stickyrole list

Lists active sticky roles.

Permission: Server Owner

⚖️ Laws of Role Management

• Never place cosmetic roles above authority or access roles.
• Audit permissions before creating or modifying roles.
• Never use mass-role commands without checking the target first.
• Preserve staff and verification hierarchy.
• Do not use roles as retaliation or humiliation.
• Review dependencies before deleting a role.
• Keep sticky roles limited to intentional persistent access or identity needs.

👑 Roles define structure. Change them deliberately, because one misplaced role can alter far more than a name or color.

📦 Bleed Server Backups

Bleed includes export tools that allow the Owner to preserve copies of the server’s custom emojis and stickers.

These commands are useful before major server changes, expression cleanup, redesigns, or any situation where you want an offline backup of visual server assets.

Both commands require Administrator and should remain Owner-only.

😀 Export Server Emojis

,extractemotes

Exports the server’s custom emojis and sends them together in a ZIP file.

Permission Required: Administrator

This is useful before:

• deleting or replacing emotes
• reorganizing expressions
• changing server branding
• removing unused graphics
• testing a new expression set
• making major server changes

Keep the exported ZIP somewhere secure so important custom emotes can be restored or reused later if needed.

🏷️ Export Server Stickers

,extractstickers

Exports all server stickers and sends them together in a ZIP file.

Permission Required: Administrator

This serves the same backup purpose as ,extractemotes, but for Discord’s sticker collection.

Consider creating a fresh export before deleting or replacing significant sticker artwork.

🗃️ Recommended Backup Practice

These commands do not appear to create a complete backup of the Discord server.

They specifically preserve:

,extractemotes → custom emojis

,extractstickers → custom stickers

They should therefore be treated as asset backups, not as a substitute for preserving:

• channel structure
• roles and permissions
• Bleed configuration
• important embeds
• moderation records
• ticket transcripts
• server artwork
• written policies

Maintain those separately where appropriate.

⚖️ Laws of Backup Management

I. Back Up Before Deleting

Export important expressions before large-scale cleanup.

II. Preserve Original Assets

When possible, keep the original high-quality artwork in addition to Bleed’s export.

III. Protect Private Files

Do not casually distribute backup archives containing assets intended only for Holme.

IV. Organize Backups Clearly

Use dates or version names so you know when each export was created.

V. Test Before Relying on a Backup

Confirm that exported ZIP files contain the expected assets before deleting originals.

📜 Quick Reference

,extractemotes — Export all server emojis as a ZIP

,extractstickers — Export all server stickers as a ZIP

📦 What belongs to the Archive should never depend upon a single copy. Preserve before replacing, and remember before removing.

🖼️ Bleed Gallery Channels

Bleed’s Image-Only Channel system allows the Owner to designate channels where members may primarily post images with captions rather than ordinary text conversation.

This is useful for art galleries, photography, character showcases, covers, memes, or other visually focused spaces.

Configuration requires Manage Guild and should remain Owner-only.

🖼️ Open Gallery Management

,imgonly

Opens Bleed’s image-only channel configuration system.

Use this to manage channels that should function as visual galleries.

➕ Create a Gallery Channel

,imgonly add [channel]

Marks a selected channel as an image-and-caption-only gallery.

Example:
,imgonly add #art-gallery

Once configured, Bleed helps enforce the channel’s visual posting format.

This may be useful for:

• member artwork
• photography
• character designs
• book covers
• server graphics
• screenshots
• visual inspiration
• themed image collections

📋 View Gallery Channels

,imgonly list

Displays every channel currently configured as an image-only gallery.

Use this periodically to check which channels are being governed by the system.

➖ Remove Gallery Restrictions

,imgonly remove [channel]

Removes a channel from Bleed’s gallery system.

The channel can then return to normal conversation depending on its Discord permissions.

Use this when:

• retiring a gallery
• changing the channel’s purpose
• replacing Bleed’s system with another format
• troubleshooting posting restrictions

⚖️ Laws of Gallery Use

I. Make the Channel Purpose Clear

Members should know before posting that the channel is intended for images and captions rather than ordinary conversation.

II. Provide Discussion Elsewhere

If members may want to discuss artwork or images at length, provide a thread or companion discussion channel.

III. Respect Ownership

Do not use gallery channels to repost another person’s artwork deceptively or claim it as your own.

IV. Follow Archive Standards

Gallery content remains subject to the server’s SFW, harassment, privacy, and conduct rules.

V. Avoid Overusing the System

Not every image-friendly channel needs to become image-only. Use this format when visual presentation is genuinely the channel’s purpose.

📜 Quick Reference

,imgonly — Open gallery configuration

,imgonly add [channel] — Create an image-only gallery

,imgonly list — View configured galleries

,imgonly remove [channel] — Remove gallery restrictions

🖼️ Some chambers of the Archive are meant to be read. Others are meant to be seen.

🏷️ Bleed Guild Tag Rewards

Bleed’s Guild Tag Reward system lets the Owner reward members who choose to display the server’s Discord guild tag.

The system can assign reward roles, post recognition messages, synchronize qualifying members, and control where guild-tag rewards are announced.

Configuration requires Manage Guild and should remain Owner-only.

🏷️ Enable Guild Tag Rewards

,badge [setting]

Enables, disables, or manages the guild-tag reward system.

Use this as the main command for controlling whether the feature is active.

🎭 Reward Roles

,badge role

Opens reward-role management.

,badge role add [role]

Adds a role to the list of rewards members may receive for using the guild tag.

,badge role remove [role]

Removes a role from the reward list.

,badge role list

Displays all roles currently configured as guild-tag rewards.

🔐 Reward roles should remain cosmetic or community-focused. They should never grant moderation or administrative authority.

📢 Reward Channel

,badge channel [channel]

Sets the channel where Bleed posts guild-tag reward notifications.

Choose a channel where recognition fits naturally without creating unnecessary announcement spam.

💬 Reward Message

,badge message [message]

Sets the message Bleed sends when a member receives a guild-tag reward.

Bleed accepts regular text or supported embed code.

,badge message view

Displays the currently configured reward message.

Use this to review the message before replacing it.

🔄 Synchronize Rewards

,badge sync

Synchronizes guild-tag members with the configured reward roles.

This can help correct situations where:

• someone recently began using the guild tag
• someone stopped using it
• reward roles became out of sync
• the reward configuration changed

Use synchronization after major changes to the reward system.

⚖️ Laws of Guild Tag Rewards

I. Participation Must Remain Optional

Members should never feel required to display Holme’s guild tag.

II. Rewards Are Recognition, Not Rank

Guild-tag roles should not grant authority, moderation powers, or preferential treatment under the rules.

III. Avoid Excessive Rewards

Keep the system simple enough that members understand what displaying the guild tag actually provides.

IV. Keep Recognition Respectful

Reward messages should thank members without implying that those without the tag are less valued.

V. Audit Reward Roles

Periodically verify that no guild-tag reward has accidentally gained sensitive permissions.

📜 Quick Reference

,badge — Manage guild-tag rewards

,badge role add — Add reward role

,badge role remove — Remove reward role

,badge role list — View reward roles

,badge channel — Set reward channel

,badge message — Set reward message

,badge message view — View reward message

,badge sync — Synchronize qualifying members

🏷️ Let the guild tag be a sign of belonging and pride—not a mark of authority.

📱 Bleed Social Reposter

Bleed’s Reposter system manages how supported social-media links are reposted or reformatted inside Discord.

It can improve how shared social content appears by controlling embeds, original links, matching behavior, and whether Bleed reposts media automatically.

Configuration requires Manage Guild and should remain Owner-only.

📱 Reposter Management

,reposter [option]

Enables, disables, or manages Bleed’s social-media reposting system.

Use this as the main configuration command for the feature.

🖼️ Reposter Embeds

,reposter embed [option]

Enables or disables an embed alongside reposted media.

An embed may provide additional context or presentation information for the shared content.

If reposted media already provides everything members need, disabling additional embeds may keep channels cleaner.

🔎 Strict Link Matching

,reposter strict [option]

Controls how strictly Bleed identifies supported social-media links within messages.

A stricter setting may reduce accidental matches, while a more permissive setting may recognize links embedded within longer messages.

Test this before enabling it broadly.

🔗 Suppress Original Links

,reposter suppress [option]

Controls whether Bleed suppresses the original link’s normal Discord embed or presentation.

This can help prevent duplicate previews when Bleed has already reposted the media.

🗑️ Delete Original Links

,reposter delete [option]

Controls whether the original social-media link is removed after Bleed reposts its content.

⚠️ Use this carefully.

Deleting the original link may make conversations cleaner, but it also removes the member’s original source reference from the channel.

For Holme, I recommend testing suppression first before enabling automatic deletion.

⌨️ Prefix Requirement

,reposter prefix [option]

Controls whether members must use Bleed’s command prefix when requesting social-media reposting.

This can be useful if you do not want Bleed automatically reacting to every supported social link posted in the server.

⚖️ Laws of Reposting

I. Preserve Context

Do not configure reposting in a way that routinely removes useful source information.

II. Avoid Duplicate Clutter

Use suppression or embed settings to prevent several previews appearing for one link.

III. Respect Channel Purpose

Social reposting may belong in casual spaces but not announcements, moderation channels, or formal Archive resources.

IV. Do Not Treat Reposting as Archival

Social-media posts can disappear or change. Important information should be preserved separately when necessary.

V. Test Before Server-Wide Use

Confirm how each supported platform behaves before enabling automatic reposting throughout Holme.

📜 Quick Reference

,reposter — Manage social reposting
,reposter embed — Control attached embeds
,reposter strict — Control link matching
,reposter suppress — Suppress original previews
,reposter delete — Delete original links
,reposter prefix — Require Bleed prefix

📱 Let shared media travel cleanly through Holme without allowing automation to overwhelm the conversation.

🎨 Bleed Server Appearance

Bleed includes several commands for changing the visual appearance of both the Discord server itself and Bleed’s server-specific profile.

Because these tools affect Holme’s public identity and branding, they should remain strictly Owner-only.

🏛️ Discord Server Appearance

,seticon [url]

Changes the Discord server icon.

Permission Required: Manage Guild

Use a direct image URL for the new icon.

,setbanner [url]

Changes the server banner.

Permission Required: Manage Guild

This affects the large banner displayed on supported Discord server surfaces.

,setsplashbackground [url]

Changes the server’s splash background.

Permission Required: Manage Guild

The splash image may appear on supported invite or server presentation screens depending on Discord’s available features.

🤖 Customize Bleed in Holme

Bleed also allows the Server Owner to customize how the bot itself appears specifically within the server.

,customize

Opens Bleed’s server customization system.

Permission Required: Server Owner

,customize avatar [url]

Changes Bleed’s server-specific avatar.

This could allow Bleed to visually match the Archives without changing how the bot appears in other servers.

,customize banner [url]

Sets Bleed’s server-specific banner.

,customize bio [text]

Changes Bleed’s server-specific biography or description.

Permission Required: Server Owner

🎨 Recommended Use in Holme

These commands are ideal for keeping Bleed visually integrated with the identity of the Archives.

Possible uses include:

• a Holme-themed Bleed avatar
• matching banner artwork
• a short Archivist-style bot biography
• seasonal server banners
• event-specific visual changes
• updating the server icon when branding changes

The visual identity should remain recognizable even when seasonal variations are used.

⚖️ Laws of Appearance Management

I. Preserve Holme’s Identity

Major visual changes should remain consistent with the established appearance and character of the Archives.

II. Keep Official Branding Distinct

Do not configure Bleed to imitate a real member or Custodian.

III. Verify Images Before Applying

Check resolution, cropping, transparency, and suitability before changing public server graphics.

IV. Avoid Constant Changes

Frequent visual redesigns can make the server feel inconsistent and difficult to recognize.

V. Keep Backups

Preserve copies of important server icons, banners, and Bleed graphics before replacing them.

📜 Quick Reference

,seticon [url] — Change server icon

,setbanner [url] — Change server banner

,setsplashbackground [url] — Change splash background

,customize avatar [url] — Change Bleed’s Holme avatar

,customize banner [url] — Change Bleed’s Holme banner

,customize bio [text] — Change Bleed’s Holme biography

🎨 The face of the Archive should change deliberately, while remaining unmistakably Holme.

🪝 Bleed Webhook Management

Bleed’s Webhook system allows the Owner to create, manage, lock, unlock, and send messages through Discord webhooks.

Webhooks can post messages through custom identities and are useful for automation, announcements, integrations, and themed system messages.

Because webhooks can imitate custom senders and affect server content directly, these commands should remain Owner-only.

🪝 Open Webhook Management

,webhook

Opens Bleed’s webhook-management system.

➕ Create a Webhook

,webhook create [name]

Creates a webhook that can be used to send or forward messages.

Permission Required: Manage Webhooks

Choose clear names so you can identify each webhook later.

📋 View Webhooks

,webhook list

Lists available webhooks in the server.

Bleed lists no special Discord permission for this command, but within the Archivist’s Vault I would still treat webhook information as owner-level administration.

📤 Send Through a Webhook

,webhook send [identifier] [message or embed code]

Sends a message through an existing webhook.

This can be useful for:

• themed announcements
• automated notices
• system-style messages
• embeds posted under a specialized identity

✏️ Edit a Webhook Message

,webhook edit [message link] [message or embed code]

Edits a message that was sent through an existing channel webhook.

Use this when correcting or updating webhook-posted information.

🔒 Lock a Webhook

,webhook lock [identifier]

Locks a webhook so it cannot be accessed by others through Bleed.

This is especially useful for important announcement or system webhooks.

,webhook unlock [identifier]

Removes the lock.

⚠️ Only unlock a webhook when there is a clear reason to restore broader access.

🗑️ Delete a Webhook

,webhook delete [identifier]

Deletes a webhook from the channel.

Permission Required: Manage Webhooks

Treat deletion carefully, especially if other systems or integrations depend on that webhook.

⚖️ Laws of Webhook Use

I. Protect Webhook Identity

Do not create webhook identities that falsely impersonate real members or staff.

II. Lock Important Webhooks

Announcement, moderation, or system webhooks should be locked when possible.

III. Keep Ownership Clear

Members should be able to distinguish official system messages from ordinary user speech.

IV. Avoid Unnecessary Webhooks

Create only those with a defined purpose.

V. Review Before Deleting

Confirm that no automation or integration still depends on a webhook before removing it.

📜 Quick Reference

,webhook create — Create webhook
,webhook list — View webhooks
,webhook send — Send through webhook
,webhook edit — Edit webhook message
,webhook lock — Restrict access
,webhook unlock — Restore access
,webhook delete — Delete webhook

🪝 Webhooks may speak with many voices, but every official voice of Holme should remain deliberate and accountable.

📑 Bleed Pagination

Bleed’s Pagination system allows multiple embeds to be attached to a single Discord message and navigated as separate pages.

This is useful for long guides, reference material, command documentation, staff manuals, or other information that would otherwise require several separate messages.

Most pagination commands require Manage Messages and should remain Owner-only.

📖 Create Pagination

,pagination

Opens Bleed’s pagination system.

,pagination set [message link]

Converts an existing embed message into a paginated message.

Use this when you already have the first embed created and want to begin adding additional pages.

➕ Add Pages

,pagination add [message link] [embed code]

Adds another embed page to an existing pagination message.

Each page can contain its own title, description, fields, images, or other supported embed elements.

This can be useful for:

• multi-page server guides
• owner documentation
• command manuals
• historical records
• structured informational panels

✏️ Update a Page

,pagination update [message link] [id] [embed code]

Replaces or updates a specific page within an existing pagination.

Use the page ID to identify which page you want to edit.

➖ Remove a Page

,pagination remove [message link] [id]

Removes one page from a pagination message without deleting the entire system.

Double-check the page ID before removing it.

🗑️ Delete Pagination

,pagination delete [message link]

Deletes the pagination configuration attached to a specific message.

Treat this as a potentially destructive action.

📚 View Existing Paginations

,pagination list

Displays all pagination embeds currently configured in the server.

Useful for auditing old guides or finding systems that may need updating.

🔄 Restore Navigation Reactions

,pagination restorereactions [message link]

Restores the navigation reactions or controls on an existing pagination message.

Use this if the pagination still exists but its navigation controls have disappeared or been removed.

☢️ Reset All Pagination

,pagination reset

Removes every pagination configuration in the guild.

Permission Required: Administrator

⚠️ This is a Destructive command and should only be used when you intentionally want to wipe all configured pagination systems.

⚖️ Owner Guidelines

• Keep page order logical.
• Avoid creating excessively long pagination sets.
• Update outdated pages rather than duplicating guides.
• Preserve important embed code before deleting pages.
• Use ,pagination list before major cleanup.
• Never use ,pagination reset casually.

📜 Quick Reference

,pagination set — Start pagination
,pagination add — Add a page
,pagination update — Edit a page
,pagination remove — Remove one page
,pagination delete — Delete one pagination
,pagination list — View all paginations
,pagination restorereactions — Restore controls
,pagination reset — Delete all pagination systems ⚠️

📑 When one page is not enough, preserve knowledge in an ordered volume rather than scattering it across the Archive.

💡 Bleed Suggestions System

Bleed’s Suggestions system allows members to submit ideas for improving the server while giving staff tools to review, respond to, approve, deny, and track those suggestions.

The system can also use review queues, discussion threads, custom reactions, and member restrictions.

Configuration should remain Owner-only, while selected suggestion-status commands may be available to trusted Custodians.

💡 Member Suggestions

,suggest [suggestion]

Allows a member to submit an idea or feature request.

Permission: None

Suggestions should focus on constructive improvements to the community, server features, events, channels, or systems.

🏛️ Configure the System

,suggest set [channel]

Sets the channel where new suggestions are posted.

,suggest config

Displays the current suggestion configuration.

,suggest reactions [upvote] [downvote]

Sets the reactions used for community voting.

,suggest threads [setting]

Controls whether a discussion thread is created with each suggestion.

Configuration: Owner-only

👁️ Review Before Publication

,suggest review [setting]

Enables or disables review before suggestions appear publicly.

,suggest review channel [channel]

Sets the private channel where suggestions await approval.

For Holme, I recommend enabling review if you want to prevent trolling, inappropriate suggestions, or personal complaints from immediately becoming public.

📜 Suggestion Status

Trusted staff may use:

,suggest consider [id]

Marks a suggestion In Consideration.

,suggest progress [id]

Marks it In Progress.

,suggest approve [id]

Marks it Approved.

,suggest deny [id]

Marks it Denied.

,suggest reset [id]

Returns it to Pending.

,suggest reply [id] [comment]

Adds an official staff response.

These are listed by Bleed as Staff Only.

🚫 Restrict Suggestions

,suggest ignore [member or role]

Prevents a member or role from submitting suggestions.

,suggest ignore list

Shows currently ignored members or roles.

Use this only for abuse of the suggestion system—not because someone repeatedly proposes ideas you dislike.

🔒 Disable or Restore Suggestions

,suggest lock

Disables the suggestion system.

,suggest unlock

Re-enables it.

Useful during maintenance or if the system temporarily becomes overwhelmed.

⚖️ Laws of Suggestions

• Judge ideas by merit, not popularity alone.
• Do not punish members for respectfully criticizing the server.
• Denied suggestions should receive a clear reason when practical.
• Do not allow suggestions to become public callout posts.
• Personal reports belong in tickets, not suggestions.
• Voting does not guarantee implementation.
• Staff should never manipulate reactions to manufacture support.

🏛️ Owner Principle

Members may propose. Custodians may review. The Owner decides what becomes part of Holme.

💡 A good Archive remembers its traditions—but still leaves room for better ideas.

🚀 Bleed Boost Messages

Bleed’s Boost Message system lets the Owner create customized messages that are automatically posted when someone boosts the server.

This is useful for recognizing supporters, thanking members, and making server boosts feel like part of Holme rather than a generic Discord event.

Configuration requires Manage Guild and should remain Owner-only.

🚀 Boost Message Management

,boosts

Opens Bleed’s boost-message configuration system.

,boosts add [channel] [message]

Creates a boost message for the selected channel.

Example:
,boosts add #announcements Thank you for strengthening the Archives!

The actual message can be made much more elaborate using Bleed’s supported variables and embed syntax.

👁️ View a Boost Message

,boosts view [channel]

Displays the boost message currently configured for a specific channel.

Use this before editing or removing a message so you know what is already active.

📜 List Boost Messages

,boosts list

Displays all channels currently configured to receive boost messages.

This is useful if you have multiple boost announcements throughout the server.

🗑️ Remove a Boost Message

,boosts remove [channel]

Removes the configured boost message from the selected channel.

Use this when:

• changing the destination
• replacing an outdated message
• simplifying boost announcements
• retiring a channel

🧩 Boost Variables

,boosts variables

Displays all variables Bleed supports for boost messages.

Variables allow Bleed to automatically insert supported information into the message when a boost occurs.

Always check this command before designing the final message so you use Bleed’s actual supported placeholders rather than assumed ones.

🏛️ Recommended Use in Holme

A boost message should feel appreciative without making non-boosters feel lesser.

Good boost messages may:

• thank the member by name
• acknowledge their support
• celebrate the strengthening of Holme
• mention Booster privileges
• direct them toward Booster customization commands

Avoid messages that imply Boosters receive moderation authority, superior status under the rules, or special immunity.

⚖️ Laws of Boost Recognition

I. Boosting Is Support, Not Authority

A Booster may receive cosmetic rewards, but never administrative power merely for boosting.

II. Do Not Pressure Members

Boost announcements should celebrate voluntary support, not guilt others into paying.

III. Keep Recognition Appropriate

Do not flood several channels with the same boost announcement.

IV. Keep Messages Current

Update boost messages when channels, perks, or server language change.

📜 Quick Reference

,boosts add — Create a boost message
,boosts view — View one
,boosts list — List configured messages
,boosts remove — Remove one
,boosts variables — View supported variables

💎 Celebrate those who strengthen Holme, while remembering that belonging to the Archive is never measured by payment.

💎 Bleed Booster Configuration

Bleed’s Booster Role system lets Server Boosters create personalized cosmetic roles while allowing the Owner to control where those roles sit, what names they may use, how many can exist, and what additional rewards boosting provides.

Administrative configuration requires Manage Guild and/or Manage Roles and should remain Owner-only. Booster-facing customization commands can remain available to eligible Boosters.

🏛️ Base Role Position

,boosterrole base [role]

Sets the base role that custom Booster roles will appear beneath.

This is one of the most important settings.

🔐 Keep Booster roles beneath all staff, moderation, access-control, and administrative roles.

🔢 Booster Role Limits

,boosterrole limit [limit]

Sets the maximum number of Booster roles allowed.

,boosterrole list

Displays all existing Booster roles.

,boosterrole cleanup

Removes unused Booster roles.

Use cleanup periodically to prevent abandoned cosmetic roles from cluttering the server.

🎁 Booster Reward Role

,boosterrole award [role]

Sets a specific role automatically rewarded for boosting.

,boosterrole award view

Shows the current reward role.

,boosterrole award unset

Removes the configured Booster reward.

Keep reward roles cosmetic or community-oriented rather than giving moderation authority.

🚫 Role Name Filtering

,boosterrole filter [word]

Blacklists a word from being used in custom Booster role names.

,boosterrole filter list

Displays currently blacklisted words.

Use this to prevent:

• staff impersonation
• administrative titles
• offensive names
• misleading authority claims
• inappropriate role names

Consider blocking terms such as Owner, Admin, Moderator, and official staff titles.

🤝 Shared Booster Roles

Bleed allows Boosters to share their custom roles with other members.

,boosterrole share max [number]

Limits how many people may share one Booster role.

,boosterrole share limit [number]

Limits how many shared Booster roles a member may join.

,boosterrole share list

Displays members currently sharing a Booster role.

,boosterrole link [member] [role]

Links an existing role to a member as their Booster role.

These settings should prevent excessive role clutter while still allowing cosmetic sharing.

💎 Booster-Facing Commands

Eligible Boosters may use commands such as:

,boosterrole — Create a custom role
,boosterrole color — Set role colors
,boosterrole random — Generate a random color
,boosterrole dominant — Match avatar color
,boosterrole rename — Rename their role
,boosterrole icon — Set an icon
,boosterrole remove — Remove their custom role
,boosterrole share — Share it with another member

🔐 Owner Principle

Booster roles are rewards, not authority.

They should never:

• outrank Custodians
• grant moderation permissions
• bypass verification or access controls
• imitate official positions
• create confusion about server authority

💎 Let Boosters personalize their place in Holme without altering who governs it.

🤖 Bleed Autoresponders

Bleed’s Autoresponder system automatically replies when a message matches a configured trigger.

It can also restrict triggers to certain roles or channels and, when configured, assign or remove roles based on matched messages.

Because autoresponders can affect server behavior automatically, configuration should remain Owner-only.

💬 Create Automatic Replies

,autoresponder

Opens the autoresponder system.

,autoresponder add [args]

Creates a new automatic reply and its trigger.

,autoresponder update [args]

Changes an existing autoresponder.

,autoresponder remove [trigger]

Deletes the response associated with a trigger.

,autoresponder list

Lists configured autoresponders.

,autoresponder variables

Shows variables available for use inside responses.

🎟️ Ticket Autoresponders

,autoresponder list tickets

Displays autoresponders associated with the ticket system.

These may be useful for automatically providing instructions when common questions or phrases appear inside tickets.

Keep automated ticket replies informational and avoid replacing necessary human moderation judgment.

🔐 Restrict Where Triggers Work

,autoresponder exclusive [role or channel] [trigger]

Restricts an autoresponder so it can only operate for a specified role or channel.

,autoresponder exclusive list [trigger]

Displays the roles or channels with exclusive access to that trigger.

This is useful for:

• staff-only automation
• channel-specific instructions
• preventing triggers from activating everywhere
• keeping specialized responses within the correct part of Holme

🎭 Automatic Role Actions

,autoresponder role

Opens role-based autoresponder management.

,autoresponder role add [role] [trigger]

Configures a role to be given when a trigger matches.

,autoresponder role add list [trigger]

Shows roles granted by a trigger.

,autoresponder role remove [role] [trigger]

Configures a role to be removed when a trigger matches.

,autoresponder role remove list [trigger]

Shows roles removed by a trigger.

⚠️ Role automation should be tested carefully. Never allow ordinary phrases to accidentally grant sensitive or staff roles.

☢️ Reset

,autoresponder reset

Removes every autoresponder configured in the server.

Treat this as a ⚠️ Destructive command.

🏛️ Sensible Uses in Holme

Autoresponders could:

• direct members to frequently requested guides
• explain where verification help belongs
• point music questions toward command documentation
• provide ticket instructions
• remind users of channel-specific resources

Avoid excessive triggers that make Bleed interrupt normal conversations.

⚖️ Owner Principle

Automate information, not judgment.

Use autoresponders for predictable guidance and repetitive assistance. Moderation decisions, disputes, reports, and sensitive situations should remain under human review.

🤖 Let automation guide members through the Archive without allowing it to govern them.

🗃️ Bleed Pin Archival

Bleed’s Pin Archival system helps preserve important pinned messages by copying or recording them into a designated archive channel before pins are removed or reorganized.

This is especially useful in The Archives of Holme, where important messages may deserve preservation even after they are no longer actively pinned.

Configuration requires Manage Guild and should remain Owner-only.

📌 Pin Archival System

,pins

Opens Bleed’s pin-archival system.

,pins config

Displays the current pin-archival configuration.

Use this before making changes so you can verify how the system is currently configured.

,pins set [option]

Enables or disables the pin-archival system.

🗃️ Set the Archive Channel

,pins channel [channel]

Sets the channel where archived pins should be preserved.

Choose a private or public archival channel depending on the kind of messages being preserved.

📜 Do not send private staff or moderation pins into a public archive.

📥 Archive Current Pins

,pins archive

Archives the pinned messages from the current channel.

Use this before deliberately clearing or reorganizing a channel’s pins.

This can help preserve:

• important announcements
• historical community moments
• useful reference messages
• event records
• notable discussions
• long-term server information

📌 Automatic Unpinning

,pins unpin [option]

Controls whether messages are automatically unpinned during the archival process.

Enable this only if you actually want archived messages removed from the channel’s active pin list.

If preservation is your only goal, review this setting before archiving.

⚠️ Reset Configuration

,pins reset

Resets Bleed’s pin-archival configuration.

Permission Required: Manage Guild

⚠️ This should also be treated as a Destructive command because it removes the existing archival setup.

⚖️ Laws of Archival

I. Preserve Before Removing

If a pinned message may still have historical, administrative, or community value, archive it before unpinning.

II. Respect Privacy

Private staff, ticket, or moderation material should never be archived into public spaces.

III. Archive With Purpose

Do not preserve every trivial pin simply because the system allows it.

IV. Keep the Archive Organized

Use a clearly designated archival channel so preserved messages remain useful rather than becoming another cluttered feed.

V. Review Before Resetting

Confirm the current configuration before using ,pins reset.

📜 Quick Reference

,pins config — View archival settings
,pins set — Enable or disable archival
,pins channel — Set archive destination
,pins archive — Archive current pins
,pins unpin — Control automatic unpinning
,pins reset — Reset configuration ⚠️

🗃️ A message may cease to be pinned without ceasing to be worth remembering.

📌 Bleed Sticky Messages

Bleed’s Sticky Message system keeps an important message visible in an active channel by reposting or refreshing it as conversation continues.

This is useful for reminders, channel-specific rules, navigation, and instructions that members should regularly see without needing to search through older messages.

Configuration requires Manage Guild and should remain Owner-only.

📌 Sticky Message Commands

,stickymessage

Opens Bleed’s sticky-message configuration system.

,stickymessage add [channel] [message]

Creates a sticky message in the selected channel.

Example:
,stickymessage add #music-commands Use this channel for Bleed music commands only.

,stickymessage view [channel]

Displays the sticky message currently configured for a channel.

Use this to review the message before changing or removing it.

,stickymessage list

Lists all channels currently using Bleed sticky messages.

This is useful for auditing where automated reminders are active.

,stickymessage remove [channel]

Removes the sticky message from the selected channel.

🏛️ Useful Places in Holme

Sticky messages work best in channels where important instructions can easily disappear beneath regular conversation.

Possible uses include:

• music-command channels
• reporting or assistance channels
• contentious-discussion areas
• roleplay spaces with special rules
• media or gallery channels
• channels requiring specific posting formats
• community spaces with recurring reminders

⚖️ Laws of Sticky Messages

I. Keep Them Useful

Sticky messages should contain information members genuinely need to see repeatedly.

II. Avoid Excessive Automation

Do not place sticky messages in every channel. Too many repeated messages create clutter and cause members to ignore them.

III. Keep Them Concise

A sticky reminder should be quick to understand. Longer policies should link members to the appropriate guide.

IV. Keep Information Current

Remove or update sticky messages when rules, channels, or procedures change.

V. Do Not Use Them for Noise

Sticky messages should not be used for jokes, unnecessary announcements, or repetitive promotional content.

📜 Quick Reference

,stickymessage — Open sticky-message management

,stickymessage add [channel] [message] — Create a sticky message

,stickymessage view [channel] — View a channel’s sticky message

,stickymessage list — List all sticky messages

,stickymessage remove [channel] — Remove a sticky message

📌 Keep what matters visible without allowing automation to overwhelm the conversation.

👋 Bleed Welcome & Goodbye

Bleed can automatically send customized messages when members join or leave the Archives.

These systems are useful for creating a consistent first impression, welcoming new Archivists into Holme, and recording departures without relying on staff to post manually.

Configuration requires Manage Guild and should remain Owner-only.

🌅 Welcome Messages

,welcome

Opens Bleed’s welcome-message system.

,welcome add [channel] [message]

Creates a welcome message in a selected channel.

,welcome view [channel]

Displays the welcome message currently configured for that channel.

,welcome list

Lists every configured welcome message.

,welcome remove [channel]

Removes the welcome message from a selected channel.

,welcome variables

Displays the variables Bleed supports inside welcome messages.

Variables can be used to automatically insert information such as the joining member or other supported server details.

📜 Check ,welcome variables before building the final message so only confirmed Bleed placeholders are used.

🌙 Goodbye Messages

,goodbye

Opens Bleed’s departure-message system.

,goodbye add [channel] [message]

Creates a goodbye message for a selected channel.

,goodbye view [channel]

Shows the currently configured goodbye message.

,goodbye list

Lists all configured goodbye messages.

,goodbye remove [channel]

Removes a goodbye message.

,goodbye variables

Displays available variables for departure messages.

🏛️ Recommended Use in Holme

Welcome messages should feel like an arrival into the Archives, while still giving members useful information.

They may include:

• a warm greeting
• the member’s name or mention
• where to begin
• links to important public resources
• encouragement to introduce themselves or choose roles

Goodbye messages should remain simple and respectful.

Avoid departure messages that:

• publicly speculate about why someone left
• shame departing members
• encourage dogpiling or mockery
• expose moderation information

⚖️ Owner Guidelines

Keep welcome messages concise enough that repeated joins do not overwhelm a channel.

Use only channels intended for automated arrivals or departures.

Review variables after major Bleed updates.

Remove obsolete messages before replacing systems.

Do not place private moderation information into automated departure messages.

📜 Quick Reference

,welcome add — Create a welcome message
,welcome view — Preview it
,welcome list — List configured welcomes
,welcome remove — Remove one
,welcome variables — View supported variables

,goodbye add — Create a departure message
,goodbye view — Preview it
,goodbye list — List configured goodbyes
,goodbye remove — Remove one
,goodbye variables — View supported variables

👋 Let every arrival feel welcomed into Holme, and every departure be recorded with dignity.

🍯 Bleed Honeypot Protection

Bleed’s Honeypot system creates a bait channel designed to identify and automatically punish obvious spam bots, raid accounts, or malicious users who interact with a channel they should have no legitimate reason to use.

Because honeypots can automatically trigger punishment, configuration should remain strictly Owner-only.

🍯 What Is a Honeypot?

A honeypot is intentionally placed as a trap.

The channel appears accessible enough for automated spam accounts to discover or interact with, but legitimate members should be clearly instructed not to use it.

If someone triggers the honeypot, Bleed applies the punishment configured for that channel.

This can provide another layer of protection against:

• automated spam accounts
• raid bots
• mass-advertising accounts
• malicious scripted behavior
• accounts blindly posting into every available channel

➕ Create a Honeypot

,honeypot add [channel] [punishment]

Adds a channel to Bleed’s honeypot system and assigns the punishment that should occur when it is triggered.

Permission Required: Administrator

⚠️ Choose the punishment carefully.

A false trigger could affect a legitimate member, so the channel should be designed so ordinary users have no reasonable reason to interact with it.

📋 View Honeypots

,honeypot list

Displays all channels currently configured as honeypots.

Permission Required: Administrator

Use this periodically to confirm that your active honeypots are still intentional and properly placed.

➖ Remove a Honeypot

,honeypot remove [channel]

Removes a channel from Bleed’s honeypot system.

Permission Required: Administrator

This stops the channel from functioning as an automatic trap.

⚖️ Laws of Honeypot Use

I. Never Trick Legitimate Members

A honeypot should catch automated or obviously malicious behavior—not curious members.

II. Keep It Away From Normal Navigation

Do not place honeypot channels where members could reasonably mistake them for ordinary discussion spaces.

III. Use Proportionate Punishment

Configure only the level of punishment justified by triggering the trap.

IV. Review Before Escalating Further

If a honeypot action creates a moderation case, review available logs before applying additional punishment.

V. Do Not Publicize Its Mechanics

Members may know that automated security exists, but avoid publishing unnecessary details that would make the trap easier to evade.

VI. Test Carefully

Verify channel permissions and Bleed behavior before relying on the system during an actual raid.

📜 Quick Reference

,honeypot add [channel] [punishment] — Create a honeypot

,honeypot list — View configured honeypots

,honeypot remove [channel] — Remove a honeypot

🍯 A honeypot should catch those attacking the Archive—not those merely wandering through it.

🔐 Bleed Owner Permissions

These commands control how Bleed recognizes permissions, exemptions, and access at a server-wide level.

They are especially important because they can change who Bleed treats as authorized, even when Discord’s native permissions remain unchanged.

These commands should remain strictly Owner-only.

🗝️ Fake Permissions

Bleed’s Fake Permissions system allows the Server Owner to grant a role permission-equivalents inside Bleed without necessarily giving that role the corresponding native Discord permission.

,fakepermissions

Opens the Fake Permissions system.

,fakepermissions add [role] [permission]

Grants a Bleed-recognized permission to a role.

,fakepermissions remove [role] [permission]

Removes a previously granted fake permission.

,fakepermissions list [role]

Displays fake permissions currently assigned to a role.

,fakepermissions reset

Removes all fake permissions configured through Bleed.

⚠️ ,fakepermissions reset is destructive and should also carry the ⚠️ Destructive tag.

🛡️ Why Fake Permissions Matter

This system may allow Custodians to use selected Bleed commands without granting them powerful native Discord permissions such as:

• Manage Guild
• Manage Roles
• Administrator
• other elevated permissions Bleed supports

This could be extremely useful for maintaining a strict separation between moderation capability and server ownership.

⚠️ Test each fake permission carefully before relying on it. Grant only the specific capability a role actually requires.

🚫 Bleed Ignore System

The Ignore system appears to tell Bleed to stop responding to or processing a selected member or channel.

,ignore

Opens the Ignore system.

,ignore add [member or channel]

Adds a member or channel to Bleed’s ignore list.

,ignore remove [member or channel]

Removes them from the ignore list.

,ignore list

Displays all ignored members and channels.

Permission Required: Administrator

🏛️ Possible Uses for Ignore

Use the Ignore system sparingly.

Reasonable uses may include:

• channels where Bleed should never operate
• bot-only or integration channels
• resolving command conflicts
• temporarily preventing Bleed interaction in a problematic space

Do not use it casually against members simply because they are annoying or disagreeable.

⚖️ Owner Rules

Grant the minimum access necessary.

Never use fake permissions as a substitute for thoughtful role design.

Review fake permissions periodically.

Do not grant server-wide capabilities when a narrower option exists.

Document important permission changes.

Use ,ignore for technical or administrative necessity—not punishment.

📜 Quick Reference

,fakepermissions add — Grant a Bleed permission
,fakepermissions remove — Remove one
,fakepermissions list — Review assigned permissions
,fakepermissions reset — Clear all fake permissions ⚠️

,ignore add — Ignore a member or channel
,ignore remove — Restore Bleed interaction
,ignore list — View ignored targets

🔐 Bleed permissions should extend capability without surrendering control of the Archive itself.

🛡️ Bleed Automated Filters

Bleed’s Filter system automatically removes or blocks unwanted content before it becomes a larger moderation problem.

It can help control spam, mass mentions, invite links, excessive emoji, unwanted links, filtered words, music files, and other disruptive patterns.

Most configuration commands require Manage Channels or Manage Guild and should remain Owner-only.

🚨 Anti-Spam

,filter spam [channel] [setting] [parameters]

Automatically removes messages from users sending messages too quickly.

,filter spam exempt [role]

Exempts a role from the spam filter.

,filter spam exempt list

Lists exempt roles.

Use conservative thresholds so normal conversation is not accidentally punished.

📣 Mass Mentions

,filter massmention [channel] [setting] [parameters]

Deletes messages exceeding the configured mention threshold.

,filter massmention exempt [role]

Exempts trusted roles.

,filter massmention exempt list

Shows exemptions.

This is particularly useful against raids and ping spam.

🔗 Links & Invites

,filter invites [channel] [setting] [parameters]

Deletes Discord invite links.

,filter links [channel] [setting] [parameters]

Deletes messages containing links.

,filter links whitelist [channel] [url]

Whitelists an approved URL.

Both systems support role exemptions.

🔗 Avoid enabling a universal link ban unless the channel genuinely requires it.

😵 Excessive Formatting

,filter caps

Removes messages with excessive uppercase text.

,filter emoji

Removes messages exceeding the emoji threshold.

,filter spoilers

Removes messages exceeding the spoiler threshold.

Each supports channel settings and exempt roles.

🎵 Music Files

,filter musicfiles

Deletes messages containing music files.

Useful in channels where uploaded audio is not permitted.

Role exemptions are supported.

📖 Word Filtering

,filter add [word]

Adds a filtered word.

,filter remove [word]

Removes one.

,filter whitelist [word]

Adds or removes a permitted word.

,filter list

Displays the current filtered-word list.

,filter exempt [role]

Exempts selected roles.

,filter wordmigrate

Migrates filtered words into Discord AutoMod.

⚙️ Advanced Filtering

,filter regex [pattern]

Adds or removes a regular-expression pattern.

⚠️ Regex can match far more content than intended. Test patterns carefully.

,filter snipe [type]

Restricts what content can be recovered through Bleed’s snipe system.

This can help balance moderation review with member privacy.

☢️ Reset

,filter reset

Resets all legacy filtered words.

Requires: Manage Guild

⚠️ Treat this as destructive.

🏛️ Recommended Holme Priorities

Start with:

Spam → Mass Mentions → Invite Protection

Add other filters only when actual server behavior shows they are necessary.

🛡️ Automate obvious disruption without making ordinary conversation feel policed.

🔌 Bleed Command & Module Control

Bleed allows the Owner to control where commands, modules, and bot events are permitted to operate throughout the server.

This is one of the most useful configuration systems for keeping commands in the correct areas of Holme instead of allowing every feature everywhere. Most commands require Manage Channels and should remain Owner-only.

⌨️ Individual Commands

,disablecommand [channel or member] [command]

Disables a specific Bleed command for a channel or member.

,enablecommand [channel or member] [command]

Re-enables a previously disabled command.

,disablecommand list

Displays currently disabled commands.

,disablecommand all [command]

Disables a command throughout the entire server.

,enablecommand all [command]

Enables a command throughout the entire server.

⚠️ The all versions affect Holme globally. Use them carefully.

📦 Modules

A module is a broader Bleed feature or command family.

,disablemodule [channel] [module]

Disables a module in a selected channel.

,enablemodule [channel] [module]

Enables a module in a selected channel.

,disablemodule list

Shows disabled modules.

,disablemodule all [module]

Disables a module across every channel.

,enablemodule all [module]

Enables a module across every channel.

This is useful when you want to remove an entire category of functionality from certain spaces instead of disabling commands one by one.

⚡ Bot Events

Events are automatic Bleed behaviors triggered by Discord activity rather than direct commands.

,disableevent [channel] [event]

Disables a bot event in one channel.

,enableevent [channel] [event]

Re-enables it.

,disableevent list

Lists disabled events.

,disableevent all [event]

Disables an event server-wide.

,enableevent all [event]

Enables it server-wide.

📋 Copy Channel Restrictions

,copydisabled [old channel] [new channel]

Copies disabled commands, modules, events, and filters from one channel into another.

This is extremely useful when creating a new channel that should behave like an existing one.

🏛️ Recommended Holme Uses

Consider disabling:

• games in serious discussion areas
• media tools in announcement channels
• music commands outside music spaces
• roleplay commands in formal channels
• public utilities inside moderation areas

Use modules when an entire family should be unavailable.

Use individual command restrictions when only one or two commands need blocking.

🔐 Owner Principle

Members should encounter Bleed where its tools make sense—not everywhere merely because they exist.

Configure by purpose:

Social spaces may be playful.
Formal spaces should remain focused.
Staff spaces should remain controlled.

📜 Bleed Moderation Messages

Bleed’s Invoke system controls the messages members receive when moderation actions are used.

You can customize both:

DM — the private message sent to the affected member
Message — the command response shown where the moderation action occurred

These settings require Manage Guild and should remain Owner-only.

⚠️ Warnings

,invoke warn — Manage warning messages

,invoke warn dm [message] — Change the warning DM

,invoke warn dm view — View the current warning DM

,invoke warn message [message] — Change the command response

,invoke warn message view — View the current response

⏳ Timeouts

,invoke timeout — Manage timeout messages

,invoke timeout dm [message] — Set timeout DM

,invoke timeout dm view — View timeout DM

,invoke timeout message [message] — Set command response

,invoke timeout message view — View response

Release

,invoke untimeout — Manage untimeout messages

Supports the same DM, DM view, message, and message view structure.

🔇 Mutes

Bleed supports customizable messages for:

,invoke mute — Text mute

,invoke unmute — Remove mute

,invoke imute — Remove image/file permissions

,invoke iunmute — Restore image/file permissions

,invoke rmute — Remove reaction permissions

,invoke runmute — Restore reaction permissions

Each family provides commands for changing and viewing its applicable DM or command-response message.

🔒 Jail

,invoke jail — Configure jail notifications

,invoke jail dm [message] — Set the jailed member’s private notification

,invoke jail dm view — View jail DM

,invoke jail message [message] — Set the command response

,invoke jail message view — View response

Release

,invoke unjail — Configure release messages

This also supports separate DM and command-response messages.

🔒 These should reflect the Cooling Chamber protocol: explain containment calmly, avoid humiliating language, and make clear that jail is temporary de-escalation.

🔨 Bans & Removal

Bleed provides Invoke families for:

,invoke ban

,invoke tempban

,invoke softban

,invoke unban

,invoke hardban

,invoke kick

Each allows the applicable private DM and/or command response to be customized and reviewed.

🏛️ Recommended Holme Style

Moderation messages should be:

• calm and factual
• clear about what action occurred
• clear about the reason
• free from insults or sarcasm
• understandable without staff jargon
• consistent across Custodians
• informative about what happens next when appropriate

A moderation message should explain an action—not shame the person receiving it.

📜 Quick Reference

invoke [action] dm — Change private notification

invoke [action] dm view — Review private notification

invoke [action] message — Change command response

invoke [action] message view — Review command response

🔐 Owner-only configuration. Custodians perform moderation actions; the Owner defines the voice Bleed uses when those actions occur.

⚙️ Bleed Core Configuration

These commands control Bleed’s server-wide foundation: command prefixes, moderation settings, staff recognition, jail configuration, logs, music roles, aliases, and other core behavior.

Because most of these require Manage Guild or Administrator, they should remain Owner-only within the Archivist’s Vault.

⌨️ Command Prefix

,prefix

Shows the current Bleed command prefix.

Permission: None

,prefix set [prefix]

Changes Bleed’s command prefix for the server.

Permission: Administrator

,prefix remove

Removes the configured server prefix.

Permission: Administrator

⚠️ Changing the prefix affects how members use Bleed commands throughout the Archives.

⚙️ View Server Configuration

,settings

Opens Bleed’s server-configuration system.

,settings config

Displays the current guild configuration.

Use this before changing settings so you can review what Bleed is currently using.

🛡️ Staff & Moderation Settings

,settings staff [role]

Sets Bleed’s recognized staff role or roles.

,settings staff list

Lists configured staff roles.

,settings modlog [channel]

Sets the moderation-log channel.

,settings joinlogs [channel]

Sets the channel used for join and leave logs.

🔒 Jail Configuration

,settings jail [channel]

Sets the jail channel.

,settings jailrole [role]

Sets the default jail role.

,settings jailroles [yes/no]

Controls whether existing roles are removed while a member is jailed.

,settings jailmsg [message]

Sets a custom jail message.

These settings should match the Cooling Chamber and your established jail protocol.

🔇 Restriction Roles

,settings muted [role]

Sets the text-muted role.

,settings imuted [role]

Sets the image/file-muted role.

,settings rmuted [role]

Sets the reaction-muted role.

🎵 Music & Member Settings

,settings dj [role]

Sets Bleed’s DJ role.

,settings autoplay [setting]

Controls music autoplay.

,settings autonick [nick]

Sets an automatic nickname for new members.

,settings premiumrole [role]

Sets the Premium Members role for server subscriptions.

,settings baserole [role]

Sets the base position used for booster roles.

🔎 Other Configuration

,settings googlesafetylevel [yes/no] — Controls Google-command safety filtering

,settings disablecustomfms [yes/no] — Enables or disables custom Last.fm Now Playing commands

🔤 Command Aliases

,alias add [shortcut] [command]

Creates a shortcut for another Bleed command.

,alias remove [shortcut]

Removes one shortcut.

,alias list

Lists aliases.

,alias view [shortcut]

Shows what an alias executes.

,alias removeall [command]

Removes aliases associated with a command.

,alias reset

Removes all server aliases.

⚠️ Treat ,alias reset as destructive.

☢️ Destructive Resets

,settings resetcases

Resets jail-log cases.

,settings reset

Resets Bleed’s moderation configuration.

Permission: Administrator

🔐 These are Owner-only destructive commands. Review the current configuration before using either reset.

Holme was not raised upon empty ground.

Beneath its terraces stood the remains of Drakmar—ancient foundations, damaged walls, weathered carvings, temples, and civic structures left behind by another civilization.

The Holmans did not erase them.

They preserved what could be preserved, strengthened what could still bear weight, and adapted the ruins to serve the living.

Thus, Holme’s architecture became an agreement between memory and possibility.

Dark, ancient stone remained visible beneath newer halls of ivory marble. Old carvings entered repaired walls. Broken foundations supported colonnades, residences, gardens, and institutions their first builders could never have imagined.

The city grew through terraces shaped by the land and its waters.

Domes rose above residential courtyards.

Bridges crossed canals and descending gardens.

Crimson drapery softened civic halls of ivory stone, while bronze and antique gold marked doors, lamps, lifts, fountains, and public monuments.

But Holman architecture was not created merely to appear beautiful.

It was designed to make flourishing possible.

Every district formed a civic constellation. Homes stood within a short journey of Markets, Forums, Athenaeums, Baths, Nymphaea, clinics, Valetudinaria, Topiaria, Hospitia, and quiet Diaeta where citizens could withdraw for rest.

“No essential part of a flourishing life should be distant from home.”

That principle shaped the city more profoundly than ornament.

Ramps and public lifts joined the elevations. Covered colonnades sheltered pedestrians. Elevated paths crossed steep terrain, while bridges connected districts separated by water and stone.

Beneath the visible streets, the Cryptoporticus formed another network.

Its covered corridors allowed movement during poor weather, provided quiet passage between civic complexes, and carried services beneath crowded public spaces. Heavy goods traveled through canals, service routes, and the Emporium rather than overwhelming the roads intended for ordinary life.

Water moved through Holme as deliberately as its citizens.

The Four Rivers fed canals, gardens, baths, orchards, workshops, fountains, and memorial pools. Water sustained public health, cultivation, craft, contemplation, and remembrance.

Nothing existed alone.

A residence belonged to a courtyard.

A courtyard opened toward a garden.

A garden depended upon water.

Water passed through mechanisms protected by stone.

Stone supported the halls where citizens learned how to preserve the Republic that had built them.

Holme therefore appeared monumental without becoming distant.

Its grandeur did not demand that ordinary people stand beneath it in awe.

Its grandeur invited them inside.

The Eternal City remembered Drakmar by allowing its foundations to carry a civilization devoted not merely to survival—

but to living well.

◀Previous · 🏛️ Master Archive · Next ▶

🎟️ Bleed Ticket Management

These commands are for Custodians and authorized staff responsible for handling tickets inside the Archives.

Use them to claim responsibility, move or rename tickets, control access, generate transcripts, correct reasons, and close or reopen cases when necessary.

Ticket commands should be used for case handling and member support, not for convenience, favoritism, or hiding mistakes.

🛡️ Claiming Responsibility

,tickets claim [channel] [reason]

Claims a ticket and marks you as the Custodian responsible for handling it.

,tickets unclaim [channel]

Releases a claimed ticket so another Custodian can take responsibility.

Claim only tickets you are prepared to actively handle.

✅ Closing & Reopening

,tickets close [channel] [reason]

Closes a resolved ticket.

,tickets reopen [channel] [reason]

Reopens a closed ticket when further review is needed.

Use clear reasons so later staff can understand why the status changed.

🗂️ Move & Rename

,tickets move [channel] [reason]

Moves or reclassifies a ticket into the correct ticket option.

,tickets rename [channel] [new-name]

Renames a ticket channel when clarification or organization is needed.

Do not rename tickets in ways that mock, expose, or unnecessarily identify members.

📜 Transcripts

,tickets transcript [channel|case_id]

Generates or retrieves the transcript associated with a ticket.

Transcripts may contain sensitive moderation or personal information.

Keep them within authorized staff spaces unless there is a legitimate reason to disclose them.

👥 Ticket Access

,tickets allow @member

Grants another member access to the current ticket.

,tickets deny @member

Removes manually granted ticket access.

,tickets allow list

Shows members who were manually granted access.

Only add people who genuinely need to participate in the case.

✏️ Correct Ticket Reasons

,tickets reason [action] [target] [reason]

Updates or corrects the recorded reason for a ticket action.

Use this to fix incomplete, inaccurate, or unclear records—not to rewrite history dishonestly.

📋 View Tickets

,tickets list

Displays current tickets when needed.

Use this for workload awareness and case management.

⚖️ Laws of Ticket Handling

I. Claim With Responsibility

Do not claim tickets merely to reserve them. If you cannot handle the case, unclaim it.

II. Preserve Privacy

Ticket contents, transcripts, reports, identities, and evidence remain private unless disclosure is necessary for moderation.

III. Limit Access

Only add members whose participation is genuinely relevant.

IV. Record Clear Reasons

Closures, reopenings, moves, and corrections should have understandable reasons.

V. Do Not Alter Records to Conceal Mistakes

Correct errors transparently rather than rewriting actions to make staff appear faultless.

VI. Close Only When Resolved

Do not close a ticket simply because the conversation is inconvenient or difficult.

VII. Reopen When Necessary

If new evidence, an appeal, or unresolved concerns emerge, reopen the case rather than forcing a new one unnecessarily.

VIII. Preserve Transcripts

Important tickets should have transcripts preserved according to Archive retention practices.

🛡️ Custodian Principle

Claim carefully. Investigate fairly. Record clearly. Resolve completely. Preserve what matters.

👁️ Bleed Snipe & Message Review

These commands allow Custodians and authorized staff to review recently deleted or edited messages, inspect removed reactions, and clear Bleed’s stored snipe history.

They are intended for moderation, evidence review, and incident investigation—not casual surveillance.

🗑️ Deleted Messages

,snipe [index]

Shows a recently deleted message.

Use the optional index to look further back through Bleed’s stored deleted-message history.

Example:
,snipe 2

Use this when deleted content may be relevant to harassment, threats, rule violations, or another active moderation concern.

✏️ Edited Messages

,editsnipe [index]

Shows a recently edited message and its previous content.

The optional index allows older stored edits to be reviewed.

This can help determine whether a member significantly changed a message after it became part of a moderation issue.

🎭 Removed Reactions

,reactionsnipe

Shows the most recent reaction removed from a message.

,reactionhistory [message link]

Displays recorded reaction activity for a specific message.

Requires: Manage Messages

Useful when reactions themselves are part of harassment, targeted hostility, dogpiling, or another moderation concern.

🧹 Clear Stored Snipe History

,clearsnipe

Clears Bleed’s stored history for deleted messages, edited messages, and removed reactions.

Requires: Manage Messages

⚠️ This removes potentially useful moderation information. Do not clear stored history while an active case or appeal may still depend on it.

⚖️ Laws of Snipe Review

I. Use Must Have a Moderation Purpose

Custodians may use snipe tools only when there is a reasonable moderation, safety, or incident-review need.

Curiosity is not sufficient.

II. No Casual Surveillance

Do not routinely inspect deleted or edited messages merely to see what members were saying.

A deleted message does not automatically imply wrongdoing.

III. Review Only What Is Necessary

Investigate only enough history to understand the relevant incident.

Do not search further into unrelated member activity once the necessary context has been established.

IV. Preserve Context

A deleted or edited statement should not be judged in isolation when surrounding conversation materially changes its meaning.

Review the relevant context before taking action.

V. Snipe Evidence Is Not Automatically Proof

Stored content may provide useful evidence, but it should be assessed alongside context, other logs, screenshots, witness reports, and member explanations where appropriate.

VI. Do Not Publicly Expose Retrieved Content

Information recovered through moderation tools should remain within appropriate staff or case-record spaces unless disclosure is necessary for a legitimate moderation reason.

VII. Preserve Evidence Before Clearing

Before using ,clearsnipe, confirm that no active case, appeal, report, or investigation still requires the stored information.

VIII. Never Weaponize Private Review

Custodians must not use recovered messages to embarrass, mock, retaliate against, or gain leverage over a member.

🛡️ Custodian Principle

Review what is necessary. Preserve context. Record what matters. Respect what does not.

These tools exist to recover evidence that would otherwise be lost—not to turn deleted thoughts into permanent public records.

🔒 Jail & Cooling Chamber Protocol

🐦‍🔥 Purpose of the System

The jail system is a temporary containment and de-escalation tool.

Use it when a member is too disruptive, heated, combative, or unwilling to disengage appropriately, but an immediate ban is not necessary.

Jail exists to restore order—not to humiliate, punish indefinitely, or win an argument.

⚖️ The Cooling Chamber

When jailed, a member is confined to the Cooling Chamber within:

⚖️ 𝗧𝗛𝗘 𝗛𝗔𝗟𝗟 𝗢𝗙 𝗖𝗢𝗡𝗧𝗘𝗡𝗧𝗜𝗢𝗨𝗦 𝗔𝗙𝗙𝗔𝗜𝗥𝗦

The Cooling Chamber is hidden from ordinary members.

While jailed, the member should only have access to the designated Cooling Chamber and any staff interaction Bleed specifically permits. The rest of Holme becomes inaccessible until release.

Cooling Chamber:
https://discord.com/channels/1539409856354844725/1540908011470725221

Contentious Affairs:
https://discord.com/channels/1539409856354844725/1540908009587478631

🔒 Jailing a Member

,jail @member [duration] [reason]

Example:
,jail @Member 30m Repeated disruption after being asked to disengage.

Bleed applies the jail restriction and removes normal server access.

All jail-related moderation records are kept privately within:

🛡️ 𝗧𝗛𝗘 𝗖𝗨𝗦𝗧𝗢𝗗𝗜𝗔𝗡𝗦 𝗢𝗙 𝗛𝗢𝗟𝗠𝗘

Records should establish:

• who was jailed
• which Custodian acted
• why the action occurred
• when it occurred
• when the member was released

🛡️ While Someone Is Jailed

Custodians should:

• explain the reason when necessary
• allow time for the member to calm down
• focus on the immediate issue
• avoid taunting, baiting, or escalating
• document further misconduct
• determine whether release or escalation is appropriate

The member does not need to agree with staff or admit wrongdoing before release.

The real question is:

Are they ready to return without immediately restarting the disruption?

🔓 Releasing a Member

,unjail @member [reason]

Once released, Bleed removes the jail restriction and normal server access returns.

✅ When Jail Is Appropriate

Use jail for:

• arguments escalating across multiple channels
• repeated refusal to disengage
• angry flooding or disruption
• continued personal attacks after being told to stop
• situations where temporary separation may prevent harsher action

❌ When Jail Is Not Appropriate

Do not jail someone merely because they:

• disagree with a Custodian
• hold an unpopular opinion
• criticize a moderation decision
• are irritating but not disruptive
• participate in contentious discussion within the rules

Disagreement alone is not misconduct.

🚨 Escalation

If a jailed member continues threatening or harassing others, attempts to evade jail, uses alternate accounts, makes credible threats, or demonstrates that containment is no longer sufficient, escalate appropriately.

Possible actions include:

Timeout → stronger restriction → ban

🐦‍🔥 Custodian Principle

Separate. De-escalate. Resolve. Release.

When resolution is no longer realistic:

Escalate appropriately.