A short, honest description of the process behind every champion guide, tier-list signal, and meta call we publish.
We wait at least 48 hours after a patch deploys before we start writing. That window lets hotfixes settle and gives us time to play matches across every role on the affected champions, instead of reacting to the first day of public sentiment. We then validate findings against multiple roles before any guide goes live.
Static champion data — abilities, base stats, ratios, item interactions — comes from Riot Data Dragon, the official static asset bundle. For current-meta verification we cross-check against Riot match-v5, the public match endpoint, so our notes reflect what is actually being played at the patch we are writing for. We never scrape third-party aggregators.
Guides, articles and counter pages are written with artificial intelligence. For champion guides the first draft starts from the official Riot Data Dragon data for the patch we are writing about, and the editorial rule is to leave out whatever cannot be verified against that source rather than soften it. Before publication every guide goes through the repository's automated checks, which stop the build on section structure, required fields, slug and role consistency, and on the items listed in the opening block, each one checked against Data Dragon to confirm that it exists and can be bought on Summoner's Rift in that patch. For blog articles the checks cover structure and publishing, not game data, and a person reads the article before it goes online. Champion guides and counter pages are different: nobody reads the text before publication, so they may contain mistakes or advice that no longer holds. Treat them as a starting point to verify, not as a final source. Publishing remains the responsibility of the site owner, Adriano Di Pietro: that is responsibility for what goes online, not a statement that every guide has been proofread.
Each guide is reviewed at minimum every patch cycle, roughly every two weeks. When a meta-shifting change lands earlier — a system rework, a major item rebalance, a champion-defining buff or nerf — we trigger an off-cycle refresh instead of waiting for the next patch.
We focus on teaching. We never copy-paste from generic stat aggregators, and we prefer reasoning over tier labels. A guide that explains why a build path works in a matchup will always rank higher in our review than a guide that just lists the highest win-rate items of the day.
We do not promise statistical win-rate guarantees, and we do not advertise a guaranteed climb. We do not present personal coaching credentials or rank-based authority claims. Our value is patch-anchored explanation; if a guide cannot defend its reasoning, it should not be published.