Brief 03 / Competitive trends
Competition in context
A pattern does not travel unchanged between patches, opponents and formats. Define the environment before deciding what the pattern means.
Method brief / Not a current meta report
Competitive trends are attractive because they compress many matches into a simple statement. A team is rotating earlier; an agent is appearing more often; a particular opening is returning. But compression removes conditions. The analyst's job is to restore the conditions that determine whether a pattern is meaningful and whether it belongs in the next review. AI can organise a large corpus, but it cannot rescue a comparison whose underlying sample answers the wrong question.
Define the unit and the opportunity
Begin by stating what counts as an observation. Is it a match, a map, a round, a draft or a decision opportunity? A strategy used in several rounds is not necessarily evidence from independent situations. The same opponent, preparation and match conditions may connect them. Keep those groupings visible instead of treating every event as a fresh experiment.
Next define the denominator. An increase in objective contests means something different if the number of available contests also changes. A selection rate should describe the eligible pool and the selection rules. If those opportunities cannot be reconstructed, report a count with its limitations rather than presenting a precise-looking rate that implies more than the data supports.
Keep the patch boundary visible
Balance changes can alter the value of resources, the pace of engagements and the viability of familiar routes. Map geometry and tournament map pools may change the available decision set even when a player's role remains the same. Record the game version attached to the replay where it is available. Do not assume that the date of a broadcast proves the version used in competition.
Use official sources to establish rules and changes. Riot Games publishes information for League of Legends and VALORANT; Valve maintains official channels for Counter-Strike 2 and Dota 2; Blizzard publishes Overwatch 2 updates. Those sources establish the environment, not the strategic consequences. A patch note is evidence that a parameter changed, not proof that a particular team behaviour was caused by it.
Account for the tournament environment
A best-of series creates different adaptation opportunities from a single-map encounter. Qualification rules, side selection, veto order and roster eligibility can influence the observed sample. Events associated with ESL, BLAST, the VALORANT Champions Tour or The International have their own rules and competitive structures. Consult the relevant event documentation instead of applying assumptions from a familiar tournament.
Public match databases such as HLTV, Liquipedia and Oracle's Elixir can be useful starting points for discovery and cross-checking where their coverage and terms permit. They are not interchangeable datasets. Inspect definitions, missing fields, corrections and licensing before analysis. A field with the same label may represent a different collection process or a different level of detail.
Test whether the trend survives comparison
Break an apparent shift into sensible groups: patch window, map, opponent tier, side or roster, depending on the question. If the pattern disappears when one group is removed, describe that dependence. It may reflect a real local adaptation rather than a broad competitive trend. Small groups can be informative, but they do not justify broad certainty merely because the effect looks large.
| Check | Reason |
|---|---|
| Patch and map pool | The feasible options may have changed |
| Opponent composition | A response may target a specific style |
| Roster continuity | Roles and responsibilities may differ |
| Repeated series | Observations may share preparation and adaptation |
A model trained on earlier competition may retain relationships that no longer hold. Check performance on later, genuinely held-out data and examine the errors, not only an aggregate score. Time-aware evaluation reduces one source of leakage, but it does not eliminate shifts in measurement or access to information. State what the model has and has not been tested against.
Translate context into a review question
A useful trend note ends with a bounded implication. Instead of declaring a new universal strategy, identify the situations worth inspecting in your own replays. Ask whether the same patch conditions, resources and opponent cues are present. Then test the interpretation through individual decisions and team responses.
Record the extraction date, source boundaries and known missing data. This page explains a method rather than reporting a live competitive meta. Any current claim needs a fresh, attributable evidence trail. When the environment changes, the responsible next step is not to defend an old chart; it is to ask whether the original comparison still exists.
