MOBAs — draft meta, jungle routes and objective timing windows
The MOBA desk covers League of Legends, Dota 2 and the wider mobile-MOBA bracket. The desk reads drafts through a tier-grade rubric, jungle routes through broadcast overlay, and objective timing through a verified window ledger.
Three MOBA titles on the desk this season
League of Legends
Draft meta, jungle routes, objective timing windows. Bi-weekly patches with smaller balance changes folded into the balance log.
Dota 2
Draft scoring, push timings, Roshan trades. Monthly patches; the desk files a draft analysis within 24 hours of every regional final.
Mobile MOBAs
Wild Rift and Mobile Legends Bang Bang — see the editorial standard for what counts as a Tier-A mobile source.
How the MOBA desk reads a draft
A draft is tier, lane, side. The desk reads three artefacts per draft: the tier of each pick, the lane matchup, and the side advantage. Where a publisher publishes a draft article, the desk reproduces the article's win-rate table; where a coach quotes a draft decision, the desk files the quote under the editorial stamp.
Tier rubric
Reproduce the tier of every pick from the publisher feed. Where the feed omits a tier, mark the read as Tier-C with a note.
Lane matchup
Track lane matchup by side and by role. Cross-stamp with the broadcaster's broadcast overlay where available.
Side advantage
Note the side advantage, the win-rate band and the trade structure. Editorial flag if the side deviates from the coach's stated draft.
Jungle route
Default reads: jungle start, gank tempo, invade windows. Edit only when the publisher's stream overlay corroborates the read.
Objective timing
Track the dragon, the baron and the Roshan trades. Tier-A lock where the publisher feed and the broadcaster overlay agree.
Archive
Filed under the MOBA chapter archive with the publisher feed URL, the broadcaster overlay URL and the editorial stamp.
How a MOBA patch moves through the desk
MOBA patches are the desk's most-republished patch reads. The desk files a balance log, a meta-shift editorial, and a context document for every Tier-A MOBA 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 champion or item change, 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 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 champion or pick rate. The read is a sequence of plausible draft 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.
What the desk does not publish for a MOBA 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.
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.