A team’s name can stay the same while its players, game version and competitive conditions change. Treat those changes as context for results rather than as reasons to invent adjustments. This guide explains how to keep patch, roster and eligibility evidence separate when following Dota 2, CS2 and League of Legends.
Separate a public update from an event’s game version
Valve maintains the Dota 2 update archive and publishes Counter-Strike update announcements. These establish that a public update was announced; they do not, on their own, prove which version a tournament used. A competition may publish its own patch or configuration notice. Record that event notice when it exists. If the organiser has not stated the version in a source you can verify, leave the field unknown rather than copying the newest version from your own game client. The date of a public download and the version used in a particular official match are different facts.
Treat a roster as a dated group of people
Keep player identities, team identity and the period of participation in separate fields. A substitute can change the line-up for one series without changing the team’s branding. Likewise, a rebrand can change the public name without establishing that every player changed. Use the organiser’s roster record and official team announcement together, noting any disagreement instead of resolving it by guesswork. Avoid transferring a player’s entire earlier record to a new line-up as if nothing changed. When discussing team form, state whether your sample spans a roster change and identify the source that dates it.
What each primary source can establish
| Primary source | What it establishes | What still needs event evidence |
|---|---|---|
| Valve public update archive | A publisher update announcement | Tournament adoption and exact match configuration |
| Valve Major rulebook | Published roster and invitation provisions | Edition-specific accepted participants and decisions |
| Riot Competitive Operations library | Official competition rule documents | The document and revision applying to the named event |
Use the Riot Competitive Operations library to locate the relevant rule document, not merely a page with a similar competition name. Save its edition and revision date. The Valve Major rulebook also shows why roster and invitation questions belong to formal rules rather than to an informal ranking screenshot. A rule is a framework; an individual eligibility decision still requires its own authoritative notice.
Compare periods without pretending to isolate causation
Imagine a fictional team winning four of six series before a roster change and two of four afterward. The first observed rate is about 66.7%; the second is 50%. These ten series do not establish that the roster change caused a decline. Opponents, format, event stage, game version and sample size may differ. Present the split as a description and list the relevant changes. Do not add an invented correction factor for a new patch or substitute. A transparent table that says what changed is more useful than a precise-looking score with no reproducible method behind it.
Keep eligibility decisions separate from performance
A team can have a strong match record and still face an eligibility question. Conversely, an eligible roster is not guaranteed a competitive result. For your archive, distinguish invited, accepted, registered, substituted and officially withdrawn states only when the organiser supplies evidence. Do not present a rumour about a suspension or identity as a confirmed finding. If a result is awarded or amended through a formal decision, record that status and the decision reference without inventing unplayed statistics. Keep personal information limited to what the official public record actually requires; private account details are not necessary for a useful sporting dataset.
Checklist for a contextual comparison
- Record the event and stage, then save the applicable rule document and its date. A general repository overview is not a substitute for an edition-specific notice.
- Store the verified game version and roster for the period being analysed. Mark unknown values explicitly and document substitutions or renamed teams.
- Split a comparison where meaningful conditions change, but explain the smaller resulting samples. Keep series counts, opponents and format visible beside any percentage.
- For an administrative decision, retain the official reference and status. Correct the archive transparently and avoid speculating about a player or team beyond the evidence.
Frequently asked questions
Can I infer the tournament patch from the latest client update?
No. The public update archive and a tournament’s version decision are separate sources. Use an event-specific notice or leave the version unconfirmed.
Does a changed win rate prove a roster change worked?
No. It describes the selected results. Opponents, format, patch and sample size can also differ, so the comparison cannot isolate the cause by itself.
Should eligibility rumours be included in a match record?
Do not present rumours as facts. Use the organiser’s official decision when one exists, distinguish it from performance data and preserve the dated source for any correction.
Sources and verification
- Dota 2 update archive — Valve — 2026-10-23
- Season 5, Armory, and More — Valve — 2026-10-23
- Counter-Strike Major supplemental rulebook — Valve — 2026-10-23
- Riot Games Competitive Operations rule library — Riot Games — 2026-10-23