Splash art of Master Yi with a gold lead line rising through the game, its key moments lit along it
GuideUpdated for Patch 26.19Updated October 7, 2026 · 8 min read

Match Breakdown: Why You Won or Lost, Explained From the Game's Own Timeline

The scoreboard tells you the score. It does not tell you that the lead peaked at minute 21, that you died three times in the eight minutes after it, or that a Baron turned into zero buildings. Pro+ reads the game's timeline and tells you exactly that.

Short answer: after every ranked, Draft and Swiftplay game, Hexgate Pro+ builds a Match Breakdown from the game's own timeline. It opens from your match history and says, in plain sentences, what hurt and what helped, with the numbers behind each call. It uses AI to decide which signals mattered; every sentence it shows is a fact from your game.

Real Breakdowns, One for Every Role

This guide walks through what a breakdown looks at, mostly with two real games: a Master Yi jungle win with one leak in it, and a Pantheon support loss where three things went wrong. Pick any role to see a real breakdown first. If you want the full window, the homepage has a live example.

Hexgate Match Breakdown of a Master Yi jungle win: highlights, the verdict, one card under what hurt and three under what helped, each with the evidence

Master Yi jungle, a win: "You won, but one thing would have cost you a closer game": 2,000+ unspent gold from minute 25.

Real Match Breakdowns from the Hexgate app. Pick a role.

Why the Scoreboard Is Not Enough

You finish a game 19/4/2 and win, so you assume it was clean. You finish 13/10/20 and lose, so you assume the deaths did it. Both assumptions are sometimes right. Neither is checkable from the post-game screen, because the post-game screen is a total: it adds up the whole game into a handful of numbers and throws away the order in which things happened.

The order is where the answer lives. A death at minute 8, caught alone in the enemy jungle, is a different event from a death at minute 29 while your team takes Baron. Three deaths in the eight minutes after your lead peaked are a throw; three deaths spread across a 39-minute game are Tuesday. A Baron that turns into five buildings won the game; a Baron that turns into zero buildings was a 35-second waste of a numbers advantage. The timeline knows all of this. The scoreboard does not. (If you are comparing tools that read it, our LoL AI coach comparison covers the alternatives.)

What a Breakdown Looks At

A breakdown starts with the verdict: one line that says how the game went and whether the result was mostly on you, on your team, or shared. Under it are cards in two groups, what hurt and what helped. Each card is one thing that changed the result, with the evidence in the second line.

Hexgate Match Breakdown of a Master Yi jungle win: highlights, the verdict, one card under what hurt and three under what helped, each with the evidence
The Yi game: one leak (unspent gold), three reasons it did not matter.

In the Yi game above, the verdict is "You won, but one thing would have cost you a closer game." The one thing: 2,000+ unspent gold held for two minutes from minute 25, peaking at 3,484. That is an item and a half sitting in the shop while the game was being decided. The three helped cards are the reason the leak did not matter: 6.9 CS per minute and 608 gold per minute as a jungler, a Baron at 22.7 minutes that turned into five buildings within 3.5 minutes, and 28 percent of the team's damage with a hand in 55 percent of its kills.

Notice what is not there. No "improve your vision" card, even though a jungler placing zero control wards is easy to flag. In a 26-minute stomp with 10 wards cleared, vision did not decide anything, so it does not get a card. That restraint is the point: a list of twenty tips is a list you stop reading after the second game.

Judged for Your Role

A support who gets told to farm more has been given advice for a different job. Each breakdown judges the game against what your role is supposed to do: ganks and objectives for junglers, vision and roams for supports, the lane matchup and tower pressure for laners, damage and fight timing for carries. The benchmarks come from what players in that role actually do, not from a single number applied to everyone.

Hexgate Match Breakdown of a Pantheon support loss: three cards under what hurt, deaths, a wasted Baron and a thrown lead, and one under what helped, vision
The Pantheon game: three things cost it, and vision was not one of them.

The Pantheon support loss shows the other side. "3 things cost you this game": ten deaths, eight of them after minute 20 and eight on the enemy side of the map, with five to Rumble alone; two Barons that turned into zero buildings; and a lead of 7,787 gold at minute 21 that ended at 728, with three of the deaths in the eight minutes after the peak. The one helped card is vision, 39 wards placed and 12 control wards bought, because for a support that is the job, and it was done well.

Master Yi jungleWin

