Skip to main content
RaidBot provides extensive server-level configuration for automating raid management, reminders, and user experience features.

​
Using /settings

Access the interactive settings panel: 
/settings
This opens an embed with toggle buttons and dropdown menus to configure all server settings.
Requires “Manage Server” permission or admin role (commands/settings.js:37). Panel times out after 5 minutes (commands/settings.js:56).

​
Reminder Settings

RaidBot can automatically remind raid creators and participants before raids start.

​
Creator Reminders

Notify the raid creator before the raid begins:
​
creatorRemindersEnabled
boolean
default:"true"
Enable or disable creator reminders.Toggle: Click “Creator: On/Off” button in settings panel
​
creatorReminderSeconds
integer
default:"1800"
How many seconds before raid start to send the reminder.Default: 1800 seconds (30 minutes)Available options:
  • Disabled (0 min)
  • 5 min (300 sec)
  • 10 min (600 sec)
  • 15 min (900 sec)
  • 30 min (1800 sec)
  • 60 min (3600 sec)
Select from the “Creator reminder timing” dropdown.

​
Participant Reminders

Notify all signed-up users before the raid begins:
​
participantRemindersEnabled
boolean
default:"true"
Enable or disable participant reminders.Toggle: Click “Participant: On/Off” button in settings panel
​
participantReminderSeconds
integer
default:"600"
How many seconds before raid start to send participant reminders.Default: 600 seconds (10 minutes)Available options:
  • Disabled (0 min)
  • 5 min (300 sec)
  • 10 min (600 sec)
  • 15 min (900 sec)
  • 30 min (1800 sec)
  • 60 min (3600 sec)
Select from the “Participant reminder timing” dropdown.

​
How Reminders Work

  1. When a raid is created, the bot schedules reminder tasks
  2. At the configured time before raid start:
    • Creator reminder: DM sent to raid creator with raid details
    • Participant reminder: DM sent to all signed-up users
  3. Reminders are marked as sent to prevent duplicates (state.js:719)
Users must allow DMs from server members for reminders to work. If DM delivery fails, no error is shown to the user.

​
Auto-Close Settings

Automatically close full raids before they start to prevent last-minute signups.
​
autoCloseSeconds
integer
default:"3600"
How many seconds before raid start to auto-close if the raid is full.Default: 3600 seconds (60 minutes)Available options:
  • Disabled (0 min)
  • 15 min (900 sec)
  • 30 min (1800 sec)
  • 60 min (3600 sec)
  • 2 hours (7200 sec)
  • 8 hours (28800 sec)
  • 24 hours (86400 sec)
Select from the “Auto-close timing” dropdown.
​
lastAutoCloseSeconds
integer
default:"3600"
Internal: Remembers last auto-close setting when toggling on/off (commands/settings.js:101-107).

​
Auto-Close Behavior

  1. Bot checks all raids periodically
  2. If a raid is:
    • Full (all slots filled)
    • Not yet closed
    • Within auto-close window
  3. The raid is automatically closed
  4. Closed raids prevent new signups
  5. Waitlist users are not promoted
Use auto-close to prevent signup churn right before raids start. Recommended: 60-120 minutes.

​
Thread Settings

Create dedicated discussion threads for each raid signup.
​
threadsEnabled
boolean
default:"false"
Enable automatic thread creation for raids.Toggle: Click “Threads: On/Off” button in settings panel
​
threadAutoArchiveMinutes
integer
default:"1440"
Discord thread auto-archive duration in minutes.Default: 1440 minutes (24 hours)Options: 60, 1440, 4320, 10080 (depends on server boost level)

​
Thread Creation

When threads are enabled:
  1. Bot creates a thread attached to each raid signup message
  2. Thread name: “Raid Discussion - [Raid Type]”
  3. Thread is auto-archived after configured duration
  4. Users can discuss strategy, ask questions, etc.
Thread creation requires “Create Public Threads” permission. If permission is missing, thread creation fails silently.

​
Raid Leader Role

Mark raid creators with a special role to show leadership on signups.
​
raidLeaderRoleId
string
default:"null"
Role ID to check for raid leader marker.Selection: Use the role selector dropdown in settings panelUsers with this role who create raids get a ⭐ marker on signups.

​
Raid Leader Marker

When configured:
  1. User creates a raid
  2. Bot checks if user has the raid leader role
  3. If yes, their signup shows: Username ⭐
  4. If no, normal display: Username
