LoL2LLM
← Back to all guides
AI Workflow

Every JSON Field LoL2LLM Exports, and Why It Matters

7 min read · Published

Comments

A field-by-field walkthrough of the JSON LoL2LLM hands to ChatGPT or Claude: how the export checkboxes map to JSON keys, a real output sample, and what to watch for when you paste it.

Orianna

CHAMPION LENS

Orianna

Champions in this guide
Nocturne
Ezreal
Nautilus
Fiora

LoL2LLM pulls the fields worth analyzing out of the Riot API match data and writes them as JSON with shortened key names. One thing to keep straight: the checkbox labels on the export screen ("Basic Metadata", "Combat", and so on) are not the key names that appear in the JSON (game, me, and so on). This guide maps one to the other, explains what each key holds, and flags what to watch for when you hand it to an AI.

Checkboxes vs JSON keys

Here is how each checkbox maps to the JSON. Every box is checked by default.

CheckboxJSON keyWhat's inside
Match Context › Basic MetadatagameMode, duration, patch, result, queue ID
Match Context › Team MacroteamsBoth teams' bans, objectives taken, total kills, total gold
My Performance › Combatme.combatKills, deaths, assists, KDA, damage to champions, damage taken, and more
My Performance › Economyme.economyCS, gold earned, level
My Performance › Visionme.visionVision score, wards placed and killed, control wards bought
My Performance › Loadoutme.loadoutItems, summoner spells, runes
Participants › Allied TeamalliesA summary of your four teammates
Participants › Enemy TeamenemiesA summary of all five enemies
Participants › Lane Opponentlane_opponentDetailed stats for the enemy in your role

The real output looks like this. It's a live match (KR_8270926232) exported with every box checked and anonymization on, taking the jungler as "me". Some fields are folded onto one line for readability, and "…" marks omitted parts.

{
  "game": {
    "mode": "CLASSIC",
    "dur_s": 1530,
    "patch": "16.12",
    "result": "Loss",
    "queue": 420
  },
  "teams": {
    "ally": {
      "bans": [235, 555, 34, 126, 143],
      "obj": { "dragon": 1, "baron": 0, "tower": 3, "herald": 0 },
      "total_k": 26,
      "total_g": 52862
    },
    "enemy": { … }
  },
  "me": {
    "name": "Player (Me)",
    "champ": "Vi",
    "role": "JUNGLE",
    "combat": {
      "k": 11, "d": 4, "a": 7, "kda": "4.50",
      "dmg_champs": 22141, "dmg_taken": 32119,
      "largest_spree": 8, "multi_kill": 2, "cc_s": 34
    },
    "economy": { "cs_total": 168, "cs_min": 17, "cs_jg": 151, "gold": 12988, "lvl": 14 },
    "vision": { "score": 55, "wards_placed": 10, "wards_killed": 13, "ctrl_bought": 10 },
    "loadout": {
      "items": [3155, 6610, 2055, 3026, 3111, 3071, 3364],
      "spells": ["Flash", "Smite"],
      "runes": { "primary_style": "Precision", "primary_picks": [8010, 9111, 9104, 8017], … }
    }
  },
  "allies": [
    { "name": "Ally (TOP)", "champ": "Ambessa", "role": "TOP", "k": 2, "d": 6, "a": 6,
      "kda": "1.33", "dmg_champs": 22773, "gold": 8668 },
    …
  ],
  "enemies": [ … ],
  "lane_opponent": {
    "name": "Enemy (JUNGLE)", "champ": "Naafiri", "role": "JUNGLE",
    "k": 6, "d": 5, "a": 7, "kda": "2.60",
    "dmg_champs": 20016, "dmg_taken": 23454, "cs": 195,
    "gold": 11617, "lvl": 15, "vision": 41,
    "items": [6699, 3071, 6695, 2019, 2422, 3364]
  }
}

game and teams: the conditions of the match

