Skip to main content

​
Museum Signups

Museum signups are streamlined events designed for activities that don’t require specific roles — like museum runs, housing tours, or casual group content.

​
What Makes Museum Signups Different?

Unlike regular raids with specific roles (Vanguard, Support, etc.), museum signups have:

Single Reaction

One ✅ reaction for all players (no role selection needed)

12 Player Cap

Default maximum of 12 participants (configurable)

First-Come Basis

Players fill slots in order — no role balancing needed

Automatic Waitlist

Overflow users automatically added to waitlist

​
Creating a Museum Signup

You can create museum signups via the /create command or recurring schedules.

​
Via Create Command

1

Start creation

Run /create to open the interactive raid builder.
2

Select Museum

From the type dropdown, choose “Museum Signup” (marked with 🏛️ emoji).
3

Set time

Click “Set Time” and enter when the event occurs:
tomorrow 3pm
Saturday 2pm
next week 6pm
4

Create

Click “Create” to post the signup. The bot automatically adds the ✅ reaction.

​
Via Recurring Schedule

For weekly museum events: 
/recurring action:create
# Select: Museum Signup
# Schedule: Weekly on desired day/time
See Recurring Raids for detailed setup instructions.

​
Signup Embed Format

Museum signup messages look like this: 
Title: Museum Signup
Description: React with ✅ to reserve a slot. Max 12 players.

Date + Time: Saturday, March 15, 2026 at 2:00 PM EST

Signups (8/12):
  1. @PlayerOne
  2. @PlayerTwo
  3. @PlayerThree
  4. @PlayerFour
  5. @PlayerFive
  6. @PlayerSix
  7. @PlayerSeven
  8. @PlayerEight

Waitlist (2):
  1. @PlayerNine
  2. @PlayerTen

Raid ID: abc123
Created by @RaidLeader

​
How Players Sign Up

1

React with ✅

Click the ✅ reaction under the signup message.
2

Automatic assignment

If slots are available:
  • Player is added to the numbered list
  • Embed updates immediately
If full:
  • Player is added to the waitlist
  • Notified via DM they’re on standby
3

Remove reaction to cancel

Click ✅ again to remove your signup.
Players can only sign up once — they can’t be on both the main roster and waitlist simultaneously.

​
Waitlist System

The waitlist automatically manages overflow participants.

​
Automatic Promotion

When a main roster player drops: The first person on the waitlist is:
  1. Moved to the main roster
  2. Sent a DM notification
  3. Pinged in the raid thread (if enabled)

​
Waitlist Notifications

Promoted users receive a DM like: 
You've been promoted from the waitlist!

Event: Museum Signup
Time: Saturday, March 15 at 2:00 PM EST
Raid ID: abc123

[View Signup]

​
Managing Museum Signups

Use the standard raid management panel: 
/raid raid_id:abc123

​
Available Actions

Lock the signup — no new reactions accepted.Use this when:
  • Event is about to start
  • Roster is finalized
  • No longer accepting signups
Change Length and Find Sub are disabled for museum signups (they only apply to role-based raids).

​
Manual Roster Management

Admins can manually add/remove players using /raidsignup.

​
Add a Player

/raidsignup action:assign raid_id:abc123 user:@Player
Adds the user to the main roster (or waitlist if full).

​
Remove a Player

/raidsignup action:remove raid_id:abc123 user:@Player
Removes the user and promotes the next waitlisted player.

​
Move to Waitlist

/raidsignup action:waitlist raid_id:abc123 user:@Player
Moves a main roster player to the waitlist (frees a slot for promotion).
Manual changes trigger the same waitlist promotion logic as player reactions. Always check the embed after making changes.

​
Use Cases

Museum Tours

Coordinate group visits to in-game museums or exhibits.

Housing Tours

Organize house visits with player count limits.

Social Events

Casual meetups, fashion shows, or competitions.

Non-Combat Content

Any activity where specific roles aren’t needed.

​
Best Practices

Set realistic caps based on instance limits. The default 12 works for most content, but you can create custom templates with different limits.
Close signups 5-10 minutes before start to lock the roster and prevent last-second changes.
Enable threads in server settings so each museum event gets its own discussion thread for coordination.

​
Customizing Museum Capacity

The default 12-player cap can be modified via custom templates:
1

Contact server admin

Museum capacity is set when creating the template.
2

Create custom museum template

Your admin can create templates with different maxSlots values:
  • Small events: 4-8 players
  • Standard: 12 players
  • Large: 16-20 players
3

Use the custom template

Select it from /create or recurring raid setup.
Template customization requires server configuration access. See Templates for details.

​
Participation Tracking

Museum signups count toward user statistics:
  • Total raid count (/stats user)
  • Weekly participation (/stats weekly)
  • Monthly reports (/stats monthly)
  • Attendance rate calculations
  • No-show tracking (if recorded)
View stats: 
/stats user user:@Player
Museum events appear as “Museum” in the “Favorite Raid Type” field.

​
Differences from Regular Raids

FeatureMuseum SignupsRegular Raids
Role SelectionNo rolesMultiple roles (Vanguard, Support, etc.)
ReactionsSingle ✅One emoji per role
CapacityFixed total (default 12)Per-role slot counts
WaitlistSingle global listPer-role waitlists
Side AssignmentN/ASupported (Lemuria raids)
Find SubNot availableSmart role-based matching
Roster CopyNot supportedWorks with recurring raids

​
Troubleshooting

  • Check if raid is closed
  • Verify player has permission to add reactions in the channel
  • Try removing and re-adding reaction
  • Ensure the previous player’s reaction was fully removed
  • Check bot permissions (Manage Messages required)
  • Verify the user being promoted can receive DMs from the bot
  • Look at the very bottom of the signup embed
  • Format: Raid ID: abc123
  • Use this exact ID (case-sensitive) in commands

Build docs developers (and LLMs) love

Get started for freeTalk to us