LoL2LLM
Back to all guides
By Role

Jungle Pathing 101: Evaluate Your Jungle Game From the Match Data

7 min read

This article is currently shown in English. A translation is in progress.

Jungle 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.

The three opening pathing archetypes

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.

Metric 1: jungle CS at 10 minutes

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.

Metric 2: kill participation

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.

Metric 3: drakes and voidgrubs

The most concrete numeric on jungle "macro work." Targets through minute 15:

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.

Metric 4: where you died (replay required)

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:

Asking the AI "at each of my death timestamps, what objective or fight was happening?" surfaces situational mismatches.

The one-line success test

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.

Try it on your own games

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


Read another guide
By Role · 7 min

ADC Positioning: What KDA Hides and Damage Share Reveals

An ADC's real job is sustained damage in fights, not staying alive. Four metrics that catch the "safe but useless" pattern KDA can't see.

(English)
Read
By Role · 6 min

Vision Score by Role: It's Not Just the Support's Job

How vision score is calculated, the per-role targets that actually matter, and the three timing rules that determine where wards go.

(English)
Read
AI Workflow · 9 min

How to Analyze Your LoL Games with ChatGPT: A Complete Guide with Copy-Paste Prompts

A step-by-step method for getting coach-level analysis of your League of Legends games from ChatGPT or Claude. Why screenshots fail, how to feed structured data, and role-by-role prompts you can copy.

(English)
Read
Jungle Pathing 101: Evaluate Your Jungle Game From the Match Data | LoL2LLM