

Decision route · Patch 7.41e
Audit lost tempo through four timestamps
A replay audit beyond KDA: income, purchase, map move and conversion into control.
- For
- Player after a confusing loss
- Window
- One replay, 15-minute review
Four steps
01-04Every step ends with a verifiable exit
Do not read everything in sequence. Open the relevant layer, run the check and return to the route with a result.
- 01

Economy Mark four timestamps
- What to do
- Capture lane end, first major purchase, first contested objective and the moment territory was lost.
- Move on when
- The replay has four comparable frames instead of a continuous retelling.
- 02

Player paths Compare the action with the role
- What to do
- At each timestamp, ask whether the hero performed the role's next map job.
- Move on when
- Each timestamp has an expected job for the hero.
- 03

Meta Separate patch context from execution
- What to do
- Check only version changes that actually affect the item, hero or selected window.
- Move on when
- No execution error is hidden behind a generic meta explanation.
- 04

Guides Write one new checkpoint
- What to do
- Choose the minute, resource and action to inspect in the next match.
- Move on when
- The conclusion can be tested in one next replay.
Route rules
Three rules that cannot move to make the answer convenient
- 01Find the first lost conversion, not the final mistake.
- 02Every purchase is checked against the next map move.
- 03The conclusion must change one checkpoint in the next match.
Current contextPatch 7.41e
The primary source defines the game version. Every amount, horizon and risk in the route remains a testable player input.
Other hub playbooks