Competition reference
Criteria
Section titled “Criteria”| Criteria | Ranks by | Queues |
|---|---|---|
MOST_GAMES_PLAYED |
Games played | one or more compatible queues |
MOST_WINS_PLAYER |
Wins | one or more compatible queues |
MOST_WINS_CHAMPION |
Wins on one catalog-valid champion | one or more compatible queues |
HIGHEST_WIN_RATE |
Win rate, above a minimum game count | one or more compatible queues |
HIGHEST_RANK |
Peak or combined normalized rank | solo, flex, and/or ranked 5s; Modern |
MOST_RANK_CLIMB |
Best or combined LP change | solo, flex, and/or ranked 5s; Modern |
HIGHEST_WIN_RATE takes a minimum game count, defaulting to 10. Rank-based
criteria take aggregation: "MAX" | "SUM". MAX uses the best selected rank
or largest complete ladder climb. SUM adds normalized ladder points or
complete per-ladder LP changes. A missing ladder is ignored; a player is omitted
only when no selected ladder has usable data.
Game variants
Section titled “Game variants”| Value | Eligible content |
|---|---|
MODERN | Modern champion catalog and every non-Classic queue |
CLASSIC | League Classic and Classic ARAM Mayhem, with the Jade champion catalog |
Classic competitions cannot use rank criteria. Changing variants clears the
selected champion and resets queues to ALL.
Competition queues
Section titled “Competition queues”| Value | Variant | Availability |
|---|---|---|
ALL | Selected competition variant | Currently live |
solo | Modern | Currently live |
flex | Modern | Currently live |
ranked 5s | Modern | Currently live |
clash | Modern | Currently live |
aram clash | Modern | Currently live |
aram | Modern | Currently live |
arurf | Modern | Limited-time; not currently live |
urf | Modern | Limited-time; not currently live |
quickplay | Modern | Currently live |
swiftplay | Modern | Currently live |
arena | Modern | Currently live |
classic | Classic | Currently live |
classic aram mayhem | Classic | Currently live |
brawl | Modern | Limited-time; not currently live |
aram mayhem | Modern | Currently live |
normal | Modern | Currently live |
draft pick | Modern | Currently live |
easy doom bots | Modern | Limited-time; not currently live |
normal doom bots | Modern | Limited-time; not currently live |
hard doom bots | Modern | Limited-time; not currently live |
custom | Modern | Currently live |
ALL is synthetic and mutually exclusive with concrete queues. It means all
queues in the selected game variant. Every other value comes directly from the
canonical lowercase QueueTypeSchema; RANKED_ANY no longer exists.
Visibility
Section titled “Visibility”| Value | Who participates |
|---|---|
OPEN | Marked as open to the server. Note that Scout currently has no self-service join action, so participants still have to be added by someone with the invite permission. |
INVITE_ONLY | Only people you invite are participants. |
SERVER_WIDE | Every tracked player in the server, automatically. |
Participant states
Section titled “Participant states”| Status | Meaning |
|---|---|
INVITED | Invited, has not joined yet. |
JOINED | Participating and accruing results. |
LEFT | Left the competition and stopped accruing. |
Window
Section titled “Window”A competition runs on either an explicit start and end date, or a League season.
Fixed values are interpreted in analysisTimezone: the start is local 00:00:00
and the end is the final local millisecond of the selected end date. The default
for a new builder-created competition is the browser’s IANA timezone; legacy
rows default to UTC.
Status — upcoming, running, finished — is derived from those dates rather than stored, so correcting a date immediately corrects the status.
Scheduled updates
Section titled “Scheduled updates”| Field | Default for legacy rows | New builder default |
|---|---|---|
scheduledUpdatesEnabled |
false |
true |
updateCronExpression |
0 0 * * * |
0 9 * * * |
scheduleTimezone |
UTC |
Browser IANA zone |
The cron must select exactly one minute and one hour and may fire at most once
per day. scheduleTimezone controls cron evaluation independently from
analysisTimezone, which controls competition-day boundaries and analysis.
Disabling updates clears nextScheduledUpdateAt; enabling an active competition
computes it immediately in the saved timezone.
Lifecycle
Section titled “Lifecycle”Scout checks competition starts and ends every 15 minutes. A declarative Temporal schedule runs a separate dispatcher every minute; stage-local Scout activity workers post leaderboard updates only for enabled, active, due competitions. Start and final announcements remain mandatory even when leaderboard updates are disabled. Failed update posts still advance the next fire.
Other fields
Section titled “Other fields”| Field | Notes |
|---|---|
| Title | Required; up to 100 characters |
| Description | Required; up to 500 characters |
| Announcement channel | Required; needs Send Messages and Attach Files |
| Max participants | Defaults to 100 for new competitions; existing caps stay unchanged |
| Game variant | MODERN by default; CLASSIC isolates Classic content |
| Analysis timezone | IANA zone for fixed-day and analysis boundaries |
| Initial player IDs | Unique guild-scoped tracked players; JOINED on create |
Initial entrants and server-wide enrollment require competitions:invite.
Enabled or customized schedules require competitions:schedule.