From .replay file to coaching note in roughly 20 seconds.

1. 01

   Drop a replay

   Native .replay format. Drag-and-drop into the dropzone in the viewer. The upload kicks the rest of the pipeline immediately — by the time you finish reading the loading screen, the engine is already scoring.

   Multi-replay batch upload is in pilot for Coach-tier accounts. If you're prepping for a coaching session, drag in the whole session at once and the worst-possessions list aggregates across replays.

   ~1s
2. 02

   Frame parse

   The replay is decoded tick-by-tick into a high-frequency time series of every car's position, velocity, boost, and ball state. Our parser handles every recent Rocket League build without breaking.

   Robust to version skew, including patch-day breakage that takes other tools out for a week. If a replay from yesterday parses, a replay from a year ago will too.

   ~3s
3. 03

   Possession segmentation

   Touches are stitched into possession episodes — sequences bounded by clear-of-zone events. Each possession becomes a unit with an entry frame, exit frame, and a list of touches.

   This is the layer where 'who had the ball, when' becomes computable. The engine operates over possessions, not raw frames, because possession value is the right primitive for coaching.

   ~2s
4. 04

   Threat scoring

   Every touch on every car gets a Threat score — 0 means harmless, 1 means a goal. The engine reads the whole field on every frame, not just the touched player.

   The scoring engine is trained on a curated 100K+ replay corpus, refreshed as the metagame moves. The engine you score against next month will be better than the one today.

   ~10s
5. 05

   Coaching notes

   Per-possession Threat deltas are translated into plain-English notes. Generated from a tight library of human-written templates fit to engine output — no LLM hallucinations.

   Notes are rank-stratified. A Plat player gets Plat-shaped notes; a GC gets GC-shaped notes. The library is a few hundred templates with strict constraints on which possessions they apply to.

   ~3s

Fast enough to use between matches.

Most replay-analysis tools are slow on purpose: they batch, they queue, they email you when it's done. That's fine if you treat coaching as homework — and worthless if you want to apply the note before the next ranked queue pops.

Twenty seconds means you finish a match, drop the replay, read the worst possession, and re-queue with that one thing in your head. The cycle stays tight. That's the only way coaching tools actually move MMR.