First-person shooters — round economy, utility timing and post-plant defaults
The FPS desk covers Counter-Strike, Valorant and the wider tactical-shooter bracket. The desk reads rounds as a sequence of utility, set-piece executes and post-plant defaults; patch reads are filed within 24h of any Tier-A drop.
Three titles on the desk this season
Counter-Strike
Round economy, utility timing, set-piece executes. The desk files a balance-log entry per patch and a meta-shift editorial within 24 hours of any Tier-A drop.
Valorant
Agent meta, post-plant defaults, retake timing. Bi-weekly patches with smaller balance changes filed into the balance log without a standalone meta-shift read.
Tactical Shooter
Three-lane rotation, defender tempo, anchor efficiency. Quarterly patches; full scene reads published through the editor's coaching column.
How the FPS desk reads a round
A round is buy, utility, contact. The desk reads three artefacts per round: the buy, the utility use, the contact outcome. Where a publisher publishes a per-round timeline, the desk reproduces the timeline; where a coach quotes a contact decision, the desk files the quote under the editorial stamp.
Buy phase
Reproduce the buy from the publisher feed. Where the feed omits a buy, mark the read as Tier-C with a note.
Utility phase
Track utility use by team, by map and by round. Cross-stamp with the broadcaster's grenade cam where available.
Contact phase
Note the contact outcome, the time-to-contact and the trade structure. Editorial flag if the contact deviates from the coach's stated set-piece.
Post-plant phase
Default reads: kit timing, retake tempo, lurk windows. Edit only when the publisher's stream overlay corroborates the read.
Editor stamp
Tier-A lock where the publisher feed and the broadcaster overlay agree. Tier-C where one disagrees.
Archive
Filed under the FPS chapter archive with the publisher feed URL, the broadcaster overlay URL and the editorial stamp.
How an FPS patch moves through the desk
FPS patches are the desk's most-published patch reads. The desk files a balance log, a meta-shift editorial, and a context document for every Tier-A FPS patch. Below is the desk's working method for each.
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 weapon change (damage, recoil, fire rate, magazine), the desk reproduces the table as-is with the publisher's own citations. The balance log is Tier-A.
The balance log is filed under a stable public URL with a verification date. The URL is the canonical reference for the patch's balance changes; meta-shift editorials and context documents link back to the balance log URL.
Meta-shift editorial
The meta-shift editorial is the desk's read of how the patch changes the competitive meta. The editorial 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 editorial is Tier-C and is explicitly flagged EDITOR'S READ.
The meta-shift editorial is not a prediction. The desk does not rank the new meta's strongest team or pick rate. The read is a sequence of plausible scenarios, written in editorial language and stamped accordingly.
Context document
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.
What the desk does not publish for an FPS 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, the 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.