Sources & methodology
Every public clue has a source.
ChampDiff’s public beta uses a deliberately small, auditable clue pack from Riot’s supported Data Dragon feed. Richer experimental clues stay out of the public game until their provenance is verified.
Public clue pack
What a round compares
| Clue | Source field | How feedback works |
|---|---|---|
| Champion | English and Korean name | The guessed champion anchors each row. |
| Role(s) | Riot champion tags | Exact for the same set, partial when at least one role overlaps. |
| Resource | Champion resource type | Exact when the resource matches. |
| Attack range | Base attack range | Exact on the same value; an arrow points toward the target value. |
| Difficulty | Riot difficulty score | Exact on the same score; an arrow points toward a higher or lower target score. |
Gender, current lane positions, species, lore regions, range categories, and release year came from sources that are not yet cleared for public use. They remain available only in an explicit internal Classic mode.
Upstream
Where the data comes from
Champion identities, localized names and titles, role tags, resource type, base attack range, difficulty score, and champion imagery come from Riot Games’ static Data Dragon files. Data Dragon versions content independently of the live game patch, so ChampDiff shows the source version rather than calling it the current patch.
The local snapshot records both upstream URLs and the generation time. A data refresh is reviewed before it becomes playable so a new champion or changed value cannot silently alter an active beta.
Corrections
Found a value that looks wrong?
Include the champion, clue, displayed value, expected value, and a Riot source. Never include your room token or private chat content.