Filed 09 September 2026 · Source: match-desk preview template, partner-published VOD convention, organiser-signed bracket diagram, dated roster filing · Tier-one plus tier-two. A reader's guide to how the same broadcast tape feeds an esports match preview and a post-match review, what the lineup, round and VOD markers reveal, and where the two pieces of coverage disagree.
One new filing this week. The article below explains how the same broadcast tape feeds an esports match preview and a post-match review, what the lineup, round and VOD markers reveal, and where the two pieces of coverage disagree; older filings are linked from the news desk.
The edition below explains what is announced, what is still pending, what the patch ledger changed yesterday, and how the viewer is expected to navigate games, teams, players and tournaments on the desk.
Switch the lens without leaving the desk. Each chapter uses the same verification ladder and the same source labels, only the gameplay taxonomy changes.
One axis follows competition progression; the other records editorial verification. A teal pill means the source ladder reaches the tournament organiser; terracotta means we have only second-hand signalling; muted means nothing has crossed the wire yet.
Three matches below. Confirmed facts sit in the upper ledger; the analytical scenario under each one is what we would write if the announced players hold, the patch holds and the announced bracket remains.
Both teams confirmed by the broadcast partner at 12 Aug 09:00 IST. Map pool restricted to six. Sidedraft order pending.
Patch 7.4 referenced. Draft study pending verification on stage order and side selection.
Character pool announced at 02 Aug. Stage direction still tentative pending venue load-in.
The desk does not run a power ranking — it records what the organiser, the team and the players have said about themselves. Numbers shown are roster size and tenure in the current split.
| Active roster | Game | Region | Tenure | Verified source | Status |
|---|---|---|---|---|---|
| Aurora Captain Reema · IGL Yuna · Operatives 4 | FPS | Asia-Pacific | Split 4 · 18 months | Organiser press kit · 04 Aug | Confirmed |
| Hermit Top-lane Kale · Mid-line Sai · Jungle Niro | MOBA | Asia-Pacific | Split 7 · 26 months | League filing · 06 Aug | Confirmed |
| Kestrel Sniper Dain · Spotter Rune | FPS | EMEA | Split 3 · 11 months | Team social · 31 Jul | Tentative |
| Yuna (player) Solo travel · coach Iris on standby | FIGHTING | EMEA | Top-32 streak · 5 events | Player interview · 02 Aug | Confirmed |
| Quill Five players · analyst squad | MOBA | EMEA | Split 2 · 8 months | League filing · 06 Aug | Confirmed |
| Drift Duo Two confirmed seats · reserve in waiting | RACING | Americas | Endurance · 2 entries | Sanctioning body · 28 Jul | Confirmed |
Each dossier is on its own team page. Numbers above reflect only what is signed and dated by an organiser; numbers still on social or unverified scouting chatter are not yet included.
Every player dossier on the desk describes in-game role before it describes brand deals, social following or any invented stat line. Use this atlas to find how a roster fits together.
Calls the macro plan. On broadcast footage the captain usually reads late and chooses first. Look for the captain in a slower page-tilt before the round starts.
Looks after pacing and resource flow for the rest of the squad. Often the one mic'd to the coach during timeouts.
Where the round is decided. Most drafted compositions put the duel liability onto this slot — high variance, high impact.
Picked as a tactical answer to one opponent. Often subbed out for the next map; sometimes the trick that flips a series.
Both reads were cross-checked against the developer's notes and the post-patch meta summary. Where a third source differs, the desk flags it; the desk never guesses version numbers.
Both field sketches are pencil-on-paper reconstructions of publicly discussed strategy segments. The desk does not leak private scrim conversations; these diagrams restate what broadcast desks have already framed on camera.
FPS arena — two-site retake concept · pencil on cream paper.
MOBA field study — three lanes converging on a neutral base.
Each desk keeps its own calendar, its own patch tracker, and its own broadcast partner contact. Nothing on the desk assumes a fictional ranking.
The matrix is rebuilt for every edition. Row order mirrors the calendar (left = earliest), with platform, broadcast language, region lock and replay access listed in plain language.
Recaps written from the broadcast tape. Where footage is missing or audio was unclear, the line is shorter and the desk flags the gap. No round counts or K-DAs are invented.
Two smokes, one flash, one incendiary — the holder had no answer for the package. We walk through the call, the clock and the substitute that came in for round 12.
Source: broadcast cut + verified clip · 30 July
One side gained tempo control by trading mid-priority for a side-lane duellist. Read the macro reasoning, the side selection logic and the early-game ward chain.
Source: broadcast cast + verified segment · 31 July
Every claim on this desk is built on a four-step ladder. Higher numbers are stronger sources; lower numbers are reported with caveats and a date stamp the reader can check.
Corrections are issued at /customer-care/. The desk never silently edits a tier label; if a story moves from L3 to L1 after verification, the byline is annotated.
The desk reads esports as a spectator practice. Some readers follow competitive brackets closely. The editor's note below is for any reader considering monetised prediction routes to engagement — pause, set a budget, know the limits.
The portal is a separate consumer surface maintained by an operator named elsewhere in the desk's coverage. We do not put the operator's destination URL on the desk; we route through a first-party tracker so the desk can keep its source ladder honest.
The portal is a third-party operator surface — opening it leaves this desk and lands on their own terms, age verification and disclosure pages. The desk has no editorial control past the redirect; the reader is responsible for confirming their local rules.
18+ only · local law applies · operator routes the rest of the journeyAffiliate disclosure — the desk never displays the destination URL on the coverage.
Selected reader questions published with the desk's reply. If your question is here, it has been researched against the source ladder; if it is not, the desk may be verifying sources before answering.
Each desk keeps a partnership rosette that names the regional broadcast partner for the event listed. Where the partner has changed or two partners exist, the desk names both and dates when the partnership began.
A confirmed source is at least L1 — the tournament organiser or its licensed broadcast partner has signed and dated the announcement. Tentative is L2 or L3; awaiting is below that.
Power rankings are subjective; the desk works with sourced claims. When a scene publishes its own ranking with methodology and the desk reads the methodology, the desk summarises it but does not endorse the order.
From the organiser's filed rosters and the team's own social account. Numbers from third-party trackers are not used unless they match a Tier-one source. Public open qualifier pages are listed on the tournaments route.
Through the corrections desk page at /customer-care/. The desk keeps the original date stamp, adds the correction date and notes the section affected. We never silently retype a claim.
The colophon on a small desk is short: who is responsible, what is in scope, where to file a correction. Below is the operating statement of egame newsroom.
Coverage of announced esports competition across FPS, MOBA, battle royale, fighting and racing. The desk does not cover gambling advertising, skin commerce or unverified ranking drama.
The editor of record is named on the /owner/ page and on every published article byline. Decisions on tier labelling, correction timing and event coverage sit with the editor.
A correction is any change to a published claim — wording, tier or date. The original claim is kept visible alongside the correction so readers can audit the change. Email the corrections address listed on the customer-care page.
This site may link to a first-party tracker that records a click before landing the reader on a third-party operator portal. We do not earn editorial decisions from those clicks; we never trade coverage for placement.