Tools

BOMBANANA Say the module, then wait

One loop for every bomb: module, position, details, manual answer, repeat-back, confirm, then a single input.

Last updated:

Callout Sheet

Print this page or pin it. BOMBANANA! is not lost on hard puzzles so much as it is lost on overlapping sentences. Mute Monkey holds the manual and cannot speak. Deaf Monkey can see and speak but cannot hear the in-game voice channel. Blind Monkey has the only hands on the case and cannot see colors or screen text. The communication guide explains why that relay exists. This sheet is the script you actually say.

Launch added fourteen new modules and three CHAOS pieces that keep Blind Monkey busy, plus hazards that can black out or shout over the van. The loop does not change when the art is hand-painted. If a new module appears in Campaign, still name it, still wait, still confirm. Unofficial lookup tables go stale; the sentence order should not.

The loop (never skip a step)

  1. Module. Name the family first so Mute can open the correct manual page: wires, direction, numpad, switches, or whatever the bomb actually spawned. “This one” is not a name.
  2. Position. Clock or corner: top right, bottom left, the panel under Blind’s left hand. Two identical wire rows will kill you if you mix them.
  3. Details. Only the facts that family needs. Dumping extra colors “just in case” is how Mute looks up the wrong row.
  4. Manual answer. Mute looks it up and gestures. Nobody else invents a rule because the timer is loud.
  5. Repeat-back. Blind (or Deaf, if Blind must keep both hands on a hold) restates the action in the same words: “cut second from Blind’s left, blue.”
  6. Confirm. Mute yes-gestures or Deaf says “confirm.” No confirm, no input.
  7. Input. One action. Then report the new state. If the LED changed, you are on a new module snapshot — restart the loop, do not reuse the old answer.

A full-stop phrase belongs in your lobby setup before the bomb arms. When anyone says it, all three mouths (and Mute’s hands) freeze. Then you restart from module.

Gesture dictionary (Mute, and anyone on the wheel)

Launch gave emotes for everyone, so this dictionary is a team language, not a Mute-only secret. Agree the mapping in the lobby. Do not change it after a strike.

  • Yes — proceed / confirm / that is the wire.
  • No — stop / wrong page / do not cut.
  • Wait — Mute is still on the table; Blind’s hands off the case.
  • Repeat — say the last details pack again, from count or equation, not from the last word.
  • 0–9 — digits. Decide whether 10 is “one then zero” or a two-hand sign before a numpad appears. Never mime a whole equation if the sheet already asks Deaf to speak the equation aloud.

If your wheel also has a slap or a rude emote, that is comedy, not a fifth answer. Keep answers inside yes / no / wait / repeat / digits.

Wires

Call count, then left-to-right colors, then LED. Never lead with a color. Three-wire and four-wire panels can live on different manual rows; a team that assumes “there are always four” cuts the wrong cable.

Example pack: “Wires, top right. Four wires. Left to right: green, blue, red, yellow. Red LED. Waiting.” Mute gestures the target. Blind repeat-backs color and position from Blind’s own left. Cut once. Report.

Do not recut “the other blue” to be helpful. If the module is still live, restart the loop with a fresh count — a strike can change the LED.

Direction

Call LED plus braille or center value. Blind is the source of braille; sighted players do not guess dots from a silhouette. Direction outputs must use Blind’s left and right, not the TV’s left, not Deaf’s screen-left if Blind is facing the other way.

Example pack: “Direction, bottom. Green LED. Blind reads five. Waiting on a direction from Blind’s left.” If a wrong press changes the LED or the center value, throw the old instruction away.

Numpad

Call the full equation spoken aloud, then odd or even, then LED. If a greater-than or less-than branch matters, include that flag too — but Mute, holding the manual and the LED, picks the winning branch. Blind must not decide “it is odd so I will just hit 3.”

The keypad is jumbled. Press the glyph wherever it sits. Do not press “the bottom-right key because that is where 3 lives on a phone.” Repeat-back should sound like “press the three glyph, not the third pad.”

The raw sum is often not the key. Treat maths as one detail in the pack, then wait for Mute’s final number.

Switches

Call the full light order and all numbers before anyone touches Enter. Switches are a sequence, not a coin flip. Resolve each switch up or down with a repeat-back, then lock the board in one Enter.

The usual death is Enter with one 50/50 still live. If an earlier switch was wrong, use Repeat and go back to that switch. Do not mash Enter to “see what happens” — Custom may give you more strikes than Campaign, but the habit will betray you on Endless.

After a strike, and how to practice

Stop. Full-stop phrase. Re-read the entire module. LEDs, digits, and stages can change after a mistake. Then one module at a time until the case is clean. Parallel talk (“I’ll describe the other panel”) is how Blind cuts a wire Mute was not looking at.

Practice on Custom with hazards off and a long timer, using the modules guide as the family list. When CHAOS modules spawn, keep this same loop; they exist to occupy Blind, not to license panic inputs. Role jobs: Mute, Deaf, Blind. Controls binds: controls. Hosting: lobby setup. Hardware: system requirements. More tools: the tools hub.

FAQ

Frequently Asked Questions

Quick answers for three-player bomb runs.

What is the callout order?

Module, position, details, manual answer, repeat-back, confirm, then one input. Skipping confirm is how most demo bombs ended.

Which wire facts does Mute need?

Count first, then left-to-right colors, then LED. Never assume every panel has the same number of wires.

Whose left and right do we use on direction?

Blind Monkey's left and right. Deaf's screen-left is the usual wrong answer. See also the Blind Monkey page.

Why not press the numpad like a phone?

The glyphs are jumbled. Press the number glyph wherever it appears, after Mute settles odd/even and LED from the full equation.

When do we hit Enter on switches?

After the full light order and every number are called, and every switch state is confirmed. Enter is a lock, not a guess.

Is this the in-game manual?

No. Mute still reads the bomb manual. This sheet only standardizes what the other two say. Pair it with the communication guide.