"You won, but one thing would have cost you a closer game."

  • 2,000+ unspent gold from minute 25, peaking at 3,484
  • 6.9 CS and 608 gold per minute as a jungler
  • Baron at 22.7 minutes into five buildings

Pantheon supportDefeat

"3 things cost you this game."

  • Ten deaths, eight after minute 20, five to Rumble
  • Two Barons into zero buildings
  • 39 wards placed and 12 control wards bought

Same tool, opposite verdict, and the difference is not the KDA. It is where the deaths happened, when they happened, and what the team did with the numbers advantages it earned.

Swiftplay, judged at Swiftplay pace

  • Level 3Everyone starts here
  • 9 minLaning is over
  • 10 minYour lane is judged
  • ~20 minMost games are over

Swiftplay gets its own clock. Everyone starts at level 3, gold comes about twice as fast and most games are over by minute 20, so ranked timings would give wrong advice. In a Swiftplay breakdown, laning is over at 9 minutes and your lane is judged at 10; Baron, Elder and the two-dragon soul are read on Swiftplay's timers; and your farm, deaths and damage are compared with other Swiftplay players, not ranked ones. Farm after your build is finished is never held against you, and dying one-on-one on the enemy half after laning gets its own line.

Your Kills and Deaths on the Gold Curve

Under the cards sits the team gold curve with every one of your kills and deaths on it. Hover a marker to see the minute, who was involved and whether you were caught alone. When the curve peaks and then bleeds out with three red dots in a row, you are looking at the throw, not reading about it.

Team gold lead chart with the player's kills and deaths marked on the curve, and the early game table against the enemy jungler at 10, 15, 20 and 25 minutes
Kills and deaths on the gold curve, then the early game against the enemy jungler.

Next to the curve is the early game against your lane opponent (for junglers, the enemy jungler): CS, gold and level at 10, 15, 20 and 25 minutes. Yi was down 6 CS and 221 gold at 10 minutes and up 22 CS and 2,000 gold at 20. That is the shape of a jungler who lost the early tempo and won the mid game, and it is exactly the shape you would want to know about if the game had gone the other way.

Fights, Objectives, Deaths

The part of the game the scoreboard never records: how many team fights happened, how many you were in, and how they went with and without you. Which dragons, Barons and Heralds your team took while you were there, and which ones fell while you were dead or on the other side of the map. How long you spent dead in total, and what share of your team's kills you had a hand in.

Fights and objectives tiles: team fights with and without the player, objectives taken and lost, time spent dead, kill participation, and the list of deaths with the enemies involved
Fights with and without you, objectives lost while dead or far away, and every death with who was there.

Below that, every death, one row each: the minute, who killed you, every enemy involved, and a tag that says whether you were caught alone with no teammate near or died on the enemy side of the map. Four deaths to Viego, three of them on his side of the map, tells a jungler something specific about where the risk was that game.

Only What Mattered

The hardest part of a post-game tool is knowing when to say nothing. A breakdown only flags what genuinely moved the result. A small vision gap in a stomp stays a clean win. A loss that was not on you says so: the verdict will tell you the result was decided by your team, and the cards will be about the fights you were not in, not about your CS.

The AI is used for exactly that judgment call: given everything the timeline says, which two or three things actually decided this game, and for this role? It does not write the evidence. The minutes, the counts and the names come straight from the game, which is why every card can be checked against the replay.

Coaching: One Thing to Fix in Your Next Game

A breakdown does not stop at what went wrong. Every card that hurt comes with a coach line, and the breakdown picks one focus for your next game, with a tip chosen from how that part of the game went. Deaths to ganks while pushed get a different tip than deaths in a side lane after 20 minutes, and a farm gap built under pressure gets a different tip than one built while roaming.

Focus next game from a jungle breakdown: be on the dragon side a minute before it spawns, with the reason (far from objectives) and that it came up in 5 of the last 10 games, then the hurt cards with next-game tips
One focus for the next game, and a tip under each card.
Habits as jungle from the last 10 breakdowns: far from objectives 5 of 10, a death opened an objective 3 of 10, caught alone in fog marked fixed
Habits across your last 10 games in a role, marked Fixed once they stop.

A few real examples:

  • Late to objectives: "Shove your wave about 45 seconds before an objective spawns and get there first."
  • Side-lane deaths: "After 20 min, leave a side lane as soon as two enemies go missing, unless your team is taking something on the other side at that moment."
  • Slow first clear (jungle): "Aim for level 4 by about 3:30 with a full clear. If you gank before that, it has to get a kill or a Flash."
  • Frontline tank that stayed back: "Walk in first so your carries can hit. Taking damage is the job."

