Five format families the desk covers this season, mapped by patch cycle
The games route is the desk's editorial atlas across the format families the operators publish. Each format gets its own update cadence, its own patch reading and its own tournament context. The atlas groups titles by family rather than by publisher, so the patch cycles of the editorial coverage line up with the format windows the operators publish.
Why format families, not titles
A title-level read forces the desk to chase publisher-specific terminology that does not travel between games. A format-level read lets the desk explain the editorial question in terms the reader can apply across titles: composition play in a 5v5 MOBA looks different from setplay in a fighting title, but the editorial question (how does the patch affect this role?) is the same shape across both.
This is the editorial position the desk takes: esports coverage is a format discipline first, a title discipline second. The atlas is the editorial proof: the desk reads the format patch and translates the changelog into the question the reader can carry across titles.
What the atlas excludes
The atlas excludes any title the desk cannot map to one of the five format families. Slot-style games, single-player speedruns and casual-party formats fall outside the editorial scope. The desk does not publish coverage of these formats not because they are unimportant, but because the editorial frame the desk uses (patch reading, role assignments, operator match pages) does not fit them cleanly.
The atlas also excludes any title whose publisher does not publish a public patch-notes page or operator roster PDF. The desk's editorial methodology depends on those sources; without them, the editorial frame breaks. If a publisher later publishes the missing pages, the desk evaluates the title against the same five-format mapping and adds it where it fits.
How the atlas maps to the patch workshop
The atlas is the macro read; the patch workshop is the micro read. The atlas tells readers which format families the desk covers and what each family looks like at the peripheral level. The patch workshop tells readers what the most recent format patch changed and how the desk interprets the change against the role notebook.
The two routes share a vocabulary: composition, rotation, utility, objective, setplay, stint. The atlas uses these at the format level; the workshop uses them at the patch level. Readers who move from one to the other see the same vocabulary applied at two different scales. The vocabulary is the editorial through-line that ties the routes together.
Editorial comparison, not a recommendation
Read before you click
The disclosed first-party route is a third-party product page operated by gogotofly.com. The desk does not edit or approve the operator's product page; readers should review the operator's terms before following the link.
Editorial disclosure
fantasye does not accept wagers. The disclosed first-party route is a product comparison entry.
Reading the atlas at the format level, not the title level
The first habit is to read the format patch before reading any title-specific patch. The format patch is published by the publisher and applies across all titles the publisher covers. Reading the format patch first means the desk knows which utility cooldowns, which map vetoes and which role adjustments are in scope before the desk reads any title-specific patch. Where the format patch and the title-specific patch disagree, the desk publishes the disagreement in the patch workshop right page.
The second habit is to keep the atlas at five format families, not more. The five families are tactical aim, composition play, rotational survival, setplay matches and stint management. The desk does not add a sixth family to make a single title fit; the sixth family would dilute the editorial vocabulary the desk has built. Where a title does not fit cleanly into one of the five, the desk publishes that observation in the title's coverage rather than expand the atlas.
The third habit is to publish the atlas with a "what the atlas excludes" paragraph. The atlas excludes any title the desk cannot map to one of the five format families. Slot-style games, single-player speedruns and casual-party formats fall outside the editorial scope because the editorial frame the desk uses (patch reading, role assignments, operator match pages) does not fit them cleanly. The desk publishes what the atlas excludes to give the reader an explicit editorial boundary.
Where the desk diverges from coverage that mirrors title-level reads is on the format-vocabulary discipline. Trade press will sometimes publish a title-specific vocabulary that does not travel between games. The desk does not. The desk uses the same five-family vocabulary on every coverage so a reader who follows the desk for a tactical aim title sees the same vocabulary on the rotational survival coverage. The discipline is sometimes slower to write; it is always more honest to read.
The desk also treats the atlas as a working document. Format families move up the editorial-ladder as publishers confirm; format families that fall off the publisher page get removed, not retained as a footnote. The atlas is rebuilt from publisher pages only. A format family the desk kept for "tracking purposes" is a format family the reader cannot verify, so the desk removes rather than retains. This is sometimes the slower choice; it is always the more honest choice.
Editorial cycle: weekday-morning source-scan, weekday-afternoon narrative-edit, weekly patch workshop. Verification timestamps on the dispatch stream.
How the desk reads this
The atlas's coverage vocabulary is built around the format families the desk publishes on. The five families are tactical aim, composition play, rotational survival, setplay matches and stint management. The vocabulary is short by design: a reader who follows the desk for three weeks can quote the vocabulary back. The desk does not expand the vocabulary to make a single title fit.
Titles the desk does not cover, and why. The desk does not cover slot-style games because the editorial frame the desk uses (patch reading, role assignments, operator match pages) does not fit them cleanly. The desk does not cover single-player speedruns because the editorial frame is built around competition between teams and players. The desk does not cover casual-party formats because the editorial frame is built around operator-published formats.
Where the desk publishes editorial coverage that crosses format families. The cross-format coverage the desk publishes (e.g. a guide on patch reading that applies across tactical aim and rotational survival) is published on the guides route rather than the games atlas. The atlas is built to be the format-level read; the guides route is built to be the cross-format read. The two routes share the editorial vocabulary.
Where the desk publishes editorial coverage that crosses title families. The cross-title coverage the desk publishes (e.g. a guide on role reading that applies across tactical aim and composition play) is published on the players route rather than the games atlas. The atlas is built to be the format-level read; the players route is built to be the role-level read. The two routes share the role vocabulary.
The atlas does not publish operator-claimed skill ratings. The desk does not publish skill ratings claimed by the operator or publisher because the operator and publisher use different rating systems and the editorial discipline requires one rating vocabulary across the desk's coverage. Where the operator or publisher publishes a skill rating, the desk cites the rating on the publisher page and notes the operator's rating vocabulary on the relevant game route.
How the cycle reads in practice
A worked example of the atlas in practice. A reader asks the desk which format family the desk covers for a particular title. The desk reads the atlas, identifies the format family, and replies with the atlas's family vocabulary. The desk does not extrapolate the format family from the title; the desk cites the atlas's family vocabulary and the publisher's page where the format is published.
Where the atlas covers a worked cross-format example. The reader asks the desk whether patch reading applies to two titles in different format families. The desk replies that patch reading applies at the format level rather than the title level, and points the reader to the guides route for the cross-format patch workshop. The atlas is built to be the format-level read; the guides route is built to be the cross-format read.
Where the atlas covers a worked cross-title example. The reader asks the desk whether the role notebook applies to two titles in the same format family. The desk replies that the role notebook applies across titles in the same format family, and points the reader to the players route for the cross-title role notebook. The atlas is the format-level read; the players route is the role-level read.
Where the atlas covers skill-rating discipline in practice. The operator publishes a skill rating on the operator page. The desk reads the operator page, cites the operator's skill rating on the publisher page, and notes the operator's rating vocabulary on the relevant game route. The desk does not extrapolate a skill rating from the operator's rating vocabulary.
Where the atlas covers editorial scope expansion in practice. The operator publishes a new format family the desk has not covered. The desk reads the operator page, considers whether the format family fits the editorial frame the desk uses, and replies to the operator inquiry on the editorial-ethics page. Where the format family fits, the desk adds it to the atlas; where it does not, the desk declines coverage.