BOMBANANA! Module Guide

This is the per-module defusal manual: how to read each panel, what to call out, and in what order. It deliberately avoids inventing answer keys where the public record is thin — process beats memorized answers, because a confidently wrong table gets teams blown up.

The Universal Callout

Learn this one structure and use it every single time:

Saying the module name and position first is the part beginners skip, and it is the most important bit. The Mute cannot find the right manual page without knowing which module you are on, and several pages involve colors and lights, so "green, blue, red" on its own is useless. A good defusal team sounds boring and robotic.

Cable / Wire Module

The classic, and usually your first module. The solve is:

count → light → target color → position from the left → cut

The Deaf calls the number of wires, then the colors from left to right, then the LED color. The Mute matches that to the manual and signals which color is the target. The Blind repeats the target back, gets a confirm, and cuts one wire.

The trap is assuming every wire module has the same number of wires — 3-cable and 4-cable boards use different rule sets, so always lead with the count. Verified mapping:

The table stops at a target color — the current cable order turns that color into a physical position. A clean wire callout sounds like: "Wires, top right. Four wires. Left to right: green, blue, red, yellow. Red LED. Waiting for the cut." And the final instruction is a position, not just a color: "Second cable from the left. Blue."

Worked example: 3 cables, Green light, order Green / Blue / Yellow. 3 + Green → target Yellow. Yellow is third from the left. Final call: "Third cable from the left. Yellow."

If the target color does not appear exactly once on the panel, stop and re-read the whole state instead of guessing.

Direction (D-pad)

Four arrow buttons around a dot cluster, plus a colored light. The input is compact:

active light + current Braille number → one direction (Up, Down, Left, Right)

The Deaf calls the active LED color and the center value — a number, or a Braille value the Blind reads by feel — then waits on the manual for a direction. The verified Direction table uses Braille numbers 1, 2, 3, 4, 5, 6, 7 and 9; if you think you are seeing an 8, re-read the pattern before pressing anything.

The more dangerous problem is not the lookup — it is two players meaning opposite things by "left". Lock in that directions always mean the Blind Monkey left and right. If you input wrong and the module changes, call the new state fresh rather than reusing the old one.

Braille

Braille is not a separate panel — it is the Blind Monkey's reading channel, and it appears inside other modules. The bomb has a diegetic Braille system built into it, and the Blind player reads the raised dots by feel while staring at a near-black screen. Where it shows up:

• Direction: the center value is a Braille number the Blind reads by touch.
• Calculator: the nine keypad keys are Braille-labelled.
• Switch Panel: a Braille number sits beneath each switch.
• Piano: the keys carry Braille dots.

The callout rule is simple: the Blind reads the dots and relays them as plain numbers, never as guesses about what they might mean. Remember the Direction table uses 1, 2, 3, 4, 5, 6, 7 and 9 — there is no 8, so if you think you feel an 8, re-read the pattern before anyone presses anything.

Calculator (Numpad / Maths Module)

The nasty one, and where most teams lose the most time. It is a two-stage module:

1. Stage 1 — equation. The panel shows an equation (for example 60 − 27 =) next to a nine-key keypad. No colored LED is needed yet. Solve it and enter the raw result. The raw result advances the module.
2. Stage 2 — final key. After the result is accepted, a light appears. Now the Mute uses the new LED color plus whether the raw result was odd or even (and, where the manual asks, greater than or less than a threshold) to pick the final single-digit key. The final key finishes the module.

Three traps:

• The answer to the sum is not always the number you press. Treat the maths as step one and wait for the manual's final instruction.
• The keypad is jumbled. Press the number itself wherever it appears, not the position it would sit in on a normal keypad.
• The priority trap. A result can be both odd and greater than five at the same time. The Blind never picks the branch on instinct — the Mute, holding the manual and the LED color, decides. The handler reports the full state: "Result is 67, odd, greater than five, yellow LED. Waiting for the final number."

If the equation result was accepted and the panel is still active, do not enter the same number again — read the new LED and continue from stage two.

Switch Panel

Four switches, four colored lights above them, Braille numbers beneath, and one ENTER button. Switches are more dangerous than wires because you usually need several states correct before a single ENTER locks them in.

The Deaf calls the light-color order across the top and the full digit string; the team resolves each switch up or down in turn, repeating each state as they go. Confirm every switch before anyone touches ENTER — the most common switch-panel death is hitting ENTER with one uncertain 50/50 still unresolved. This is why you agreed a go-back signal in setup: if an earlier switch is wrong, use it and revisit that exact switch instead of mashing ENTER.

Symbol (Symbol Wheel)

A rotating pointer or wheel with four symbols — hourglass and triangle shapes are mentioned in footage — plus colored buttons. Blind rotates the knob until one symbol makes a sound, then presses a colored button; the sequence repeats per stage. Status: Observed in launch playthrough footage — the manual page has not been shown on camera, so the exact rule table is Unconfirmed. Team tip: agree on stable names for every shape before the run. A shape with three different names is a failed relay waiting to happen.

Piano

A short keyboard with Braille dots on the keys and a colored light that changes color per attempt. Blind plays the note sequence the manual gives. Status: Observed in footage; manual page not verified, so the exact procedure is Unconfirmed. Carry the light color, the Braille labels and the note order as one packet — describing everything visible at once makes this module harder than it is.

Soundboard

Rows of buttons with three colored lights; only one button plays a sound. Find the sounding button first, then press the positions the manual gives. Status: Observed in footage; manual page not verified. The expensive mistake is describing the whole grid before identifying which button actually sounds — search first, then resolve.

Color Sliders

Four vertical sliders in red, green, yellow and blue; Blind pushes each up or down per instruction. Status: Observed in full-game footage (seen at level 2); the manual page was not shown on camera, so treat exact combinations as Unconfirmed and call sliders strictly left to right.

Chaos

Chaos modules are not puzzles to solve — they are hazards that compete for attention while you solve. Lefto lists three CHAOS modules designed to keep the Blind Monkey busy. Only one is verified on footage:

• Rising Slider: a single slider marked with a yellow warning triangle that creeps upward on its own. Blind keeps pulling it back down until the bomb is defused.
• Chaos modules #2 and #3: announced, but not yet seen in verifiable footage — Unconfirmed.

The practical rule: stabilize the danger first, then return to the defusal panel and re-confirm its current state before acting on any older answer. A correct lookup from before the interruption may already be stale.

For every module on this page, the universal callout still applies: name the module, report only the current state, wait for the manual answer, repeat back, confirm, act.

After Any Mistake

When an input goes wrong, stop. Panic inputs stack mistakes faster than calm retries. Call a full stop, then re-read the entire module from scratch — a wrong input can change the LED, the number, or the stage you are on. The answer that was right ten seconds ago may not be any more.

Treat every successful input as a checkpoint. After a press, cut or accepted Calculator result, check: did the module clear? If yes, drop every value attached to it. If no, read the current panel again before using another answer. As teams get faster, stale answers become more dangerous than slow lookups.

Sources: whisperofthehouse wire guide, whisperofthehouse module solver, Mobalytics module and callout guide, bombananaguide.wiki modules.