Game chapters — strategy context per title with editorial patch-watch

The games desk covers 15 active titles, organised into five chapters (FPS, MOBA, Battle Royale, Fighting, Racing). Each chapter has its own patch-watch cadence and a published editorial read of every major patch.

A patch is a balance log, a meta shift and a context document. The desk publishes all three. The balance log is reproduced verbatim from the publisher feed (Tier A); the meta shift is editorial read (Tier C); the context document is the desk's editorial composite (Tier C) — never published as fact.

A patch is the most republished item in the newsroom. The desk treats every patch as three parallel artefacts: the balance log (publisher-verbatim), the meta shift (editorial read), and the context document (editorial composite of the season's coaching interviews). Below is the working method for each, written for a reader who wants to follow the desk's read from the patch's drop to a published editorial.

The balance log — verbatim reproduction

The balance log is the publisher's own patch notes reproduced verbatim in the newsroom. The desk does not editorialise the balance log. Where the publisher publishes a table of changes — character, change type, magnitude — the desk reproduces the table as-is, with the publisher's own citations. Where the publisher publishes only a written list, the desk reproduces the list with the publisher's wording. The balance log is Tier-A.

The balance log is filed under a stable public URL with a verification date and a publisher-source citation. The URL is the canonical reference for the patch's balance changes; editorial reads and meta shifts link back to the balance log URL.

The meta shift — editorial read

The meta shift is the desk's editorial interpretation of how the patch changes the competitive meta. The meta shift is filed within 24 hours of the patch drop; the desk reads the publisher's roadmap, the regional press, and any early coach interviews the editor has access to. The meta shift is Tier-C and is explicitly flagged EDITOR'S READ.

The meta shift is not a prediction. The desk does not rank the new meta's strongest team, character or pick rate. The shift is a read-through of the patch's likely impact, written in editorial scenario language and stamped accordingly.

The context document — composite editorial

The context document is the desk's editorial composite of the patch through the season's coaching interviews. The context document is published 7 to 14 days after the meta shift, once the first two weekends of post-patch matches have produced enough broadcast footage for a composite reading. The context document is Tier-C with a corrections log; readers who disagree with the composite are invited to send a correction to the corrections desk.

The context document is the longest editorial artefact the desk produces for a patch. It is the editorial document a reader who wants to understand the post-patch competitive scene can re-walk themselves, against the same broadcast footage the desk used.

What the desk does not publish for a patch

The desk does not publish mid-week balance speculation. Pre-patch speculation is Tier-C only when the publisher's roadmap has explicitly disclosed the change; otherwise, speculation is held until the patch drops.

The desk does not publish private developer comments. The publisher's published developer commentary is re-printed; private chat content, screenshot leaks, and unverified community chatter are held until the publisher confirms. Where private content is widely reported, the desk files the story under the news beat with a Tier-C read and a note that the desk is awaiting citation lock.

The desk does not publish patches for retired titles. A retired title's balance log stays in the archive; the desk does not delete coverage.

Five chapters across fifteen titles is a lot of editorial ground to cover for a reader who follows esports from the newsroom side. Below is a reading list the desk itself uses to re-walk its own coverage. Use it as a starting point for any of the five chapters; each chapter has its own pattern of patches, broadcasts, brackets and editorial reads.

FPS — reading list

The FPS chapter covers Counter-Strike, Valorant and tactical shooters. Counter-Strike coverage is the densest in the chapter, with monthly patch cadence, a Tier-A mirror feed for every regional series, and a tactical board the desk publishes per bracket stage. Valorant coverage is bi-weekly, with a parallel agent-meta patch-watch rail. Tactical-shooter coverage is quarterly, with a wider-rotation emphasis.

MOBA — reading list

The MOBA chapter covers League of Legends, Dota 2 and mobile MOBAs. League's bi-weekly patch cadence drives the chapter's editorial cadence; Dota's monthly cadence drives a deeper editorial read per patch. Mobile MOBAs carry their own Tier-A source rules — see the desk's editorial standard.

Battle Royale — reading list

The Battle Royale chapter covers PUBG, Apex Legends and tactical BR. PUBG's monthly patch cadence is similar to Dota's, with a weekly opening-zone-collapse summary per regional series. Apex's bi-weekly patch cadence drives a fast editorial cycle; tactical BR's quarterly cadence allows deeper editorial reads.

Fighting — reading list

The Fighting chapter covers Street Fighter, Tekken and platform fighters. The seasonal patch cadence produces one or two editorial reads per calendar quarter per title. The bracket seeding for fighting titles is a different reading path from the other four chapters.

Racing and Sim — reading list

The Racing and Sim chapter covers sim racing and arcade circuits. Lap-by-lap telemetry, fuel strategy and stint simulation produce a different editorial shape — the editorial reads are filed per race weekend rather than per patch.