How should I read the piano clue?
🎹 Callout builder
Piano sequence card
Write the note sequence in a fixed order and use the readback before pressing.
Choose the octave and light, read the matching four-note cell in the current manual, then tap keys to rehearse the packet.
Name the stage, note labels, and any adjacent symbol or LED. Use a consistent left-to-right description, then repeat the final note sequence before the input player starts.
Piano module facts
| Field | Reference answer |
|---|---|
| Difficulty | Medium |
| Module type | Defusal |
| Panel footprint | Check the current keyboard and Braille layout |
| First fixed campaign appearance | Level 9 |
| Fixed campaign appearances | Levels 9 and 10 |
The note sequence is selected by the Braille octave number and the active light colour. Read the matching cell in the current in-game manual before using a sequence in a live run; the available octave rows and light columns can change with the build.
Worked-state status
Braille octave plus active light selects one four-note cell. Use the current in-game manual for the exact notes instead of carrying a copied example into a live run.
Piano callout card
| Emoji | Callout field | What to say |
|---|---|---|
| 🔢 | Braille octave | Give the row number first. |
| 💡 | Active light | Give the light colour with the number; either clue alone is incomplete. |
| 🎵 | Four-note packet | Read the notes in order and keep repeated notes. |
| 🔁 | Repeat-back | The input player repeats the full packet before pressing. |
| ✅ | Accepted | Confirm that the panel advanced before using another sequence. |
| 🛑 | Rebuild | If one note or the light is disputed, reread number + light. |
Two independent module references agree on the lookup shape—Braille octave plus active light selects the note sequence. The emoji is a communication aid; the current in-game manual remains the authority for the exact four notes.
Piano lookup status
| What the player has | What it proves | What is still required |
|---|---|---|
| Braille octave number | Selects the row | Confirm the active light |
| Active light colour | Selects the column | Read the four-note cell in the live manual |
| Four notes in order | Defines the input packet | Repeat the packet before pressing |
The live manual remains the authority for the exact note sequences. This page keeps the stable lookup rule and the callout format, while directing the team back to the current in-game chart for every octave-and-colour combination so an outdated sequence is not carried into a new build.
Keyboard orientation 🎹
The visible keys follow the ordinary left-to-right note order C → D → E → F → G → A → B. A recorded playthrough repeats that order while the player reads the Braille-marked keys, and the current module reference also shows a short keyboard with tactile/Braille marks. Use the letter order only to orient the operator; it does not replace the octave-and-light lookup.
What if the sequence fails?
Check whether the stage advanced or reset, record the exact state, and compare it with the puzzle index.
What should be written down before pressing?
Write the stage number, visible note labels from left to right, any nearby symbol or light, and the sequence the interpreter gives back. The operator should repeat the sequence once, then press it without improvising a missing note. If the panel resets, keep the failed sequence in the notes so the team can tell a wrong interpretation from a missed input.
What is the complete piano workflow?
- Name the piano module and stage.
- Read every visible note from left to right.
- Report any adjacent symbol, indicator, or changed panel state.
- Have the interpreter translate the clue into a note sequence.
- Ask the operator to repeat the sequence before pressing.
- Record whether the panel advanced, reset, or rejected the input.
Do not begin pressing while the observer is still counting notes. A sequence that is correct for one stage may be wrong after the panel advances.
The Module Solver is a practice and read-back utility: choose the Braille octave and active LED colour, read the matching note cell from the current manual, then tap the keys to rehearse the packet. Record the state and have the operator repeat the sequence before pressing.
How should repeated notes be called?
Use position and label together: “second key, C,” rather than only “C.” This avoids confusion when the same note appears more than once. If the team uses shorthand, keep it stable for the whole level and write the long form in the notes.
What should happen after a failed sequence?
Stop, reread the stage, and check whether the panel reset or advanced. Do not append another note to the old sequence until the current state is confirmed. Link back to the puzzle index if the visual panel no longer resembles the piano reference.
For level context, check Level Lookup and Campaign Progression. For coordinated callouts, see Roles and the Puzzle Index.