Agent changes
Two agents return to the select pool. The first-pick rate across the next four rounds reflects the change. The patch post lists the agents and the rationale; the desk cites the patch post verbatim and does not paraphrase the rationale.
Patch posts are dense by design. The reading order is straightforward: read the agent or hero changes first, then the map changes, then the economy changes, then the side selection changes. Agent or hero changes shift the pick pool; teams adapt within the first round. Map changes rotate the pool; the veto process reflects the rotation. Economy changes shift the buy window; teams adjust the save phase. Side selection changes refresh the side bias figures; the data poster on the games page carries the latest side bias figures. Where a developer has not yet published a side bias figure, the row says pending. The patch reading order is the same for every title; the specific changes vary by title.
Patch posts are dense by design. The reading order is straightforward: read the agent or hero changes first, then the map changes, then the economy changes, then the side selection changes. Agent or hero changes shift the pick pool; teams adapt within the first round. Map changes rotate the pool; the veto process reflects the rotation. Economy changes shift the buy window; teams adjust the save phase. Side selection changes refresh the side bias figures; the data poster on the games page carries the latest side bias figures. Where a developer has not yet published a side bias figure, the row says pending. The patch reading order is the same for every title; the specific changes vary by title.
The editorial standard applies across the site. The verification note attached to each entry lists the source page the data was drawn from. We do not fabricate placement, roster composition, dates, scores, brackets or player data. Where a figure is pending publication by the league, the entry says so explicitly and does not invent one.
For viewers who want to read more, the related hubs linked below cover the same topic from different angles. The tournament index pairs with the match schedule to surface the format primer for each event. The team directory pairs with the player profiles to surface the current roster for each team. The news desk pairs with the guides to surface the editorial standard for each story.
Every figure on the site links back to a verified source: the league page, the org's official announcement, or the developer's patch post. Where a figure is pending publication, the entry says so.
Patch 8.4 is the most recent patch for Title A. The patch post covers four sections: agent changes, map changes, economy changes and side selection changes.
Two agents return to the select pool. The first-pick rate across the next four rounds reflects the change. The patch post lists the agents and the rationale; the desk cites the patch post verbatim and does not paraphrase the rationale.
Map Charlie rotates out at the start of week 38. The map pool narrows from seven maps to six. The veto process on the matches page reflects the new pool. The patch post lists the map and the rotation schedule.
The buy window is retuned; the save phase rounds run slightly shorter. The patch post lists the buy window and the save phase adjustment. The desk cites the patch post verbatim.
Side bias figures refresh after week 38. The data poster on the games page carries the latest side bias figures. Where the developer has not yet published a side bias figure, the row says pending.
Patch posts are dense by design. The reading order is straightforward: read the agent or hero changes first, then the map changes, then the economy changes, then the side selection changes. The total read is five to ten minutes for most patches. The reading order is the same for every title; the specific changes vary by title.
Agent or hero changes shift the pick pool. Teams adapt within the first round; the editorial desk watches the first-pick rate across the next four rounds and updates the meta shifts rail. Map changes rotate the pool; the veto process reflects the rotation. Economy changes shift the buy window; teams adjust the save phase. Side selection changes refresh the side bias figures.
Where the developer has not yet published a side bias figure, the row says pending. The editorial desk does not infer side bias from a single match; the figure must reflect the league's published match history across the cycle. The desk reads the developer's patch post and the league's published match history together to write the patch read.
The patch reading order is the second cheat code. Read the patch, then read the round. The format primer on the format-glossary page covers the round layout. The bracket explainer covers the round layout in detail. The map veto process page covers the operational schedule for the match. Together, the three references are the operational map for the competitive circuit.
Five references for viewers who want to read patch posts in detail and understand the meta shifts the editorial desk tracks across the cycle.
Patch context, map pool shifts and meta reads for every active title. The patch hub panel covers the current patch version, the most recent meta shifts and the map pool state.
Editorial coverage of recent patch impact on the competitive circuit. Each entry cites the developer's official patch post and the league's published match history.
Every term a viewer will hear on the broadcast. Bo1, Bo3, Bo5; single elim, double elim, GSL, Swiss, round robin. Plain-language definitions.
Today's matches, listed by start time in UTC. The match card carries the format, the stage and the verified broadcast link.
How the map veto works. Ban-ban-pick with a worked example from week 37, including side selection and the order that decides who picks first.
The editorial desk covers patch literacy the same way it covers every other editorial subject: cite the source, do not invent figures, and mark pending entries explicitly. The desk reads the developer's official patch post after every patch closes and updates the patch hub on the games page. The desk does not infer patch impact from a single match; the impact must reflect the developer's official patch post and the league's published match history across the cycle.
Where the developer has published a partial patch post — for example, a side bias figure that has not yet been published — the patch hub lists the published portion and marks the rest as pending. The desk does not estimate the missing portion. The desk does not run rumors. The desk does not paraphrase quotes from caster desks.
The desk publishes the patch primer for every active title on the games page. The patch primer covers the current patch version, the most recent meta shifts and the map pool state. The primer links to the deeper explainers on the patch explained page. The primer is editorial copy, not a citation.
Where the patch includes a map change, the desk publishes the map pool rotation on the games page. The map pool refreshes after every major patch. The desk does not infer map pool rotations from a single match; the rotation must reflect the developer's official patch post and the league's published match history across the cycle.
Where the patch includes an economy change, the desk publishes the buy window retune on the games page. The buy window refreshes after every major patch. The desk does not infer buy window retunes from a single match; the retune must reflect the developer's official patch post and the league's published match history across the cycle.
The patch explained page is the starting point for new viewers. The patch hub on the games page is the public reference for patch literacy. The patch impact entries on the news desk are the editorial coverage of patch impact. Together, the three references are the operational map for the competitive circuit.