BOMBANANA Piano module guide

The BOMBANANA Piano module is a defusal panel classified as medium. The Braille scale and LED determine four notes. Number and transmit the entire sequence as one packet. A Braille scale and LED color produce a four-note sequence. The sequence must retain both note identity and position from lookup through performance. Observation, lookup, relay, and action give each monkey a checkable stage. Read stable values first and changing values last. The order reduces the chance that a live state expires while Mute is still searching a rule branch.

Piano has fixed Campaign appearances in Level 9, and Level 10, beginning at Level 9. A fixed appearance names the family, never its live answer. Queue work by state sensitivity, not visual size: protect anything changing or cumulative, then clear the shortest fully understood panel before opening a long route. Review the BOMBANANA procedure pre-play and recollect values after loading.

Open with “Piano” so Mute reaches the correct BOMBANANA manual section. Its required packet is Braille scale from 1 to 7, LED color, Four-note sequence. Read those fields in their displayed order and attach numbers or coordinates wherever position matters. If a value is uncertain, name the missing field instead of supplying alternatives. Use numbered positions during the first scan, because a later color, symbol, or direction is only useful when the team can attach it to one control.

Keep observation separate from interpretation: Deaf describes visible state, Blind contributes tactile or Braille state, and Mute performs the rule lookup. An observer who suggests an answer too early can anchor the group to a previous run. Close every action with the observed result—cleared, unchanged, or new stage—so nobody silently carries an old answer into the next exchange. For this BOMBANANA panel, familiarity never replaces a complete current packet.

For this BOMBANANA module, Deaf begins with its name and visible values in stable order. Blind adds tactile information while keeping clear of actionable controls. Mute checks the matching branch and returns only the requested result; Deaf translates that result into Blind’s viewpoint; Blind repeats, waits for confirmation, acts once, and reports the outcome. Use Blind’s viewpoint for the final instruction even when Deaf sees the panel from another angle. Viewpoint translation belongs before, not during, the movement.

The compact procedure is: Read the Braille scale and LED. Mute finds the four-note sequence. Transmit the notes as positions 1 through 4. Blind repeats the full packet, then plays it in order. The pace may slow, but the fields should retain their order. If Mute signals missing data, return only that field unless a full reset is requested. A changed stage expires the old packet and restarts at “Piano.” A role that notices missing context should stop the chain immediately. Repairing one field preserves the packet; guessing forces the team to rebuild after a strike. This predictable BOMBANANA loop exposes skipped steps.

Unnumbered notes are easily repeated, dropped, or reordered, especially when the same note appears more than once in the phrase. Prevent it by attaching every answer to the Piano module, current stage, and physical position. A color without a control, a direction without a stage, or a sequence without numbered places is incomplete. Use Blind’s viewpoint for the final instruction even when Deaf sees the panel from another angle. Viewpoint translation belongs before, not during, the movement. Blind should be able to repeat the final action without needing the manual logic.

A second BOMBANANA failure is continuing through uncertainty because the timer is audible. “Hands off” is a neutral correction: recheck one missing field, or request a full reread after a state change. Restart from the module name after an interruption, then re-establish stage and current inputs. Resuming from a remembered answer joins two different moments of bomb state. Classify the issue afterward as observation, lookup, relay, positioning, execution, or interruption recovery.

No trustworthy complete public mapping was found, so the in-game manual remains the authority for the final answer. The cited structured and community sources supporting the callout order were checked September 3, 2026. A BOMBANANA table is a lookup aid, not a replacement for reading the panel. Read stable values first and changing values last. The order reduces the chance that a live state expires while Mute is still searching a rule branch. Select a row only after every input is attached to the current stage.

If BOMBANANA changes Piano, compare live behavior with the source date before blaming the player. Record the exact inputs, result, and stage, then seek an official announcement or reproducible community correction. One failed attempt is not enough to patch a table because execution errors and expired state can imitate a rule change. End practice with one deliberate failure and recovery. A group that only rehearses perfect packets has no shared language for the first real disruption.

Use four numbered note cards. Mute signals all four, Deaf repeats positions one through four, and Blind performs only after the entire phrase is confirmed. Keep the exercise outside a serious Campaign attempt until every role can finish without inventing vocabulary. Then add a timer and one deliberate interruption. Rehearse the full BOMBANANA recovery: hands off, identify the break, declare stability, restart at “Piano,” and collect current fields. After any break, ask whether the panel is unchanged, advanced, or reset. That classification determines whether the old lookup is valid or must be discarded.

Measure packet accuracy before raw speed. Count missing fields, ambiguous positions, premature actions, and failed confirmations; only shorten pauses after the packet is reliable. Rotate BOMBANANA roles so everyone experiences observation, manual search, relay translation, and physical execution. Rotate roles after a clean attempt. Experiencing each information limit helps players request only what the next person can actually observe or communicate. Shared understanding is more useful than one player memorizing a table.

Before touching the BOMBANANA Piano panel, name the module, identify the stage, collect Braille scale from 1 to 7, LED color, Four-note sequence, and convert the manual result into a physical instruction. Repeat the whole action and wait for confirmation; after one input, report whether the panel cleared, changed, or expects another stage. A role that notices missing context should stop the chain immediately. Repairing one field preserves the packet; guessing forces the team to rebuild after a strike.

If Chaos interrupts Piano, stop its callout and clear the emergency first. Treat the packet as expired until every role confirms otherwise; reread the panel, reopen the correct branch, and send a fresh physical instruction. Restart from the module name after an interruption, then re-establish stage and current inputs. Resuming from a remembered answer joins two different moments of bomb state. Labeled repetition is safer than combining correct fragments from different BOMBANANA moments.

• Say “Piano” before reporting any values.
• Collect Braille scale from 1 to 7, LED color, Four-note sequence in a fixed order.
• Keep the live observation separate from the manual interpretation.
• Translate the answer into Blind’s physical viewpoint and confirm once.
• After a state change or Chaos event, discard the old packet and reread.