BOMBANANA! Piano Module: Octave, Light, Sequence

The Piano module is a Medium-tier lookup puzzle in BOMBANANA!, and musical talent is irrelevant to it. The rule quoted in community coverage is not about playing well — it is about relaying a number and a colour correctly, then playing whatever the manual's row tells you to play. This page covers the loop as published, the two inputs that decide whether the round survives, and the parts that no source has verified. Status on this site: Observed in footage.

The Published Rule

The official rule is quoted as:

"Play the notes in sequence based on the octave number written in Braille, and the color of the active light."

Read that as a lookup, not a performance. Two pieces of information come off the bomb — the octave number (read in Braille) and the colour of the active light — and the manual turns that pair into the key, or key sequence, that has to be played. The skill the module actually tests is a clean relay of both facts, because only one player can touch the panel, only one can read the manual, and only one can see the light.

Because it is a pure lookup, the failure modes are input failures. Nothing about the module rewards guessing a melody, and nothing about it punishes a team for being unable to read music — it punishes a team that loses one character of the octave number or recycles last round's colour.

The Four Calls

The published loop runs in four calls, one role each:

Read the octave. The Blind — or the Deaf, whoever can read the display — reports the octave number written in Braille.
Read the light. The Deaf reports the colour of the active light.
Look up the sequence. The Mute finds the row for that octave and light colour in the manual, which maps to the key, or key sequence, to play.
Play. The Blind plays the keys in order on the braille-engraved keyboard.

Note how the calls divide: the octave and the light are the only two facts the panel produces, and the manual is the only place they turn into an action. If your team's callout order puts the manual lookup before both facts are on the table, the Mute is guessing a row — and a guessed row is a wrong sequence played at speed.

The Two Inputs to Protect

Because the module is pure lookup, the two things worth protecting are its two inputs:

The octave number must be read precisely. Braille digits swap easily under pressure. The Deaf should read the number back to the Blind before the Mute looks it up — that readback is the cheap check that catches a transposed digit while the panel is still untouched.
The light colour is per-sequence. Reusing the previous round's colour without a fresh call is a guaranteed strike. Call the active light again for every sequence, even when it looks unchanged.

Both failures look the same from the outside: a confident answer drawn from stale information. Neither is fixed by reading the manual harder.

Sequence Discipline

When the manual asks for a sequence of keys, press them one at a time with confirmation — the same readback ritual the cable-style modules need. Teams that narrate the whole sequence and then ask "go" make transcription errors at the worst moment: somewhere between the second and third note, the description and the action stop matching, and nobody notices until the panel resets.

Two habits keep a sequence honest:

Confirm each key before it is pressed, so a wrong note is caught after one input instead of after five.
Re-state the octave and light at the start of the sequence, not once at the beginning of the round — the pair is what the manual row was keyed on.

What Is Not Verified

No collected source verifies a Piano note sequence or an answer mapping, so everything specific stays Unconfirmed (reviewed September 21, 2026):

The name itself. Community references contain unverified module names, and a visual module can be described with a familiar label that differs from the in-game title. Whether "Piano" is the official name is not established.
The panel's contents — number of keys, note names, key layout, and whether the keyboard is fixed or changes.
The mapping — how octave numbers pair with light colours, sequence length, and the row contents themselves.
Behaviour — whether the module uses audio at all, what the reset action is, which input is accepted, and whether the sequence changes between modes.

A precise-looking note list, colour table or melody found on a fan page is not evidence for any of the above. Copying a standard sequence from another game, or promoting a community list into an official manual row, is the exact shortcut that produces an avoidable failed defusal. One related count also stays open: the launch announcement's "14 new modules" wording (11 standard plus 3 CHAOS) does not prove that 14 is the total module count, and it says nothing about this panel's rules.

For the same reason, the loop described above should be treated as published guidance for the launch version (September 2026) rather than as a table you can act on. The in-game defusal manual is always the final authority.

Testing the Panel Yourself

The reliable way to turn this page into rules is to record the panel yourself. A reusable entry should capture:

The exact in-game title and the build version.
The mode and the visible state — light colour, octave readout, keyboard markings.
The role perspective the evidence came from (what the Blind feels versus what the Deaf sees).
The action taken and the result — including failures, not just the runs that worked.

Use a community page as a research lead, then compare every note and every state against the current build. Do not throw away contradictory evidence because a sequence worked once; a single success can be a coincidence, and a single failure can be a misread octave.

Until then, the safe team practice is the one that needs no table: ask the visible player to describe the interface, have the manual reader relay only verified information, and let the interacting player repeat the intended sequence before entering it. That is a team recommendation, not a confirmed Piano mechanic — but it is the only thing on this page that works even if every unverified detail above turns out wrong.

One practical note for drilling the readout: the demo does not start below three players, and a third-party mod (Bytonian Mods) exists that lets a single player start a run, hot-swap between the Blind, Deaf and Mute roles, and freeze the timer. It is an unofficial tool, not a game feature — but it is the cheapest way to rehearse the octave readback on your own.

All modules and their evidence status — where Piano sits in the module list.
The module guide — the per-module callout procedure, including what to carry as one packet.
Reading the defusal manual — the input-packet habit that makes a lookup panel solvable.
How to play — role assignment and the callout order for a first run.

Sources

The loop above reflects community coverage of the launch version (September 2026) and may shift after patches. Details marked Unconfirmed were reviewed on September 21, 2026.