/availability

The /availability command allows members to record their timezone, preferred days/times, and roles, helping raid leaders schedule events when the most people can participate.

Command Signature

/availability <set|view|summary|optimal|check|clear|post-button|list> [...options]

Subcommands

Set your availability (opens a form).

/availability set [user:@PlayerName]

user

User to set availability for (Admin only, defaults to you)

Opens a modal with fields:Timezone

Format: EST, PST, UTC-5, GMT+1, America/New_York
Example: EST, America/Chicago, UTC-5

Preferred Days/Times

Format: Natural language time windows
Examples:
- Mon-Fri 7-10pm
- Weekends 6-11pm
- Sat 2pm-6pm, Sun afternoons
- Weekdays evenings
- Everyday after 5pm

Preferred Roles

Example: Vanguard, Support, Surge, Gates, Flex

Notes

Any other scheduling constraints or preferences

Result:

Bot parses your time windows and confirms
Shows parsed windows in your timezone
If parsing fails, notifies admins via audit log

View availability for a user.

/availability view [user:@PlayerName]

user

User to view (defaults to you)

Output includes:

Timezone
Preferred days (raw input)
Preferred roles
Notes
Parsed time windows (in your timezone)

Example:

PlayerName's Availability

Timezone: America/New_York
Preferred Days: Mon-Fri 7-10pm, Weekends 6-11pm
Preferred Roles: Storm, Support
Notes: Can't do early mornings

Parsed Time Windows (EST):
Monday 7:00 PM-10:00 PM
Tuesday 7:00 PM-10:00 PM
...
Saturday 6:00 PM-11:00 PM
Sunday 6:00 PM-11:00 PM

View server-wide availability breakdown.

/availability summary

Output includes:

Total members with availability set
Heatmap of most popular time slots
Top 5 optimal raid times
Times shown in your timezone

Example:

Server Availability Summary

24 members have recorded their availability.
Times shown in EST

Hottest Time Slots:
Day       Time      Users
─────────────────────────
Saturday  7:00 PM   ████████████ 18
Sunday    3:00 PM   ██████████ 15
Friday    8:00 PM   ████████ 12
...

Best Times for Raids:
1. Saturday 7:00 PM — 18 available
2. Sunday 3:00 PM — 15 available
3. Friday 8:00 PM — 12 available

Find time slots when the most users are available.

/availability optimal [min_users:5]

min_users

integer

Minimum number of available users (1-100)

Output includes:

All time slots meeting the minimum
Grouped by day of week
Sorted by availability count
Times shown in your timezone

Example:

Optimal Times (5+ users)
Times shown in EST

Saturday:
7:00 PM (18 users), 6:00 PM (16 users), 8:00 PM (14 users)

Sunday:
3:00 PM (15 users), 2:00 PM (12 users), 4:00 PM (10 users)

Friday:
8:00 PM (12 users), 7:00 PM (9 users)

Based on 24 member availability records

Check who is available at a specific time.

/availability check time:"Saturday 7pm"

time

string

required

Time to check. Formats:

Natural language: “Saturday 7pm”, “tomorrow 8pm”
Unix timestamp: 1234567890

Output includes:

Formatted time
List of available members (up to 25 shown)
Total count

Example:

Availability Check

Time: Saturday, Mar 2, 7:00 PM EST

18 members available:
@Player1, @Player2, @Player3, @Player4, @Player5,
@Player6, @Player7, @Player8, @Player9, @Player10,
...

Based on recorded availability windows

Clear your availability data.

/availability clear [user:@PlayerName]

user

User to clear availability for (Admin only)

Permanently removes availability data for the user.

Post a persistent “Set Availability” button (Admin only).

/availability post-button

Creates a message in the current channel with:

Informative embed about availability
“Set Availability” button
Clicking the button opens the availability form
Useful for onboarding channels

View all members who have set their availability.

/availability list

Output includes:

Count of members with availability
List showing:
- Display name
- Timezone
- Days preview (truncated)
- Parse status (✓ or ⚠️)
Members with parse failures shown first

Example:

Availability List

24 members have set their availability.
⚠️ 2 with parse issues (check their input)

Members:
⚠️ Player1 (EST)
   weekdays nights and stuff
✓ Player2 (PST)
   Mon-Fri 7-10pm
✓ Player3 (EST)
   Weekends 6-11pm
...

Parse Failures:
Members marked with ⚠️ have entered availability
that could not be parsed into time windows.
Use /availability set user:@user to fix their input.

Time Parsing

The bot attempts to parse natural language into structured time windows: Supported formats:

Mon-Fri 7-10pm → Monday-Friday, 7:00 PM - 10:00 PM
Weekends 6-11pm → Saturday-Sunday, 6:00 PM - 11:00 PM
Weekdays evenings → Monday-Friday, 6:00 PM - 10:00 PM (heuristic)
Sat 2pm-6pm → Saturday, 2:00 PM - 6:00 PM
Everyday after 5pm → All days, 5:00 PM - 11:59 PM

Parse failures:

If the bot can’t parse your input, it saves it but marks it as unparsed
Admins are notified via audit log
You can fix it by running /availability set again

Timezone Handling

All time windows are stored in UTC and converted for display:

Input is converted from your timezone to UTC
Output is converted from UTC to viewer’s timezone
This ensures accurate cross-timezone availability

Integration with Other Commands

/raid - Find Sub:

When finding substitutes, the bot checks availability
Users available at raid time get priority in the ranking

/create - Recurring Raids:

Can use availability data to suggest optimal times

/stats - User Stats:

User stats show availability settings if configured

Examples

/availability set
→ Timezone: EST
→ Days: Mon-Fri 7-10pm, Weekends 6-11pm
→ Roles: Storm, Support, Flex
→ Notes: Can't do early mornings

/stats - View user availability in stats
/raid - Find Sub uses availability
/poll - Create time slot polls

Command Reference

Command Signature

Subcommands

Time Parsing

Timezone Handling

Integration with Other Commands

Examples

Build docs developers (and LLMs) love

Command Reference

​Command Signature

​Subcommands

​Time Parsing

​Timezone Handling

​Integration with Other Commands

​Examples

​Related Commands

Build docs developers (and LLMs) love

Command Signature

Subcommands

Time Parsing

Timezone Handling

Integration with Other Commands

Examples

Related Commands