/stats command

Statistics and analytics — raid, guild, status, attendance, suggest

5 subcommands available · Per-raid and guild-wide analytics · Player attendance history and reliability scores · Composition analysis with optimization suggestions

Syntax

/stats <subcommand> [options]

Parameters

raid optional

View sign-up, opt-out, and late counts for a specific raid

Format: raid_id:<id>

guild optional

View guild-wide attendance statistics over a time period (default: month)

Format: [period:week|month|all] [team:<name>]

status optional

Dashboard of the next 7 upcoming open raids with roster counts, optionally scoped to one team

Format: [team:<name>]

attendance optional

View a player's attendance history, reliability score, and role distribution

Format: player:<@user> [period:month|quarter|all] [team:<name>]

suggest optional

Analyze raid composition and get role gap warnings, swap suggestions, and success likelihood

Format: raid_id:<id>

Examples

Check a player's reliability

/stats attendance player:@Healbot period:quarter

Shows Healbot's attendance rate, opt-out patterns, and role distribution over the last 90 days

Guild overview

/stats guild period:month

Shows total raids, average attendance, and top attendees for the last 30 days

Composition check

/stats suggest raid_id:abc123

Analyzes the raid's tank/healer/DPS balance and suggests swaps to fill gaps

Subcommands

Each subcommand focuses on a different analytics view.

  • raid — per-raid breakdown of attending, opted-out, and late counts
  • guild — aggregate stats across all raids in a time window
  • status — quick dashboard of upcoming raids and their fill status
  • attendance — individual player history with reliability scoring
  • suggest — composition analysis with role gap detection and swap recommendations

Time Periods

Several subcommands accept a period option to scope the analysis.

  • week — last 7 days (guild only)
  • month — last 30 days (default for guild and attendance)
  • quarter — last 90 days (attendance only)
  • all — all recorded history

Permissions

  • Discord ManageEvents permission required

Troubleshooting

  • If stats show zero data, ensure raids have been created and members have responded.
  • The status dashboard only shows open raids with future dates — closed or past raids are excluded.
  • Attendance data is based on final roster state — opt-outs that later re-join are counted as attending.
  • Suggest works best when raids have a roles composition set (e.g., '2T 4H 14D' on creation).