The lead paragraph should answer the reader's question directly: what changed, when it changed, what it means for the next announced event.
What changed
The FPS developer notes for patch 2.13 were published on 30 July. The change that the desk reads as match-shaping is a smoke duration reduction on contested sites. Two smaller changes adjust incendiary area of effect and a single map's geometry have been trimmed. Players have already begun discussing the change on stream.
Reading the smoke duration change
Smoke duration on contested sites goes from eight seconds to six. That is enough to break an Aurora lineup's retake utility routine. The retake playbook for Aurora (filed 04 August) calls for two smokes, one flash and one incendiary at the same choke; with smoke duration down, the holder has a two-second window of clear sight that the retake cannot fill.
What the desk reads from the change
Three things follow. First, Kestrel's required utility coordination rises by one notional utility per round. Second, Aurora's broadcaster demo will need to thread the flash in tighter than the playbook suggests. Third, the cast pair's commentary on 14 August will likely lean on how the holder-vs-retaker sees the timing window.
The desk does not write this as a forecast. The match is announced and dated; the desk is publishing this article to give the reader a frame for the broadcast it intends to watch.
Broader context
FPS patch 2.13 is the smaller of the two current patches the desk is tracking. The larger is the BR season notes from 27 July, which shortened the round-four zone contraction by eight seconds. Both patches shift tournament reading in the same week; both are summarized together on the FPS chapter page.
Continuing coverage
The desk will update this article when the next post-patch meta summary lands. Read it together with the MOBA desk, where the patch is summarised in chapter form.
The desk continues to read paper patch notes alongside the developer's notes; both are linked below for re-checking by the reader.
Related desk reading
Reader questions · this article
Why was this article written now?
The patch crossed the wire at the developer's notes page on 31 July. The desk writes the summary the same week the patch lands so the reader's preparation is current.
What does tier-one actually mean?
Tier-one is signed, dated text from the tournament organiser, the sanctioned league or the developer that publishes the patch. The desk quotes or paraphrases from it directly.
Where can I re-verify the patch numbers?
The developer's notes page is linked in the infobox above. The post-patch meta summary on the broadcast partner is linked as a tier-two source where one is published.
Will the desk update this article?
Yes — when the post-patch meta summary lands on the broadcast partner, the desk reads it and adds the tier-two summary to the article.