Evidence before speed
Editorial Policy
This policy explains how LoL Classic Wiki sources, labels, writes, reviews, and corrects League of Legends Classic coverage.
Effective and last updated
Source priority
- Current first-party Riot Games, League of Legends, LoL Esports, or Tencent League pages for the relevant region.
- Official account, support, patch, and developer material when it directly supports the claim.
- Reputable reporting for discovery and clearly labeled context.
- Community posts and datamining only as leads or speculation, never as official confirmation.
Fact-status labels
Stated directly on a current Riot Games, League of Legends, LoL Esports, or Tencent League source.
The main point is official, but an important detail or regional application is still missing.
The reviewed official pages do not currently answer this question.
A community, media, or datamining claim that is not suitable for publication as an official fact.
Directly observable in public creator testing with a stable timestamp and recorded test environment.
Directly verified in a recorded game-client capture for the stated region and build.
Rechecked in the public launch client for the stated region and patch.
A test-build or incomplete fact that must be rechecked in the public launch version.
A reviewed claim that conflicts with stronger evidence or fails the evidence requirements and must not be published as fact.
A status belongs to a specific claim. One official sentence does not automatically confirm a full roster, all item values, a complete queue list, or every regional implementation detail.
Writing and review rules
- Answer the search question before adding background.
- Use absolute dates and name the timezone or regional service.
- Keep official facts, partial facts, unknowns, and speculation visibly separate.
- Do not invent search metrics, dates, game values, builds, qualifications, downloads, or personal experience.
- Do not copy a competitor's wording, imagery, code, table design, or brand treatment.
- Generate visible FAQ answers and structured data from the same reviewed source.
Automation may assist with research organization, drafting, testing, and formatting. Publication still requires direct source review, consistency checks, and an evidence boundary. Tool output is never treated as authority over a first-party source.
Update policy
The homepage shows its last-updated and last-verified dates. Live status, access rules, maintenance, systems, and regional events can change quickly. Material official changes should update the central fact data, visible answer, FAQ, structured data, source log, and verification date together.
Corrections
If a statement is outdated, regionally misapplied, or unsupported, note the page URL, the disputed sentence, and a first-party source that supports the correction. Do not share account credentials, private identifiers, or other sensitive information.
Confirmed corrections should update every affected surface. A correction does not silently convert community reporting into official evidence.
Commercial and editorial independence
The current release includes Google AdSense site-verification code and an ads.txt seller record, and selected content pages may show a labelled native banner from a third-party advertising network. It contains no affiliate links, paid rankings, sponsored placements, or fabricated recommendations. Any future monetization will remain separate from evidence status and editorial conclusions.
Return to the current LoL Classic guide or learn more about LoL Classic Wiki.