In twice, hitting every note perfectly is not the actual goal. You play one 40-beat chart twice, and the game measures how the timing of those two performances differs. To get a readable result, follow the visible count-in, press once per beat on both passes, and avoid mashing between beats.
Play / プレイURL: https://chiaki-plays.itch.io/twice
Eight steps to a valid result
| When | Action | Result | Source |
|---|---|---|---|
| Open the game | Choose Run game in your browser | Start the two-pass measurement | [1] |
| Find beat one | Watch the playhead sweep during the 3.2-second lead-in | See the first beat coming in v1.0.1 | [1], [2] |
| First pass | Press Space, click, or tap once at each of the 40 beats | Record the first set of timing offsets | [1] |
| Second pass | Repeat the same 40-beat chart without random extra presses | Provide beat-by-beat data for comparison | [1] |
| Hit window | Aim at each beat inside the stated 80 ms window | Reduce misses without covering the gaps | [1] |
| Too many extras | Restart if you made nine or more between-beat taps | The verdict is withheld and the number is marked noise | [1], [2] |
| Read the result | Check hits and signed early/late differences between passes | Understand variation, not a conventional accuracy grade | [1], [2] |
| Play again | Begin a fresh run in version 1.0.1 | Old tap arrays no longer contaminate new results | [1], [2] |
What does the score mean?
The game compares matching beats with signed timing errors. Being 60 ms early is not the same as being 60 ms late: direction matters. Earlier scoring used absolute errors and could erase that distinction. The current design separates drift from spread rather than merely rewarding the smaller average error. No fixed winning score or rank is promised in the published rules.
Why does it say “no reading”?
First count your presses between the intended beats. More than eight extra taps triggers the anti-mashing rule. Version 1.0.1 still shows a numerical value underneath, but labels it noise rather than issuing a valid verdict. If your first note keeps missing, follow the playhead from the beginning of the 3.2-second lead-in. One input method—Space, mouse, or touch—is enough.
Version 1.0.0 versus 1.0.1
A player tested the game using actual Space presses and reported two bugs: the first beat had no visual cue, and tap data carried over between runs. The developer fixed both in 1.0.1, and the tester confirmed the changes. A smaller wording bug remained: a result with 39/40 in both passes could describe a miss as occurring in only one pass. Treat the individual counts as more informative than that sentence.
Bottom line
Play 40 beats twice, once per beat, without nine stray presses. The goal is a valid comparison of two attempts, not an invented perfect-score victory. Exact verdict thresholds and a universal optimal input sequence have not been established by the published material.
References (2)
[1] chiaki-plays, twice, itch.io — rules, controls, timing window, v1.0.1 changes: https://chiaki-plays.itch.io/twice
[2] AI Browser Game Jam 5, twice submission and developer/player exchange, Oct 23, 2026 — real keypress test, bug fixes, remaining wording issue: https://itch.io/jam/ai-jam-5/rate/5210085
