11 Reading Patterns by Name
Skills are what you train. Patterns are what you search for. A player who can say "I lose spaced streams and squares" can find practice maps in five minutes; a player who says "my aim is bad" cannot. The vocabulary below is the community's, stabilized across more than a decade of guides. 1,66
| Pattern | What it is, and what it tests |
|---|---|
| Jump | Two objects placed further apart than the map's normal spacing. Tests aim speed and precision; cross-screen jumps test both at once |
| Square | Four jumps forming a square, in any rotation. Tests pattern processing more than aim, and chained squares are called tornado jumps |
| Triangle, star | Three or five objects in a closed shape. Same demand as squares, at different counts |
| Stream | Consecutive 1/4 objects. Tests finger control, tapping stamina, and flow aim (Ch. 12) |
| Spaced stream | A stream with wide spacing between notes, so it becomes an aim test at the same tap rate |
| Burst, triple | Short runs, often three to eight notes. The bridge between singletapping and streaming |
| Fast singles | Spaced notes at borderline stream speed, too fast to tap comfortably with one finger but spaced like jumps |
| Stack | Objects on the same spot. A stream that doesn't move; pure tapping |
| Slider stream | Short sliders in place of stream notes. Rewards holding over tapping, and punishes mashing |
| Tech | Irregular rhythms, odd snaps (1/3, 1/6), and unusual slider shapes. Tests reading above everything else |
Don't read a pattern as a shape
The oldest concrete reading method in osu! comes from that 2012 thread, and it still holds: never look at a pattern as a whole. Break it into lines of two notes and count them.
- Two notes = one line. Think "one-two".
- Triangle = a line plus a note. Count "one-two, one".
- Square = two lines, the second running opposite to the first. Hit the first note of each line and ignore the transition in between.
- Star = "one-two, one-two, one", because three-note counting breaks down when the pattern cuts across the playfield.
- Five notes or a pentagon = three, then a line.
Fact check
- Research. This is chunking, and it's the same limit that makes it necessary: working memory holds about four chunks at once, so a five-note shape read as five items overflows while the same shape read as "line, line, note" does not. 101
- Adds detail. The method's author adds a trick worth stealing: count the pattern with the hitsounds rather than the visuals, so you know when it ends and can move your attention to the next one before it arrives. 66
Take: jesse1412's thread
- Squares are the pattern nearly everyone fails, and reading them as shapes is why. Agrees with the chart. Pattern processing, in DigitalHypno's terms, and the fix is the same: split it into pieces you already know. 1,66
- High AR is arguably the easiest to read once mastered, because nothing else is on screen. Supported. At AR 10 objects are visible for 450 ms rather than 600 or 750, so fewer overlap. That is the same mechanism Tonehh warns about from the other side: comfort at high AR can hide an inability to read dense low-AR screens (Ch. 8). 15,47
- Practicing Hard Rock as a newer player wrecks your sightreading, leaving you able to play only fast maps. Agrees with Tonehh. Written in 2012, eight years before the video that makes the same argument, by a different player about a different symptom. 15,66
- Pick your sensitivity or area and stop changing it, so muscle memory can form. Agrees with everyone since. The same rule the 2026 top players give. 19,40
- Mouse players should use low DPI. Contested, even in the thread. One reply recommends staying under 800 and going lower; another top mouse player of the era recommends high DPI, under 2000, and says it helps more in the long run. Pointing research puts both inside the broad middle range where performance is flat, which is the honest answer: neither is wrong, and changing constantly is worse than either. 66,139,140
Spinners
Spinners are the one hit object this book has otherwise ignored, and they are almost pure mechanics.
- Hold the key down and spin in one direction until the circle fills. Releasing the key, or lifting the pen, stops the spin being read at all.
- Never reverse direction mid-spinner. The game drops your spins per minute to zero and resets the orientation before it starts counting again, so a reversal costs more than a slow spin would have.
- Keep spinning after it clears. Extra rotations pay bonus score and restore health, which makes a spinner the cheapest health recovery in a map when you're close to dying.
- The ceiling is 477 spins per minute, which is also the rate the Auto mod spins at. Spun Out spins for you at 287, so if a map's spinners are the only thing failing you, that mod exists.
- Technique is unglamorous: a small, fast circle near the middle of the play area, driven by the wrist for a mouse or by short pen circles on a tablet. There is no research here and no top-player consensus worth quoting. 53
Fact check
Triples: which finger starts
A triple is three 1/4 notes, stacked or moving. There are two ways to tap them:
- zxz, then xzx — alternate which finger starts each triple. Harder to learn, but each finger rests between triples, so consecutive triples cost less.
- zxz, zxz — always start on the same finger. Easier to keep a rhythm, but your lead finger is effectively streaming while the other rests.
The first is the chart's finger-control test in miniature: can you start a pattern on either finger? Build it at speeds where it stays clean, then raise the tempo. 1,66
Drill: Name the pattern, then chunk it
- Open any map at your comfortable level in the editor, or watch it in a replay, and write down the five patterns that recur most.
- For each, decide its chunking before you play: line, line plus note, two opposing lines, three then a line.
- Play the map twice with that plan in mind. Squares and stars are where the difference shows first. 66,101
Train this with your own data
This chapter trains reading. Numbers come from your real top plays (see how on your profile).
Finished this chapter?
Log in to track progressMark it complete for 🍪 100 and track your way to Codex Graduate.
Community discussion
Discussion is not evidence: it never changes the chapter directly. Corrections go through Codex suggestions, where they're checked against sources.
Forum threads about this chapterStart one
None yet — longer questions and write-ups belong in the forums, where they stay findable.