MODULE / DEFUSAL / 07
Find the only button that produces sound, then use the Braille number and color from that one cell.
By BOMBANANA! Wiki editors · Updated September 3, 2026 · Full-release guide
PROCEDURE
Probe one cell at a time until the sounding button is found.
Discard descriptions of the other eight cells.
Read the target cell’s Braille number and color.
Return every required press with fixed coordinates such as TL, TC, and TR.
BOMBANANA! PLAYER GUIDE
Learn how to identify the Soundboard panel, collect its required inputs, move the answer through Blind, Mute, and Deaf, recover after Chaos, and practice without memorizing an expired state.
The BOMBANANA Soundboard module is a defusal panel classified as medium. Find the only button that produces sound, then use the Braille number and color from that one cell. Only one cell produces sound. Its Braille number and color select the answer, which should be returned as fixed coordinates on the 3×3 grid. Observation, lookup, relay, and action give each monkey a checkable stage. 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.
Soundboard has fixed Campaign appearances in Level 11, and Level 12, beginning at Level 11. A fixed appearance names the family, never its live answer. Start with the clearest shared state, then move toward the most demanding procedure. Early confirmation establishes rhythm without sacrificing a volatile panel. Review the BOMBANANA procedure pre-play and recollect values after loading.
Open with “Soundboard” so Mute reaches the correct BOMBANANA manual section. Its required packet is Sound-producing button, Its Braille number, Its color, 3×3 coordinates. 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. 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.
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. 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. 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. 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.
The compact procedure is: Probe one cell at a time until the sounding button is found. Discard descriptions of the other eight cells. Read the target cell’s Braille number and color. Return every required press with fixed coordinates such as TL, TC, and TR. 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 “Soundboard.” 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. This predictable BOMBANANA loop exposes skipped steps.
Describing all nine cells overloads the channel, while vague positions such as “top side” create ambiguity between corners and the center. Prevent it by attaching every answer to the Soundboard module, current stage, and physical position. A color without a control, a direction without a stage, or a sequence without numbered places is incomplete. Close every action with the observed result—cleared, unchanged, or new stage—so nobody silently carries an old answer into the next exchange. 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. A clean restart has three markers: interruption resolved, original module named, and fresh input acknowledged. Missing any marker leaves roles at different points. 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. Separate what the bomb shows from what the manual concludes. That boundary makes a bad observation easier to locate without reopening every earlier decision. Select a row only after every input is attached to the current stage.
If BOMBANANA changes Soundboard, 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. Use physical props or drawn panels to verify viewpoint language. If a teammate points to the wrong location, revise the phrase before returning to Campaign.
Practice the TL, TC, TR, ML, MC, MR, BL, BC, and BR coordinate set until every player can point to a called cell without translation. 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 “Soundboard,” and collect current fields. Use “hands off” as a state-control command, not criticism. Neutral language makes it easier to stop a nearly completed action when the evidence changes.
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. Replay the longest exchange once without a timer and once under pressure. Compare where vocabulary changes, because that is usually where reliability disappears. Shared understanding is more useful than one player memorizing a table.
Before touching the BOMBANANA Soundboard panel, name the module, identify the stage, collect Sound-producing button, Its Braille number, Its color, 3×3 coordinates, 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. 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.
If Chaos interrupts Soundboard, 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. A clean restart has three markers: interruption resolved, original module named, and fresh input acknowledged. Missing any marker leaves roles at different points. Labeled repetition is safer than combining correct fragments from different BOMBANANA moments.
