
What the 7.40 patch changes about how a mid-lane reads the map
Three changes matter, two are window dressing, and one will quietly decide the next three weeks of Tour matches. The desk's priority list.
Read the note →The games desk is the editorial layer that turns a competitive game into a publication the editorial newsroom can read across patches. Eight games, eight patch cycles, eight editorial coverage weights. The games desk pairs every game with the patch cycle, the meta read, and the broadcast schedule.
Three working documents. The game profile is the published record — the game name, the publisher, the patch cycle, the meta read, the broadcast partner, and the editorial coverage weight. The patch note is the published patch analysis — the patch version, the release date, the editorial read, the priority changes, and the meta impact. The meta read is the published meta analysis — the meta shifts, the role impact, the team impact, and the broadcast implications.
The games desk refreshes the game profile daily, the patch note within four hours of every patch release, and the meta read within two hours of every meta shift. The games desk is the working document the editorial newsroom reads when it needs to know what game is in play, what patch is current, and what meta is dominant.
The desk reads a game the way the casters read a patch. The game profile is the broadcast's editorial record — the game name, the publisher, the patch cycle, the meta read. The patch note is the broadcast's editorial analysis — the patch version, the release date, the editorial read, the priority changes. The meta read is the broadcast's editorial impact — the meta shifts, the role impact, the team impact, the broadcast implications.
The desk's editorial read pairs the game profile with the patch note and the meta read. The game profile is the editorial record. The patch note is the editorial analysis. The meta read is the editorial impact. The desk's read is the editorial layer the broadcaster can't carry — the game, the patch, the meta.
The desk covers eight competitive games. League of Legends is the flagship — fourteen-day patch cycle, sixteen-team regional qualifier path, the deepest editorial coverage weight. Dota 2 is the second flagship — irregular patch cycle, the DPC Tour points path, the second-deepest editorial coverage weight. Counter-Strike 2 is the third flagship — map pool rotations, the Major cycle, the third-deepest editorial coverage weight.
Valorant is the strong coverage — six-week agent update cycle, the Champions Tour regional path, the fourth-deepest editorial coverage weight. Rocket League is the standard coverage — seasonal playlist changes, the RLCS regional path, the fifth editorial coverage weight. PUBG Mobile is the strong coverage — map rotations, the Global Open regional path, the sixth editorial coverage weight. The mobile esports circuit is the standard coverage — per-game patch cycle, the wildcard qualifier path, the seventh editorial coverage weight. The desk's editorial read pairs every game with the patch cycle, the meta read, and the broadcast schedule.
The patch note is the published patch analysis of the game. The desk tracks five layers: the patch version, the release date, the editorial read, the priority changes, and the meta impact. The patch version is the published version number. The release date is the published release date. The editorial read is the published editorial analysis. The priority changes are the published priority changes. The meta impact is the published meta impact.
The desk's patch note read pairs each layer with the patch version, the release date, the editorial read, the priority changes, and the meta impact. The patch note is the editorial analysis the broadcaster can't carry — the patch version, the release date, the editorial read, the priority changes, the meta impact. The desk refreshes the patch note within four hours of every patch release, with the verification chain documented in the patch footer.
The meta read is the published meta analysis of the game. The desk tracks four layers: the meta shifts, the role impact, the team impact, and the broadcast implications. The meta shifts are the published meta shifts. The role impact is the published role impact. The team impact is the published team impact. The broadcast implications are the published broadcast implications.
The desk's meta read pairs each layer with the meta shifts, the role impact, the team impact, and the broadcast implications. The meta read is the editorial impact the broadcaster can't carry — the meta shifts, the role impact, the team impact, the broadcast implications. The desk refreshes the meta read within two hours of every meta shift, with the verification chain documented in the meta footer.
Three working notes from the games desk. First, the game profile is the published record — read it before the broadcast, then follow it during the broadcast for the patch coverage. Second, the patch note is the editorial analysis — read it before the broadcast, then use it to plan the next week's editorial window. Third, the meta read is the editorial impact — read it during the broadcast, then replay it after the broadcast for the editorial recap.
The games desk is open to all readers. The desk does not require a subscription, does not publish betting lines, and does not promote a particular game's meta. The editorial read is published with the verification chain documented in the game footer, and the source dossier is available on request through the contact desk.
The games desk's editorial coverage weight table. Patch cadence, roster signal, and the editorial weight the desk assigns to each game.
| Game | Editorial stage | Patch cadence | Roster signal | Coverage weight |
|---|---|---|---|---|
| League of Legends | GroupSix regions, 16 teams each | 14-day cycle | High · 1,408 players | ★★★ Flagship |
| Dota 2 | TourTour + DPC + Major | Irregular · 7.40 series | High · 720 players | ★★★ Flagship |
| Counter-Strike 2 | MajorValve Major + ESL | Map pool rotations | Very high · 612 players | ★★★ Flagship |
| Valorant | ChampionsChampions Tour regional | 6-week agent updates | High · 410 players | ★★ Strong |
| Rocket League | RCSRLCS + regional opens | Seasonal playlist | Medium · 230 players | ★ Standard |
| PUBG Mobile | GlobalPro League + regional | Map rotations | High · 530 players | ★★ Strong |
| Mobile esports | WildcardWildcard qualifier | Per-game cycle | Medium · 600 players | ★ Standard |
| Eastern Division Cup | CupMulti-game cup | Per-game cycle | Medium · 280 players | ★ Standard |
Three working notes from the games desk for the week ahead. The game profile, the patch note, and the meta read — together they read the game the way the editor reads the script.

