3 min read · Published · Updated
Jungle gives the least real-time feedback of any role. The fix is a post-game review framework grounded in your own export — here's the one I use.

CHAMPION LENS
Lee Sin
Karthus
Kindred
Shaco
NidaleeJungle is the role where it's hardest to know, mid-game, whether your last decision was correct. The feedback comes too late and too quietly. The fix is to build a habit of reviewing the match data afterward and asking whether the choices were actually rational. Here's the framework I use to evaluate jungle games from the JSON LoL2LLM exports.
Full clear into level-3 gank: stable. Maximizes XP and gold; weak early pressure. Default for scaling junglers (Karthus, Graves, Nidalee).
Three-camp into early gank: aggressive. Generates lane pressure but vulnerable to a counter-clearing enemy. Lee Sin, Elise, Zac territory.
Counter-jungle first: high risk, high reward. Steal camps to open an XP lead. Shaco, Kindred, top-tier Ekko games.
Which is correct depends on the matchup of your champion vs theirs. A useful prompt: "given my champion and the enemy jungler, which opening path was the correct one?" — checks whether your draft-time plan even made sense.
Gold-range median for jungle CS at 10 minutes is 40–50. Below 35 means you've burned too much time on ganks or got counter-cleared. Above 55 with zero kill participation means you over-farmed — you weren't affecting any lane.
Share of your team's kills + assists you were involved in. Jungle target is 60–75%. Below 50% you basically weren't on the map.
Caveat: KP scales with total team kills. 5/8 in a low-kill game (62%) and 12/20 in a bloodbath (60%) read the same percentage but mean different things. Always check raw kill count alongside.
The most concrete numeric on jungle "macro work." Targets through minute 15:
Voidgrubs: 3–4 as a team (out of 6)
Drakes: 1–2
Zero grubs and zero drakes means you lost early map control entirely. "But my KP was great" doesn't convert to wins under those conditions. Objectives are to junglers what CS is to laners.
The JSON doesn't carry coordinates, but each death time is recorded. Jumping to those timestamps in the in-client replay is one of the highest-leverage habits in solo queue.
The recurring patterns:
Invading the enemy jungle without knowing where their jungler is
Third gank into a losing lane — same trap, three times
Engaging at drake with a bad teamfight comp because the timer felt urgent
Asking the AI "at each of my death timestamps, what objective or fight was happening?" surfaces situational mismatches.
KDA lies more on jungle than any other role — great KDA losses and bad KDA wins are both common. The check I run on every jungle game:
jungle CS at 10 ≥ 40 AND kill participation ≥ 60% AND drake participation ≥ 50%
Pass all three: your jungle game succeeded, win or lose — the loss was downstream of you. Fail any one: there's room even if KDA looks fine. Hand the AI this rule of thumb explicitly and the analysis becomes a verdict, not a suggestion list.
The Gold-range median is 40-50. Below 35 means you burned too much time on ganks or got counter-jungled out of your XP. Above 55 with zero kill participation means you over-farmed and weren't affecting any lane.
60-75%. Consistently below 50% means you basically weren't on the map. Note that KP scales with total team kills, so always read it alongside the raw kill count.
Three archetypes: the stable full clear into a level-3 gank (default for scaling junglers like Karthus and Graves), the aggressive three-camp into an early gank (Lee Sin, Elise territory), and the high-risk counter-jungle-first opening (Shaco, Kindred). Which is correct depends on your champion versus theirs.
Pass all three checks: jungle CS at 10 minutes of 40 or more, kill participation of 60% or more, and drake participation of 50% or more. Pass them all and your jungle game succeeded win or lose; fail any one and there's room to improve even if the KDA looks fine.
QiyanaReal Challenger match data from T1 jungler Oner's public account, pulled via Riot's official API and run through AI analysis. The actual CS/min, kill participation, and damage share of a pro jungler, and why jungle farm runs lower while KP runs higher, with match IDs you can verify.
NautilusWhat kill participation (KP) means in League of Legends, how it's calculated, and measured median KP by role and rank from JP1 solo queue match data. Why farming alone loses, what to fix when your KP is low, and how to analyze your own games with AI.
ThreshWhat counts as a good vision score in League of Legends for support, jungle, solo lanes, and ADC — with measured per-minute medians by role and rank from JP1 solo queue match data, how vision score works, and why it stays low even when you ward.