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.
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.