Skip to main content
RaidBot needs to know where to post different types of signups. Use the /setchannel command to configure channel destinations for each signup type.

​
Channel Types

RaidBot supports multiple channel destinations for different raid types and logging:

Raid Channel

Where standard raid signups are posted (Dragonspyre, Lemuria, Polaris, etc.)

Museum Channel

Where museum run signups are posted

Key Boss Channel

Where gold key boss signups are posted

Challenge Channel

Where challenge mode signups are posted

Audit Log Channel

Where audit logs for raid actions are recorded

Debug Log Channel

Where debug logs and errors are sent for troubleshooting

​
Using /setchannel

The /setchannel command provides an interactive panel to configure all channels at once, or you can set specific channels directly using command options.

​
Interactive Mode

Run /setchannel without options to open an interactive configuration panel: 
/setchannel
This opens an embed showing current channel configurations with dropdown menus to select new channels for each type.
The interactive panel times out after 5 minutes of inactivity (commands/setchannel.js:98).

​
Direct Channel Setting

Set specific channels directly using command options: 
/setchannel raid_channel:#raid-signups

​
Setting Multiple Channels

You can set multiple channels in one command: 
/setchannel raid_channel:#raid-signups museum_channel:#museum-runs audit_channel:#logs

​
Command Options

​
raid_channel
channel
Text channel where raid signups will be posted. Created via /create for raid type.Requirements: Must be a text channel (commands/setchannel.js:21)
​
museum_channel
channel
Text channel where museum run signups will be posted. Created via /create for museum type.Requirements: Must be a text channel (commands/setchannel.js:26)
​
key_channel
channel
Text channel where gold key boss signups will be posted.Requirements: Must be a text channel (commands/setchannel.js:31)
​
challenge_channel
channel
Text channel where challenge mode signups will be posted.Requirements: Must be a text channel (commands/setchannel.js:36)
​
audit_channel
channel
Text channel for audit logs tracking:
  • Raid creation and deletion
  • Signup modifications
  • Permission changes
  • Admin actions
Requirements: Must be a text channel (commands/setchannel.js:41)
​
debug_channel
channel
Text channel for debug logs including:
  • Error messages
  • Performance warnings
  • Rate limit alerts
  • System diagnostics
Requirements: Must be a text channel (commands/setchannel.js:46)
Debug logging is useful for troubleshooting but can be verbose. Consider a private admin-only channel.

​
Channel Status

After setting channels, the bot displays current configuration: 
Channels updated.
Raid: #raid-signups
Museum: #museum-runs
Key: #key-boss
Challenge: #challenge-mode
Audit: #bot-audit
Debug: Not set
Channels marked as “Not set” are optional. Signups for those types will fail until a channel is configured.

​
Permissions Required

The bot needs these permissions in configured channels:
  • View Channel — To access the channel
  • Send Messages — To post signup embeds
  • Embed Links — For rich signup displays
  • Add Reactions — To add role reaction buttons
  • Manage Messages — To update and delete signups
  • Read Message History — To track existing signups
  • View Channel — To access the channel
  • Send Messages — To post log entries
  • Embed Links — For formatted log messages
If the bot lacks required permissions, signup creation will fail. Ensure the bot’s role is positioned above channel permission overrides.

​
Data Storage

Channel configurations are stored per-guild in the database (state.js:216-307):
  • Raid channels: guilds.raid_channel_id
  • Museum channels: guilds.museum_channel_id
  • Key channels: guilds.key_channel_id
  • Challenge channels: guilds.challenge_channel_id
  • Audit channels: guilds.audit_channel_id
Changes are persisted immediately to the SQLite database.

​
Troubleshooting

  1. Verify the correct channel is set with /setchannel
  2. Check bot permissions in the target channel
  3. Ensure the channel is a text channel (not voice/announcement)
  4. Check debug logs if debug channel is configured
  • The channel must be a text channel
  • You must have “Manage Server” permission
  • The bot must have access to view the channel
  • Ensure you’re not timing out (5 minute limit)
  • Check that the database is writable
  • Verify no errors in debug channel

​
Best Practices

Separate Channels

Use different channels for raid types to keep signups organized and reduce clutter.

Archive Old Signups

Consider auto-archiving completed raids using Discord’s thread feature (see Settings).

Private Logs

Keep audit and debug channels private to prevent spam and protect sensitive information.

Clear Names

Use descriptive channel names like #raid-signups instead of #raids for clarity.

Build docs developers (and LLMs) love

Get started for freeTalk to us