Events supply context for matches: prize pools, LAN/online status, prize distribution per team, and qualified event chains. This page documents each field the model reads from theDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/ValveSoftware/counter-strike_regional_standings/llms.txt
Use this file to discover all available pages before exploring further.
events array in matchdata.json.
Event object fields
Each entry in the top-levelevents array describes a single tournament or league.
Unique numeric identifier for the event. Matches reference this value via their
eventId field.Display name of the event. The model checks this value for the substring
"showmatch" (case-insensitive) and excludes all matches from events whose name matches.Total prize pool as a dollar-formatted string, e.g.,
"$250,000". The model strips the $ and commas and converts it to a number.Prize pools are capped at 1,000,000.
Whether this event was played on LAN. LAN status influences the seeding modifier calculation for teams.
Whether the event has concluded. Matches from events where
finished is false are excluded from ranking calculations because final prize distribution is unknown.Array of per-team prize entries. Each entry records a team’s placement, prize money, and any events the placement qualified them for. See prizeDistribution entry fields below.
prizeDistribution entry fields
Each object in theprizeDistribution array represents one team’s result at the event.
The team receiving this prize entry. Matches the
team1Id or team2Id values on match objects that belong to this event.The team’s final finishing position at the event (e.g.,
1, 3, "5-8").Prize money awarded to the team, in USD.
Additional club share amount in USD. The model adds
clubShare to prize when computing the team’s total earnings from this event.Whether the prize was shared with other teams (e.g., in a joint placement).
Array of event IDs that this placement qualified the team to attend. Used by the model to chain prize pools across connected events.
Qualified event chaining
When a team wins or places highly at event A and that result qualifies them for event B, the model adds a portion of event B’s prize pool to event A’s value. This reflects the full competitive significance of the earlier result. The added value follows a halving rule per chain link:- One qualifying hop: event A’s prize pool += 50% of event B’s pool
- Two hops (A → B → C): event A’s pool += 25% of event C’s pool
finished === true) contribute to this chain. If a qualified event is still in progress, its prize pool is not added.
Certain high-value events — specifically RMR events and Majors — are explicitly included in the model’s
__highValueEvents list regardless of other eligibility rules. Their event IDs are hardcoded in data_loader.js to ensure they always contribute their full weight to the seeding modifier calculation.