`/config`

Guild configuration command.

Only an Organizer or a server admin can use it.

If you run /config with no options, the bot returns the current guild configuration.

Base Guild Config

`regions`

Comma-separated enabled regions.

Example:

NA,EU,OCE

Input is forgiving: lowercase works (na, eu), and stray spaces and trailing commas are ignored.

`max-roster-size`

Maximum allowed roster size for teams in this guild. Whole number between 1 and 10 (default 10).

Matchmaking Config

These values live inside the guild's matchmaking namespace and are unique per guild.

`matchmaking-max-matches`

Maximum number of scheduled matches a team can receive in a week.

`matchmaking-elo-floor`

Minimum allowed ELO difference for a generated matchup.

`matchmaking-elo-ceiling`

Maximum allowed ELO difference for a generated matchup.

`matchmaking-channel`

Text channel where generated weekly schedules are posted.

Optional Organizer-side channel for schedule controls. When set, published schedules post two copies: a clean, button-free embed in matchmaking-channel for players, and a mirror in this channel carrying the Report result / Edit schedule buttons. Results and edits made on the mirror update the public copy automatically (and vice versa — results from /report-match update both).

When not set, the buttons live directly on the public message. To go back to that single-message mode, set this option to the same channel as matchmaking-channel.

`matchmaking-auto`

Enable or disable automatic weekly schedule generation (default: enabled). With this off, schedules are only created via /schedule generate or the /schedule draft review flow.

`matchmaking-gen-day`

Day of week when automatic schedule generation runs.

`matchmaking-gen-hour-utc`

UTC hour for automatic generation.

`matchmaking-gen-minute-utc`

UTC minute for automatic generation.

Per-region slot times (which nightly times each region plays, and how many slots) are configured on the web under Manage → League → Competition, not with /config.

Stat Tracking Config

Settings for the in-game collector and player stats. See Stat Tracking for the full picture.

`min-team-size`

Smallest match format the collector records, per side: 1 = 1v1 … 8 = 8v8 (default 3 = 3v3). Games with fewer than size × 2 players on teams aren't recorded — this keeps post-pug duels and warmups out of the stats, and applies to every match including a ref's .start.

`stats-channel`

Channel receiving live stat events (tracking started, round end, map end, tracking finished), each with 🗑 Void / ✅ Approve buttons.

`stats-approval`

manual (default): tracked stat matches are pending and count toward nothing until an organizer approves them. auto: they count immediately and organizers void the occasional bad one.

`ref-role`

Role allowed to use the in-game ref commands. Must be a specific role — @everyone is rejected, since it would make every linked player a ref.

`series-format`

League series length used by the automatic result arbiter: Best of 1 / 3 / 5 / 7 (default Best of 5, first to 3 maps).

`min-rating-rounds`

Rounds a player needs in a bucket before they receive a rating or leaderboard rank (whole number 1–1000; default 50). Until then their profile shows "Stats are tracking — rating pending" with a progress bar toward the threshold — see Web Profiles.

`stats-leaderboard-channel`

Channel holding the persistent per-bucket stat leaderboard embeds (see /stats leaderboard).

`stats-leaderboard-buckets`

Which buckets get their own embed there: a comma-separated subset of competitive,casual,overall, or all / none (default competitive,overall).

`team-leaderboard-channel`

Channel holding the persistent team elo leaderboard.

The leaderboard posts also have on/off switches, and tournament and prediction announcements can be routed to dedicated channels — those live on the web under Manage → Discord → Channels, not in /config. See Shouts.

Example

/config matchmaking-max-matches:1 matchmaking-elo-floor:0 matchmaking-elo-ceiling:250 matchmaking-days:tuesday,thursday,friday matchmaking-channel:#scores matchmaking-gen-day:monday matchmaking-gen-hour-utc:18 matchmaking-gen-minute-utc:0

The automatic scheduler is UTC-based. If the bot is offline at the configured time, it catches up as soon as it is back online later that week — a restart can no longer skip a week. Automatic schedules are only generated once a matchmaking-channel has been configured.