Skip to content
Menu
Practice & progressDeep dives

How to review an osu! replay and diagnose repeated misses

Follow a replay review checklist, separate aim and timing observations, and troubleshoot missing beatmaps or incomplete score data.

01

Start with the right replay and difficulty

Match the player, play time, exact difficulty and mods before reviewing. A score summary is not a cursor replay: accuracy and miss count cannot reconstruct movement or key presses. An exported .osr also needs its matching beatmap. If playback cannot locate the map, obtain the original difficulty instead of substituting another difficulty with the same song title. In stable, the results screen's F2 export is the documented way to save a replay.

02

Review a short sequence, not a frozen miss

Choose three errors, including one from an unsuccessful attempt. Watch each lead-in at normal speed, then slow playback to inspect the input and movement order. Note the object time, cursor position when input occurs, and the next object. Example note: at 01:12, the cursor is left of the circle on input and enters it afterwards. This supports an arrival/tap coordination observation; it does not prove that sensitivity, reaction time or reading is the cause.

03

Turn the observation into the next check

Cursor outside on input: inspect whether movement stops short or continues past the target. Cursor reaches the target before the input: check whether it leaves too soon. No clear input: inspect recorded key state rather than assuming an aim error. For sliders, locate the head, tick, repeat or end involved before comparing failures. If playback or analysis cannot resolve the event, mark it unknown. Do not count an uncertain label as a confirmed technique problem.

04

Choose one correction you can test

Suggested exercise: after finding the same observation in several places, choose a short section that contains the preceding object and the next transition. Make three attempts with one focus, such as keeping the cursor on the target until the intended tap. Then play another section with comparable movement and rhythm. Record whether the original error decreased and whether a new error appeared. A clean memorised section alone is not evidence of reliable transfer.

05

When replay review cannot answer the question

If a replay ends early, review only the portion actually recorded. If a download is unavailable, a public score entry does not guarantee accessible replay bytes. If the cursor looks wrong after an import, first compare the original map and mod settings. Avoid deleting the original replay while troubleshooting. Keep a compact log: difficulty ID, time, observed event, uncertainty and next check. That gives the next review a concrete starting point.

Keep exploring

Sources & further learning

2 resources