game holds the mode (mode; Summoner's Rift games are CLASSIC), game length in seconds (dur_s), patch (patch), result (result), and queue ID (queue; 420 is Ranked Solo/Duo). The patch helps keep the AI from judging your game against a different patch's meta. Game length is the denominator for CS/min and every other per-minute figure: a 6/0/2 in a 20-minute stomp is a different game from a 6/0/2 in 40 minutes of teamfighting.

teams has an ally and an enemy block, each with bans (bans), dragons, barons, towers, and heralds taken (obj), total kills (total_k), and total gold (total_g). Bans are champion IDs, not names, and -1 means no ban. This is the team-level frame your individual stats sit inside; kill participation, for example, is your kills plus assists divided by total_k.

me: your own stats

me holds your name, champion, and role (name, champ, role) plus whichever sub-categories you checked: combat, economy, vision, loadout.

The AI won't always translate item IDs into the right names. When you ask for a build review, add the names of your main items to the prompt so nothing gets misread.

allies and enemies: the other nine

allies holds your four teammates and enemies all five opponents. Each entry is lighter than me: name, champion, role, kills, deaths, assists, KDA, damage to champions (dmg_champs), and gold. Without it, though, an AI cannot tell whether your 6/2/8 is good or bad — it has no peer comparison. Damage share, for example, is your dmg_champs divided by the sum of dmg_champs for you and your four teammates.

lane_opponent: the most useful single section

lane_opponent holds the enemy who played your role: kills, deaths, assists, and KDA, plus damage to champions, damage taken, total CS (cs), gold, level, vision score (vision), and items. A prompt like "compute CS, damage, and death deltas vs lane_opponent and judge who came out ahead" gives you a metric-grounded verdict instead of a vibes-based one. Keep in mind these are end-of-game totals, so they can't show how the lane phase itself went.

The opponent is matched by role, so supports get the enemy support. In games without assigned roles (ARAM, for instance), lane_opponent is not included. Between two supports, comparing vision score and damage taken shows the gap in vision work and in how much each soaked on the front line.

The anonymization toggle

"Hide usernames" is on by default. While it's on, names become role labels: you are Player (Me), teammates look like Ally (TOP), and enemies like Enemy (JUNGLE). Turn it off and each player's Riot ID game name appears instead. Only the names change; every number the analysis uses stays the same. Leave it on when you want to discuss the game publicly (Reddit, Discord, X) without dragging other players' names along.

Don't check every box

Even with every box checked, one game is about 3,900 characters (measured on the match above), so size isn't the problem. The problem is focus: numbers unrelated to your question tend to pull the answer toward them. Curated sets by question:

Once you understand what each field carries, you can match the export to the question. Specific input, specific question, specific answer — that's how you turn an LLM into a useful coach instead of a generic feedback machine.

Found this article useful? Leave a like, and share your thoughts or questions in the comments.

Try it on your own games

Search your Riot ID and export your match data as AI-ready JSON.


Comments

Loading comments…

Write a comment

0 / 1000

To prevent spam, we record your IP address and browser details when you post (they are never shown). Comments appear on every language version of this article, and posts that break our Terms of Service are removed.

Read another guide

Ahri
Stat Fundamentals · 5 min

How to Read LoL Match Stats: KDA, CS, Vision, and Damage Share

Read the post-game scoreboard the way a coach would. Role-aware benchmarks, what each number actually measures, and how to combine them before handing the JSON to an AI.

Read
Lee Sin
Stat Fundamentals · 6 min

LoL APM (Actions Per Minute) Explained, With Measured Ability Casts per Minute by Rank

What APM (actions per minute) means in League of Legends and why a high APM doesn't make you a better player. LoL has no official APM, so we measured ability casts per minute (Q/W/E/R) from Riot match data by rank, role and champion.

Read
Jhin
AI Workflow · 4 min

The Best Prompts for ChatGPT and Claude to Analyze a LoL Match

When to use which of LoL2LLM's five personas, plus the one-line additions that turn a generic answer into a sharp one.

Read