League of Legends / Riot API / Po account report. Source: Riot API pull for Jocelyn Flores#505, EUW, fetched on 2026-06-05.
Po / Jocelyn Flores League Coach Report
This report uses Riot API account, ranked, champion mastery, latest 20 ranked solo queue match details, and timeline data. It is not frame-by-frame VOD review, but it is strong enough for player profiling, champion-pool read, role tendency, recent form, training priorities, and product validation.
One-Sentence Coach Verdict
Po's account profile is strong: Master I 753 LP, 55% win rate over the latest 20 games, and 6.85 average KDA. The hardest climb signal is not support; it is Kha'Zix/Talon jungle. The latest 7 jungle games are all wins, with clear kill-window and snowball ability. The support sample does not look like an awareness issue: KP and vision investment are both real. The likely fix is death control, reset/exit discipline, and turning enchanter/engage value into map conversion.
Core Riot API Read
753 LP, 198W / 191L, API status shows current hot streak.
All RANKED_SOLO_5x5, 6.85 average KDA, 60.7% average kill participation.
Jungle 7, Bottom 7, Support 6. This is not a one-role account.
Lux 308,667 points; Talon, Sona, Janna, Nami, and Senna are also high-mastery picks.
Recent Role Profile
| Role | Sample | Signal | Coach Read |
|---|---|---|---|
| Jungle | 7 games, 7 wins; Kha'Zix 5 games, Talon 2 games. | Lines like 19/4/6, 9/0/8, 14/2/12, 13/1/4, and 18/2/10 are not normal noise. | This is the strongest current carry lane. Po can tear the game open with assassin jungle. The training focus is not whether he can kill; it is whether every kill converts into herald, dragon, invade, side tower, or enemy jungle quadrant. |
| Support | 6 games, 2 wins / 4 losses; Sona/Janna/Rell/Nami/Lux. | 62.5% average KP, 2.83 vision/min, 3.83 control wards. Participation and vision are not absent. | The support issue looks like fight-end discipline. A Janna 2/6/20 loss with 3.91 vision/min shows heavy involvement, but deaths and resets need review. |
| Bottom / Mage carry | 7 games, mostly Lux/Senna/Seraphine. | Lux bottom has high-DPM games such as 1055.6 and 1016.4 DPM, plus low-death losses. | The damage is real, but we need lane control, wave crash, objective setup, threat range, and pre-fight positioning. API proves output; VOD proves whether the output was controllable. |
Strengths To Keep
1. Assassin Jungle Tempo Conversion
The Kha'Zix/Talon recent data is not merely good-looking. It is winning repeatedly while producing high kill density. Kha'Zix games include 19/4/6, 9/0/8, 13/1/4, 18/2/10, and 15/8/12. Talon includes 4/11/11 and 14/2/12. Even the high-death Talon game wins, which suggests enough chaos creation and map value to overcome messy fights.
Coach advice:Make this the main climb lane. Do not review jungle games by asking how many kills happened. Ask what the first kill became: camp lead, objective, plate/tower, vision denial, or enemy jungle quadrant.
2. Broad Champion Pool, Good Coach Profile
This is not a single-champion climb account. High mastery includes Lux, Talon, Sona, Janna, Nami, Senna, Bard, Nidalee, Sylas, and Seraphine. The latest 20 also cover jungle, bottom, and support. For the coaching product, this is a strong signal: Po can explain the same game from different roles instead of only one lane lens.
Coach advice:Po's coaching angle should be cross-role game-state explanation. He can connect support wave/vision language with jungle tempo/objective language, which is harder for a one-role coach to do.
Main Repairs
1. Support Needs Stricter Death / Exit Rules
The support sample averages 4.83 deaths. That is not catastrophic, but combined with 2-4 results and high KP, it suggests Po often gets into the right fights but does not always exit, reset, or preserve position after the value has been created. For example, the Janna 2/6/20 loss has deaths at 4, 11, 15, 19, 23, and 38 minutes. Early and midgame death chains damage enchanter tempo.
Drill:After every assist, immediately label the next state: continue, cover wave, reset, objective, or deep ward. The support goal is not to stand around for five more seconds. It is to turn a won exchange into the next first-move condition.
2. Mage Bottom Needs Control, Not Only DPM
Lux/Senna/Seraphine bottom damage is high enough to prove the output exists. But high-DPM losses usually point toward wave state, objective setup, threat range, or teamfight entry angle. API can tell us damage and result; it cannot tell us whether Q/E/R angles or pre-fight positioning were correct.
Drill:For bottom mage games, review only three questions: did we have lane control before first dragon, did each ultimate trade for objective/summoner, and did the last 10 seconds before a lost fight give enemy engage angle?
Recent 20 Sample
| Champion | Role | Result | KDA | KP | DPM | Vision/min |
|---|---|---|---|---|---|---|
| Talon | Jungle | Win | 4/11/11 | 42.9% | 650 | 0.97 |
| Kha'Zix | Jungle | Win | 19/4/6 | 67.6% | 1169 | 0.97 |
| Kha'Zix | Jungle | Win | 9/0/8 | 77.3% | 882 | 0.95 |
| Talon | Jungle | Win | 14/2/12 | 49.1% | 836 | 0.91 |
| Kha'Zix | Jungle | Win | 13/1/4 | 54.8% | 859 | 0.91 |
| Kha'Zix | Jungle | Win | 18/2/10 | 57.1% | 1483 | 1.64 |
| Janna | Support | Loss | 2/6/20 | 59.5% | 392 | 3.91 |
| Sona | Support | Win | 4/3/30 | 68.0% | 679 | 2.73 |
| Lux | Bottom | Win | 11/4/15 | 70.3% | 1016 | 0.50 |
| Lux | Bottom | Win | 7/0/5 | 35.3% | 608 | 0.66 |
API Product Boundary
Riot API reports can already automate rank, recent roles, champion pool, KDA, KP, damage, vision, wards, death timing, and objective timeline. That is strong enough for a 10-minute first diagnosis.
It does not replace VOD. Skill angle, movement, mouse/camera, wave detail, fight target selection, and comms require replay/VOD. The best product shape is: Riot API profile + uploaded VOD + human coach explanation of key turns.
30-Day Training Plan
| Week | Theme | Completion Standard |
|---|---|---|
| Week 1 | Jungle kill conversion | For every Kha/Talon game, mark what the first three kills became within 45 seconds. |
| Week 2 | Support exit rules | After each fight, tag the next state: reset, cover wave, objective, deep ward, or continue. |
| Week 3 | Mage bottom control | Only review pre-dragon lane control and whether ultimate trades for objective/summoner. |
| Week 4 | Coach template | Turn API fields into a product template: rank profile, role split, champion pool, recent form, death timing, VOD ask. |