Scoring & Standings

How wins translate into rank, and how match outcomes are recorded and confirmed.

Scoring & standings

How wins translate into rank.

Scoring mode

Field: scoringMode — ELO | FLAT_POINTS | WIN_LOSS

  • ELO — rating system, K-factor based on match volume; rewards beating stronger opponents more.
  • FLAT_POINTS — fixed points per win/loss/draw (configured with the fields below).
  • WIN_LOSS — pure win/loss tally, no rating.

Points per win

Field: pointsPerWin — integer

Only used when scoring mode is FLAT_POINTS. Default 3.

Points per loss

Field: pointsPerLoss — integer

Only used when scoring mode is FLAT_POINTS. Default 0. Set negative to penalize losses.

Points per draw

Field: pointsPerDraw — integer

Only used when scoring mode is FLAT_POINTS. Default 1.

ELO tiers

Field: eloTiers — array of

Custom rank tiers (e.g. Bronze 0+, Silver 1000+, Gold 1300+). Only meaningful for ELO scoring. Empty list disables tier display; null leaves it unchanged.

Standings columns

Field: standingsColumns — string[] (optional)

Override which columns the standings table shows. null = use the per-scoring-mode default (e.g. ELO mode shows Rating; FLAT_POINTS shows Points).

Show rating publicly

Field: showRatingPublicly — boolean

When false, the public standings page redacts ELO from non-org-members. Tier and rank stay visible — a common "hide MMR but show rank" pattern.

Match results

How match outcomes are recorded and confirmed.

Result mode

Field: resultMode — DUAL_SUBMIT | WINNER_REPORTS | ADMIN_ONLY

  • DUAL_SUBMIT — both teams submit a result; agreement auto-confirms, disagreement triggers a dispute.
  • WINNER_REPORTS — only the winning team reports; the loser has the auto-confirm window to dispute.
  • ADMIN_ONLY — only org staff can record results.

Auto-confirm hours

Field: autoConfirmHours — integer (hours)

Only used by WINNER_REPORTS mode. After the winner reports, the loser has this many hours to dispute before the result auto-confirms.