BOMBANANA Piano Module Guide and Braille Callouts

Publication status: candidate workflow

This is a candidate observation and communication workflow, not a verified full-release answer sheet. It stays out of the index while the module roster, complete lookup table, Campaign appearances, timer, and mistake behavior remain unverified. Do not treat this page as proof that Piano appears in a specific level.

Quick answer

The BOMBANANA Piano module combines two clues, the current Braille row and the light color. A collected practice reference organizes seven Braille rows against four light colors, creating 28 lookup states. Use that structure to understand the input packet, yet treat the exact full-release mapping as To be confirmed and let the current in-game manual decide the sequence.

The manual guide explains the general relay. The three-role guide explains who should report tactile information, visible color, and the final physical input.

Read both clues before lookup

Name the module first. The player with the tactile view reports the Braille row, and the visual player reports the light color. The manual reader should repeat both values before choosing a piano sequence.

Do not let the color replace the Braille clue. Four colors can point to different results depending on the row, and a correct row with the wrong light is still the wrong lookup. Number any keys or positions that the bomb handler needs to identify physically.

The 28-state practice structure

The collected reference uses seven Braille rows and four light colors. That gives a 7 by 4 set of possible input states. One practice example maps Braille 1 with Yellow to the sequence C, E, G, C. This example is a study reference only and is To be confirmed for the current full-release build.

The important lesson is the shape of the lookup. The team must keep the Braille row and the color attached until the manual reader returns the complete sequence. Dropping one clue early turns a precise lookup into a guess.

A safe Piano procedure

1. Name the Piano module.
2. Report the Braille row in the agreed wording.
3. Report the light color separately.
4. Repeat the pair and let the manual reader check the live rule.
5. Return the complete key sequence with physical positions.
6. Have the bomb handler repeat the sequence and wait for confirmation.
7. Report whether the panel cleared, changed, or expects another input.

This is the same observation, lookup, relay, and confirmation loop used by the communication guide. It keeps the person who knows the rule from assuming that the person who can touch the piano has seen the same clues.

Common Piano mistakes

The first mistake is reporting a color without a Braille row. The second is reporting a letter sequence without saying which physical keys those letters refer to. The third is carrying a previous sequence into a new stage.

Use a stop signal when the row is uncertain. If the light changes or the panel advances, discard the old pair and collect the current state again. A practice table cannot repair a missing observation.

What remains To be confirmed

The 7 by 4 practice structure and the example above are useful for describing the collected guide material, yet they do not prove that every row, color, sequence, timer, or Campaign appearance is permanent in the full release. The complete current mapping, level placement, mistake behavior, and any update-specific changes remain To be confirmed.

When the live manual disagrees with a remembered sequence, use the live manual. Add a permanent table only after a current reproducible record supports every row and color. Until then, the Modules database should point players toward the workflow rather than a guessed answer sheet.