Skip to main content
Once a raid is created, you can manage it using the /raid command with the raid’s unique ID. This opens an interactive management panel with powerful controls.

​
Accessing the Management Panel

1

Find the Raid ID

Every raid has a unique ID shown at the bottom of the signup embed:
Raid ID: `ABC123`
Created by @YourName
Copy this ID to use in management commands.
2

Open the panel

Run the /raid command with the Raid ID:
/raid raid_id:ABC123
This opens an ephemeral (private) management panel visible only to you.
3

Use the controls

The panel shows:
  • Current raid status (Open/Closed)
  • Raid type and name
  • Jump link to the signup message
  • Action buttons for management tasks
The /raid command requires the Manage Server permission.

​
Management Actions

​
Close Signup

Closing a raid:
  • Removes all reaction emojis
  • Adds “Signups Closed” to the description
  • Adds a status field showing who closed it and when
  • Records participation statistics for all signed-up players
  • Archives the discussion thread (if enabled)
  • Prevents new signups
Click the Close button in the management panel.The button is disabled if the raid is already closed.
Closing a raid records participation stats. Reopening and closing again will use delta tracking to only update stats for players who were added or removed between the two closures.

​
Reopen Signup

Reopening a raid:
  • Restores all reaction emojis
  • Removes “Signups Closed” from the description
  • Updates the status field to show who reopened it
  • Allows new signups again
  • Resets reminder flags
1

Click the Reopen button

In the management panel, click Reopen.This button is only enabled when the raid is closed.
2

Reactions restored

The bot automatically re-adds all necessary reaction emojis based on the raid type:
  • Regular raids: Role emojis (⚔️, 🛡️, etc.)
  • Museum: ✅
  • Key/Challenge: Team numbers (1️⃣, 2️⃣, 3️⃣, 4️⃣)

​
Delete Raid

Deleting a raid:
  • Permanently removes the signup message
  • Removes the raid from the active raids list
  • Cannot be undone
Deletion is permanent! Make sure you want to delete before clicking.
Click "Delete" → Raid message deleted → Raid data removed

​
Change Time

Update the raid’s scheduled time:
1

Click Change Time

In the management panel, click Change Time.
2

Enter new time

A modal appears asking for the new date/time. Use the same natural language formats as creation:
  • tomorrow 8pm
  • friday 7pm EST
  • 2026-03-20 19:00
  • Unix timestamp
3

Time updated

The raid embed is updated with the new time. The bot also:
  • Resets creator and participant reminder flags
  • Updates the embed timestamp
  • Logs the change to the audit channel
Changing the time uses the same chrono-node parser as raid creation, respecting your server’s configured timezone.

​
Change Length

For regular raids (not museum, key, or challenge), you can change the raid length:
1

Click Change Length

In the management panel, click Change Length.
This button is disabled for museum, key boss, and challenge mode signups.
2

Select new length

Choose between:
  • 1.5 hours
  • 3 hours
3

Length updated

The raid embed updates to show the new length badge:
`3 HOUR KEY`

​
Mark No-Show

After a raid is closed, you can mark players who didn’t show up:
1

Click Mark No-Show

In the management panel (with a closed raid), click Mark No-Show (❌).
This button is only enabled when the raid is closed.
2

Select users

A user select menu appears. Choose one or more users who were signed up but didn’t attend.You can select up to 25 users at once.
3

No-show recorded

The bot:
  • Increments the no-show count for each user
  • Shows a confirmation message
  • Logs the action to the audit channel
No-show tracking is permanent and can be used for guild management decisions.
Only mark users as no-shows if they confirmed attendance but didn’t show up. Don’t mark users who properly removed their signup or gave notice.

​
Find Substitute

For regular raids with role-based signups, you can find substitute candidates:
1

Click Find Sub

In the management panel, click Find Sub (🔍).
This feature is only available for regular raids with roles, not museum or team-based signups.
2

Select the role

Choose which role you need a substitute for from the dropdown menu.The menu shows all roles in the raid (Hitter, Jade, Support, etc.).
3

View recommendations

The bot analyzes participation data and shows the top 5 candidates based on:
  • Role experience: Number of times they’ve played this role
  • Total raids: Overall raid participation
  • Availability: If they marked themselves available at the raid time (✅)
  • Recency: Activity in the last 2 weeks
Example output:
🔍 Substitute Candidates for Storm Hitter

1. @PlayerOne — 15x Storm Hitter, 43 total raids ✅ available
2. @PlayerTwo — 12x Storm Hitter, 38 total raids
3. @PlayerThree — 8x Storm Hitter, 25 total raids ✅ available
4

Contact candidates

Reach out to the top candidates to see if they can fill in!
The substitute finder prioritizes players who have marked themselves as available for that specific time using the /available command.

​
Duplicate Raid

Create a copy of an existing raid with a new time:
1

Click Duplicate

In the management panel, click Duplicate (📋).
2

Enter new time

A modal appears asking for the date/time of the duplicate raid.Use natural language or Unix timestamps:
  • next friday 7pm
  • two weeks from now at 8pm
3

Choose roster option

For regular raids, you’ll be asked:Copy Roster - Duplicates the current signups (preserves who signed up)Start Empty - Creates empty slots (fresh signup)
Museum, key boss, and challenge mode raids always start empty.
4

Duplicate created

A new raid is created with:
  • Same type and configuration
  • New Raid ID
  • New timestamp
  • Same length/strategy (if applicable)
  • Copied or empty roster based on your choice
  • Fresh reactions added
  • New discussion thread (if enabled)
You run a weekly Dragonspyre raid every Saturday at 7pm.

1. After this week's raid closes
2. Click "Duplicate"
3. Enter "next saturday 7pm"
4. Choose "Start Empty"
5. New signup posted for next week!

​
Audit Logging

All management actions are logged to the audit channel (if configured): 
Raid Closed
By: @Manager
Raid ID: ABC123
Message: [Jump Link]

​
Best Practices

Close raids soon after they finish to:
  • Record accurate participation stats
  • Clear the active raids list
  • Archive discussion threads
  • Update bot presence
If you forget, the bot will auto-close based on configured settings.
If someone drops out last minute:
  1. Try Find Sub to identify replacements
  2. Contact top candidates
  3. Only cancel if no substitutes available
Only mark no-shows for players who:
  • Confirmed they would attend
  • Didn’t show up without notice
  • Didn’t remove their signup
This data helps guild leaders identify reliability issues.
For weekly or recurring raids:
  • Run the raid
  • Close it to record stats
  • Duplicate for next week with empty roster
  • Keeps the same configuration without manual setup

​
Next Steps

Time Parsing

Learn about natural language time parsing

Polls

Use polls to find optimal raid times

Build docs developers (and LLMs) love

Get started for freeTalk to us