This helps identify experienced raid leaders at a glance.
Use this for veteran raiders, guild officers, or certified raid leaders.

​
Timezone Settings

Set the default timezone for raid time parsing.
​
defaultTimezone
string
default:"America/New_York"
IANA timezone identifier for the server.Format: Continent/City (e.g., “America/Chicago”, “Europe/London”)Setting: Click “TZ” button in settings panel, enter timezone in modal (commands/settings.js:66-97)

​
Supported Timezones

Must be valid IANA timezone identifiers: 
America/New_York (Eastern)
America/Chicago (Central)
America/Denver (Mountain)
America/Los_Angeles (Pacific)

​
Timezone Validation

The bot validates timezone input (commands/settings.js:87-90):
  • Must be valid IANA format
  • Invalid timezones are rejected with error message
  • Helps ensure consistent time parsing
Invalid timezone format will reject the setting. Use exact IANA identifiers from the timezone database.

​
Settings Storage

All settings are stored per-guild in the database (state.js:428-497): 
CREATE TABLE guilds (
  id TEXT PRIMARY KEY,
  creator_reminder_seconds INTEGER DEFAULT 1800,
  participant_reminder_seconds INTEGER DEFAULT 600,
  auto_close_seconds INTEGER DEFAULT 3600,
  last_auto_close_seconds INTEGER DEFAULT 3600,
  creator_reminders_enabled INTEGER DEFAULT 1,
  participant_reminders_enabled INTEGER DEFAULT 1,
  raid_leader_role_id TEXT,
  threads_enabled INTEGER DEFAULT 0,
  thread_auto_archive_minutes INTEGER DEFAULT 1440,
  default_timezone TEXT DEFAULT 'America/New_York'
);
Changes are persisted immediately when settings are updated (state.js:470-496).

​
Settings Panel Components

The interactive panel includes (commands/settings.js:199-265):

​
Toggle Buttons

  • Creator: On/Off — Enable/disable creator reminders
  • Participant: On/Off — Enable/disable participant reminders
  • Auto-close: On/Off — Enable/disable auto-close
  • Threads: On/Off — Enable/disable thread creation
  • TZ: [Current] — Open timezone modal
  • Creator reminder timing — Select reminder time
  • Participant reminder timing — Select reminder time
  • Auto-close timing — Select auto-close time

​
Role Selector

  • Raid leader role — Select role for ⭐ marker

​
Best Practices

Reasonable Reminders

Set creator reminders 30-60 min before, participant reminders 10-15 min before.

Auto-Close Timing

Auto-close 60-120 minutes before raid start to prevent last-minute changes.

Enable Threads

Threads reduce channel clutter and provide dedicated discussion space.

Raid Leader Recognition

Use raid leader role to highlight experienced leaders and build community trust.

Consistent Timezone

Set timezone to match your server’s primary region for accurate time parsing.

Test Reminders

Create a test raid to verify reminder timing and DM delivery.

​
Troubleshooting

  1. Check if reminders are enabled
  2. Verify users allow DMs from server members
  3. Check bot has permission to DM users
  4. Ensure raid time is in the future (reminders don’t fire for past raids)
  1. Verify auto-close is enabled (not set to 0)
  2. Check if raid is actually full
  3. Ensure raid time is in the future
  4. Verify auto-close time hasn’t already passed
  1. Check if threads are enabled
  2. Verify bot has “Create Public Threads” permission
  3. Ensure channel allows thread creation
  4. Check server boost level for thread limits
  1. Verify raid leader role is configured
  2. Check if creator has the role
  3. Ensure role is above bot’s role in hierarchy
  4. Verify role ID is correct
Use exact IANA timezone format:
  • ✅ America/New_York
  • ✅ Europe/London
  • ❌ EST
  • ❌ GMT
  • ❌ New York
Find valid timezones at timeapi.io/timezones
  1. Ensure you have “Manage Server” or admin role
  2. Check database write permissions
  3. Look for errors in debug channel
  4. Verify settings panel hasn’t timed out (5 min limit)

​
Settings Embed Display

The settings panel shows current configuration (commands/settings.js:160-196): 
Your Server • Settings

Creator reminders: 30 min before start
Participant reminders: 10 min before start
Auto-close full raids: 60 min before start
Discussion threads: Enabled (auto-created per raid)
Raid leader role: @Raid Leader (⭐ on signups)
Default timezone: America/New_York
Disabled features show “Disabled” instead of timing.

Build docs developers (and LLMs) love

Get started for freeTalk to us