Three changes matter, two are window dressing, and one will quietly decide the next three weeks of Tour matches. The desk's priority list.
Read the note →
Three priority shifts and the rosters that benefit. The desk's working note pairs every patch release with the next week's qualifier draws.
Read the guide →The editorial desk reads three working documents on every page the desk publishes. The published record is the editorial layer the broadcast can't carry — the source, the verification date, the verification result, and the editorial context. The editorial analysis is the editorial timing the broadcast can't carry — the editorial read, the editorial verification chain, the editorial context. The editorial coverage is the editorial follow-up the broadcast can't carry — the editorial window, the editorial cadence, the editorial follow-up.
The editorial read pairs the published record with the editorial analysis and the editorial coverage. The editorial read is the editorial layer the broadcast can't carry, and the editorial verification chain is published with the page footer. The editorial read is built to be accessible to readers aged 18 and over, and to readers using the editorial desk's accessibility layer.
The broadcast studio is the editorial layer the broadcast can't carry. The studio carries the editorial read, the editorial verification chain, and the editorial context. The editorial read is published with the editorial verification chain, and the editorial verification chain is published with the page footer.
The verification chain is the editorial layer the operator's marketing channel can't carry. The chain documents the source, the verification date, the verification result, and the editorial context. The chain is published with the page footer, and the editorial verification chain is available on request through the contact desk.
The editorial verification chain is documented across four layers. The source layer identifies the official channel the editorial desk cross-checked against — typically the operator's official documentation, the league's official channel, the team's official social media, or the broadcast partner's official bracket. The verification date layer identifies when the editorial desk cross-checked the source. The verification result layer identifies the editorial desk's conclusion — confirmed, refuted, or unresolved. The editorial context layer identifies the editorial reasoning behind the result.
The editorial verification chain is built to be transparent. The chain is published with the page footer, and the chair is available on request through the contact desk. The chain is built to be accessible to readers aged 18 and over, and to readers using the editorial desk's accessibility layer.
First, the published record — the source, the verification date, the verification result, and the editorial context. Second, the editorial analysis — the editorial read, the editorial verification chain, the editorial context. Third, the editorial coverage — the editorial window, the editorial cadence, the editorial follow-up. The three documents are the editorial layer the broadcast can't carry, and the editorial read is published with the editorial verification chain.
The editorial desk reads the broadcast the way the casters read the script. The desk reads the editorial layer, the editorial verification chain, and the editorial context. The editorial read is the editorial layer the broadcast can't carry, and the editorial verification chain is published with the page footer.
The desk verifies every patch note against the official patch release, the developer's official patch notes, and at least one independent source. The verification chain is published with the patch footer.
The desk covers eight competitive games — League of Legends, Dota 2, Counter-Strike 2, Valorant, Rocket League, PUBG Mobile, the mobile esports circuit, and the Eastern Division Cup. Each game has its own patch cycle, its own broadcast partner, and its own editorial coverage weight.
The desk refreshes the patch note within four hours of every patch release. The refresh windows are tied to the official patch release cadence. The verification chain is published with each refresh.
The meta read is the editorial layer the broadcast can't carry. The desk reads the meta shifts, the role impact, the team impact, and the broadcast implications. The desk refreshes the meta read within two hours of every meta shift.
The desk does not publish betting lines, fantasy-pick cards, or fabricated statistics. The desk does not promote a particular game's meta, and does not accept story placement from operators in exchange for editorial coverage.