BOMBANANA Soundboard Module Guide and 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 pattern table, Campaign appearances, timer, and mistake behavior remain unverified. Do not treat this page as proof that Soundboard appears in a specific level.

Quick answer

The BOMBANANA Soundboard module has a 3 by 3 grid of nine buttons. Press or test the buttons one at a time until one produces the sound, then read only that button’s Braille number and color. Use those two clues in the current manual to find the marked grid pattern, repeat the positions, and confirm before the bomb handler presses them.

The search step and the pattern step are different jobs. A permanent answer table and every full-release mapping are To be confirmed. The manual guide and communication guide help the team keep the two phases separate.

Search the nine-button grid

Start by naming the Soundboard module. Number the grid positions in a fixed order before testing them. Move through the nine buttons one at a time until one button produces the sound. That button becomes the source of the lookup.

Do not read every Braille number and color as if all nine buttons were part of the final answer. The collected procedure uses the sounding button to identify which state should be resolved. Keeping the search short prevents a team from mixing clues from different controls.

Read the sounding button

Once the sounding button is identified, report its Braille number and color. The player who sees the color and the player who can read or feel the number should keep those fields distinct. The manual reader repeats the pair before choosing the grid pattern.

The result is a set of grid positions, not a color name alone. Return each position in numbered form so the bomb handler can map it to a physical button. If the team loses track of the sounding button, stop the lookup and search again instead of guessing from memory.

A safe Soundboard procedure

1. Name the module and agree on the grid numbering.
2. Test buttons one at a time until one produces the sound.
3. Report the sounding button’s Braille number.
4. Report its color.
5. Let the manual reader resolve the pair into marked positions.
6. Repeat the complete position list and confirm before pressing.
7. Report whether the grid clears, changes, or expects another pattern.

The three Monkey roles guide is useful here because the grid combines physical input, visible color, and rule lookup. One player should not silently merge all three jobs.

Common failure points

The biggest error is skipping the search and trying to solve from the whole grid. Another is losing the identity of the sounding button while describing the other eight. A third is returning a pattern without a position convention.

When two voices overlap, use the agreed stop signal and restart with the module name. When the panel changes, discard the old pattern. The next state can use the same layout while asking for a different answer.

Evidence boundary

The current collected procedure supports the 3 by 3 layout, the sounding-button search, and the Braille plus color lookup. It does not verify a permanent public table for every pattern, exact Campaign placement, timer, mistake allowance, or update-specific variation. Those details remain To be confirmed.

Use the live in-game manual as the authority for a current bomb. A community pattern list can help with vocabulary, yet it should not replace a fresh lookup. The Modules database keeps this page connected to the other workflows without turning an unverified table into a promise.