How we verify this wiki

Every claim on HoKWorld Wiki is attached to a source and a confidence tier. This page documents what those tiers mean, how we collect data, and how the dates on each page are computed.

Source tiers

We classify every source into one of three tiers. Inline citation markers and the Sources list at the bottom of entity pages surface the tier for every reference.

T1 — first-party

First-party (official API, game data)

• world.qq.com — official Tencent game portal API (hero roster, CN names, cover art).
• Game client DataTables — extracted from the NGR/Content/Paks/*.db files of the Chinese PC build (1,069 tables, 20,463 rows as of patch 1.0.6.20).
• Official CDN assets — published at ngrrelease.gcloudcdn.qq.com.

T2 — reputable secondary

Reputable secondary (press, established wikis)

• baike.baidu.com — Chinese-language Wikipedia equivalent, used for lore and historical character background.
• gamersky.com — the multi-page compendium 2117382 is our primary source for hero skill CN names and tips.
• Press previews from Gamescom 2025, GDC 2025, WCCFTech, VGC, and Ungeek, where the game was played hands-on.

T3 — community aggregation

Community aggregation (forums, dataminers)

• NGA forum (king.nga.cn) threads with dataminer spreadsheets.
• Reddit r/HonorOfKings, r/gachagaming datamining posts.
• Bilibili gameplay clips with visible skill tooltips (used to cross-reference CN numbers).

How we verify

• Triangulation.Load-bearing claims — damage numbers, release dates, launch rosters — need at least two independent sources at T2 or above before we publish them without a "speculative" marker.
• Named citations.Every specific number or date on the site is linked to a named source. If we can't name a source, we don't state the fact — we mark it as pending.
• Bilingual cross-check. CN and EN names stay locked together so a mistranslation can be spotted by any reader who reads either language.

Freshness policy

Every entity page shows its last-verified date. That date advances only when the underlying content actually changes. Concretely: every deploy runs tools/compute_content_hashes.py, which SHA-256-hashes the semantic fields of every hero, boss, item, region, etc. If the hash matches the previous build, the date stays put. If the hash changes, the date advances to that deploy's date.

This matters because silently bumping dates on unchanged pages is a well-documented spam signal (see John Mueller's 2023 statement on lazy sitemap lastmod). Our dates are meant to be honest — stale content shows stale dates, rather than looking artificially fresh.

What we deliberately avoid

• Tencent-owned artwork. We do not redistribute official character splash art, logos, or in-game screenshots beyond the small subset already hosted on the public CDN. Where we need an image we cannot link, we generate a placeholder locally.
• Fabricated stats.Skill damage, cooldowns, mana costs — most of these are server-side and not in the client DataTables. If we don't have a verified number, the field stays empty rather than being filled with a plausible guess.
• Invented author profiles. No stock photos, no generated biographies. Attribution is by git commit history, not by persona.

Corrections

If a claim on any page looks wrong, please raise it via Contact. Include the page URL, the specific sentence, and the source you're comparing against — we'll verify and either update the page or add a note explaining why the existing claim stands.