The advice is judged for your role and your champion's class, so a support is never told to farm and an enchanter is never told to walk in first. A death that pulled three enemies away while your team took Baron counts as a trade, not a mistake.

Compared with players of your rank. Your numbers are measured against real ranked games of players in the same rank and role: "At 15 min your CS was in the bottom 20% of Gold players in your role", or, when you did well, "Your vision score was in the top 15% of Platinum players in your role."

Habits across games. When the same mistake shows up in 3 of your last 10 games in a role, it is listed as a habit with its count, and it is marked Fixed once it stops showing up. That is the difference between reviewing one game and actually improving.

How to Use It Without Overthinking It

  1. After a loss, open the breakdown before you queue again. Read the verdict and the first hurt card. That is the one thing to carry into the next game. Ignore the rest for now.
  2. Then watch the death itself. The breakdown tells you why a death cost you; the clip shows you the moment. With Clips, every recorded death in the breakdown has a Watch button that plays it in slow motion, with who killed you and your level, gold and CS against theirs. How rewatching your deaths works.
  3. After a win, read the hurt cards anyway. Wins hide leaks. The Yi game was won with 3,484 gold unspent; against a closer team that is the game.
  4. Watch your habits. If "deaths on the enemy side of the map" shows up three games in a row, that is a habit, not variance. The habits section counts it for you and tells you when it is gone.
  5. Trust the "not on you" verdicts. Some games are lost in fights you were not part of. Knowing that is worth as much as knowing what you did wrong, because it stops you fixing something that was not broken.

Where it lives: click any ranked, Draft or Swiftplay game in Hexgate's match history. Breakdowns are built in the background right after the game ends and stored, so opening one is instant. Games already in your League client's recent history get analyzed too, so the list is full from day one.

What It Costs

Pro+

Hexgate Pro+

  • Match Breakdown of every ranked Solo/Duo, Flex, Normal Draft and Swiftplay game
  • Everything in Pro: unlimited games, lane matchup scoring, OTP builds
  • Lane Scouting on the loading screen
  • Clips of every death to rewatch

€14.99a month, or €11.24 a month billed annually

Get Hexgate Pro+ Compare plans

Match Breakdown is part of Hexgate Pro+, and it includes everything in Pro. Pro+ also includes Lane Scouting, which shows your lane opponents' early-game habits on the loading screen, and Clips, which records every death automatically so you can rewatch it. The free tier and Pro still get the full in-game overlay. Already on Pro? Switch plans from the billing portal in the app.

Before the Game: Lane Scouting

The breakdown explains a game after it ends. Pro+ also helps before it starts: when a ranked or Swiftplay game loads, Lane Scouting reads your lane opponents' own recent games of that mode and shows what they tend to do early, like the enemy jungler's start side and the lane he ganks most, or a lane opponent who dies before 8 minutes in most games. How Lane Scouting works.

Frequently Asked Questions

Does the Match Breakdown use AI?

Yes. Hexgate uses AI to weigh the signals from the game and decide which ones actually changed the result. Every sentence on a card is still a fact from your game: the minute, the number, the enemies involved. The AI decides what deserves a card; it does not invent the evidence.

Which games get a Match Breakdown?

Ranked Solo/Duo, Flex, Normal Draft and Swiftplay games, with Swiftplay judged at its own pace. ARAM and ARAM Mayhem are not analyzed. Games already in your League client's recent match history are analyzed as well, so the list fills with breakdowns as soon as you upgrade.

Does it coach me, or only list mistakes?

It coaches. Each breakdown picks one focus for your next game with a concrete tip chosen from how that game went, compares your numbers with players of your rank in your role, and lists the mistakes that repeat across your recent games as habits, marked fixed once they stop.

Is this the same as the Mobalytics GPI?

No. The GPI scores your skills across many games over time. A Match Breakdown explains one game: what hurt, what helped, and why the result went the way it did. If you want a long-term skill profile, Mobalytics is the tool; if you want to know what happened in the game you just lost, this is.

Is it allowed by Riot?

Yes. The breakdown is built from the match history and timeline that your own League client already holds. Hexgate does not modify game files, read game memory or automate anything, and it works within Riot's third-party tool rules.