Settings Commands

Configure Raptor's behavior and logging for your server.

Logging Configuration

settings logchannel

Sets the default channel where message logs are sent.

Usage:

/settings logchannel [channel]

Example:

/settings logchannel #mod-logs

What Gets Logged:

• Message edits and deletions
• Message-log fallback events when no dedicated channel exists

Required Role: Admin

settings modactionchannel

Sets an optional dedicated channel for manual moderation actions.

If this is not configured, these events continue going to the default message log channel.

Usage:

/settings modactionchannel [channel]

Example:

/settings modactionchannel #mod-actions

What Gets Logged:

• Clears/purges
• Warnings issued/removed
• Mutes and unmutes
• Kicks and bans
• Unbans
• Channel lockdown/hide actions

Required Role: Admin

settings logoverride_add

Adds or updates a channel/category override for message edit/delete logs.

Use this when you want one area (like #nsfw) to log to a different channel than the default mod log channel.

Usage:

/settings logoverride_add [log_channel] [source_channel?] [source_category?] [events?]

Examples:

/settings logoverride_add #nsfw-logs source_channel:#nsfw events:both
/settings logoverride_add #tickets-logs source_category:Tickets events:delete

Rules:

• Provide exactly one source: source_channel or source_category
• events supports edit, delete, or both
• Channel overrides are checked before category overrides

Required Role: Admin

settings logoverride_remove

Removes an existing message log override.

Usage:

/settings logoverride_remove [source_channel?] [source_category?]

Examples:

/settings logoverride_remove source_channel:#nsfw
/settings logoverride_remove source_category:Tickets

Required Role: Admin

settings logoverride_list

Shows all configured message log overrides.

Usage:

/settings logoverride_list

Required Role: Admin

settings joinchannel

Sets the channel for member join/leave notifications.

Usage:

/settings joinchannel [channel]

Example:

/settings joinchannel #member-logs

What Gets Logged:

• Member joins
• Member leaves
• New member information
• Join timestamps

Required Role: Admin

settings modmaillogchannel

Sets an optional dedicated channel for Modmail ticket archives and block/unblock alerts.

If this is not configured, these events fall back to the default message log channel.

Usage:

/settings modmaillogchannel [channel]

Example:

/settings modmaillogchannel #modmail-logs

What Gets Logged:

• Ticket closure archives
• User block alerts
• User unblock alerts

Required Role: Admin

settings modmaillogoverride_add

Adds or updates a role-based override for modmail logs.

Use this when you want logs for tickets assigned to certain roles (like QA Testers or Admins) to go to a separate channel.

Usage:

/settings modmaillogoverride_add [role] [log_channel]

Example:

/settings modmaillogoverride_add @QA-Testers #qa-modmail-logs

Rules:

• The log channel is determined by the role the modmail ticket is currently assigned to.

Required Role: Admin

settings modmaillogoverride_remove

Removes an existing modmail role override.

Usage:

/settings modmaillogoverride_remove [role]

Required Role: Admin

settings modmaillogoverride_list

Shows all configured modmail role overrides.

Usage:

/settings modmaillogoverride_list

Required Role: Admin

settings announceupdate

Sets the fallback channel for bot announcements.

Usage:

/settings announceupdate [channel]

Example:

/settings announceupdate #announcements

Used For:

• Bot update announcements
• Service notifications
• Important system messages

Required Role: Admin

settings tempvoicecreatevc

Creates and binds a dedicated voice channel that users can join to auto-create their own temporary VC.

Usage:

/settings tempvoicecreatevc [category] [trigger_name] [default_vc_name]

Example:

/settings tempvoicecreatevc Voice Channels "Join to create vc" "Temp VC - {user}"

What It Configures:

• Temp voice creation category
• Voice-to-create trigger channel bind
• Default temporary VC name template

Template Placeholders:

• {user}
• {display_name}
• {username}

Required Role: Admin

Content Configuration

Permission Role Configuration

Set the custom moderator roles for Raptor's permission system.

settings modrole

Sets the moderator role for standard moderation access.

Usage:

/settings modrole [@Role]

Example:

/settings modrole @Moderator

Access Level:

• Full moderation capabilities
• Can issue warnings, mute, kick
• Can manage filters and settings

Required Role: Admin

settings adminrole

Sets the administrator role for full access.

Usage:

/settings adminrole [@Role]

Example:

/settings adminrole @Administrator

Access Level:

• All moderation capabilities
• Server configuration access
• Full system control

Required Role: Admin

settings trial_mod

Sets the trial moderator role for limited access.

Usage:

/settings trial_mod [@Role]

Example:

/settings trial_mod @TrialMod

Access Level:

• Basic moderation only
• Limited warning system access
• Supervised capabilities

Required Role: Admin

settings honeypotrole

Sets the honeypot auto-kick role.

Usage:

/settings honeypotrole [@Role]

Example:

/settings honeypotrole @Honeypot

Description:

• Any member who is assigned this role will be instantly kicked from the server.
• This is highly effective as a honeypot trap to catch malicious raid bots that auto-assign all server roles to themselves upon joining.

Required Role: Admin

Honeypot Channel Protection

Designates one or more channels as trap/honeypots. Any non-staff member who sends a message in these channels will trigger immediate moderation action (Ban or Kick).

Dashboard Configuration: Configure this feature exclusively via the web dashboard: Dashboard -> Select Server -> Core Settings -> Honeypot Channel Protection

Configurable Settings:

• Honeypot Channels: Multi-select dropdown containing channels designated as traps.
• Action Severity: Configurable action taken on triggering members (options: Ban or Kick, defaulting to Ban).
• Whitelist Staff: Exempts Admins, Moderators, and Trial Moderators from triggering the trap.
• Auto Post Message: Automatically posts a warning/bait embed in newly assigned honeypot channel(s) when settings are saved.

settings send_typing

Toggles whether the bot shows a "is typing..." status in the channel while executing prefix (non-slash) commands.

Usage:

/settings send_typing [enabled]

Example:

/settings send_typing enabled:True

Required Role: Admin

settings delete_mod_prefix_commands

Toggles whether authorized moderation prefix commands are automatically deleted after the bot confirms the user can run them. This setting is enabled by default.

Usage:

/settings delete_mod_prefix_commands [enabled]

Example:

/settings delete_mod_prefix_commands enabled:False

Also Available In Dashboard:

Dashboard -> Select Server -> Core Settings -> General Configuration -> Delete Authorized Mod Prefix Commands

Applies To:

• Legacy moderation prefix commands such as clear, kick, ban, mute, announce, warn, warnings, delwarning, and warnnote
• Only invocations that pass the bot's role-based permission check

Required Role: Admin

settings notifications

Toggles direct message notifications sent to members when their messages are censored, or when they are muted, banned, warned, or kicked. By default, all notifications are enabled.

Usage:

/settings notifications [censor_dm: True/False] [mute: True/False] [ban: True/False] [warn: True/False] [kick: True/False]

Example:

/settings notifications censor_dm:False mute:False kick:False

Required Role: Admin

settings embed_logging

Toggles whether message logs (edits, deletions, censors) are sent as rich embeds or custom plain text layouts with synchronized application emojis. By default, embeds are enabled.

Usage:

/settings embed_logging [enabled]

Example:

/settings embed_logging enabled:False

Required Role: Admin

Configuration Checklist

After setting up Raptor, verify your configuration:

• [ ] Log channel set: /settings logchannel

• [ ] Message log overrides configured as needed: /settings logoverride_add

• [ ] Modmail log channel set: /settings modmaillogchannel

• [ ] Join channel set: /settings joinchannel

• [ ] Announcement channel set: /settings announceupdate

• [ ] Temp voice creator channel configured: /settings tempvoicecreatevc or Dashboard → Core Settings

• [ ] Moderator roles configured: /settings modrole, /settings adminrole, /settings trial_mod

• [ ] Starboard module configured in Dashboard → Starboard

Dashboard Starboard Module

Starboard is configured from the web dashboard for each server.

Path:

Dashboard -> Select Server -> Starboard

Available Settings:

• Enabled toggle
• Destination channel
• Reaction mode (⭐ only or any emoji)
• Reaction threshold (minimum reaction count)
• Channel blacklist
• Category blacklist

Access Required: Dashboard Editor or Dashboard Admin

Viewing Current Settings

Troubleshooting

Settings not applying?

• Ensure you have Manage Server permission
• Verify the bot has permission to send messages in log channels
• Restart the bot if changes don't take effect

Logs not appearing?

• Check that the log channel exists and bot can access it
• Verify the channel permissions allow the bot to post
• Confirm logging is enabled in settings

Need special routing for specific channels/categories?

• Use /settings logoverride_add or Dashboard → Core Settings → Message Log Overrides