// THE POST-MORTEM
Reviewing a Run
Every result is a lesson if you read it. A battle moves through three stages. You watch it unfold, you get a post-battle breakdown, and then you open analytics to understand exactly why you won or lost. Most players stop at the first stage. The ones who climb live in the second and third.
Watch it unfold
A freshly accepted battle plays as a live, real-time head-to-head. Both controllers defend the same peg while their running scores climb. The market timeline shows events as they fire, one after another, and the winner stays hidden until the run completes. Watch the timeline, not just the score. The events tell you what your controller was reacting to, and the moment the gap moved is usually the moment a battle was won or lost.
The post-battle breakdown
When the run completes you get a results screen. It reveals the winner and compares both sides pillar by pillar: peg health, control quality, participant balance, and liquidity strategy. It also shows the settlement and your rating change. This is the headline view. It tells you the outcome and, just as important, where the outcome was won. You see the opponent's scores on each pillar, but never their controller or their liquidity settings. You learn that you lost on control quality. You do not learn what they did differently.
Peg Health
How close to target you held the price across the whole run.
Control Quality
How clean your response was: firm when needed, calm when not.
Participant Balance
How well you kept both sides of the market in line.
Liquidity Strategy
How wisely you sized and spent the firepower you committed.
The analytics dashboard
If you played the battle, you can open a deeper analysis of your own side. Your market price is drawn against your opponent's on a single chart, so you can see exactly where the two runs split apart. Below it sits an event-by-event story: what the market did, and how your controller responded to each shock. Then comes your run diagnosis across three lanes, peg discipline, controller behavior, and liquidity, followed by consistent coaching that points you to one thing to tune next. The opponent's configuration always stays private. You are studying your own film, not theirs.
Analytics gives you a direction, not a single magic config. It might tell you that you over-corrected, or that you ran out of firepower early. It will not hand you the settings that win every time, because those do not exist. Take the direction, make one change, and test it.
Replays you can share and study
Settled battles become replays anyone can rewatch, with full transport, so you can scrub to any moment, pause on the worst spike, and play it back in slow motion. Each replay has its own shareable link. Use replays to slow down the turning points instead of trusting memory, which always smooths the story in your favor. They are also how you study which conditions your config handles well and which ones break it.
Find your lowest pillar in the breakdown. Turn it into a single hypothesis, for example "my control was too slow on the first big shock." Then go to solo practice and test only that. One change, one question, one clear answer.
Next: carry what you learned into Solo Practice, then back into Ranked Battles.