BOMBANANA! Mute Monkey Guide

The Mute Monkey holds the defusal manual and cannot speak. You know the answers — and you can never say them. You see only the manual, not the bomb, so everything you work from arrives as gestures and described state from the Deaf. Mental load is highest on you: you must convert colors, numbers and directions into the correct manual branch, then signal the answer back through one silent channel. If the team is a communication chain, you are the knot.

What You Own

The defusal manual — every module's rule pages.
The decision — you pick the branch, the target color, the final key. Nobody guesses on instinct while you hold the manual.
The answer relay — you signal the result to the Deaf, who speaks it to the Blind.

You cannot see the bomb, so your first job on any module is to know which module you are solving and what state it is in — only then does the manual page mean anything.

Find the Right Page

The universal callout exists to feed you:

The Deaf leads with module name + position — that is the page you open.
You then need the specific facts the rule branch uses: count, colors, LED, stage, sound, Braille value.
Ask targeted yes/no questions when a fact is missing. A nod costs a second; a wrong branch costs the bomb.

Remember the Direction table uses Braille numbers 1, 2, 3, 4, 5, 6, 7 and 9 (no 8), the Calculator is two stages (raw result, then LED + odd/even), and Switch needs every state confirmed before ENTER.

Package One Answer

Do not dump the whole rule at the Deaf. Package the one action the Blind needs:

✅ "Press 5." / "Third cable from the left."
❌ "So if the light is red and there are four wires and the result was odd, then the target is green, which means…"

The Deaf cannot hold a rule chain under timer pressure — they can only hold one clear instruction. If a rule has branches, ask for the missing fact instead of narrating every branch aloud.

The Gesture Dictionary

Agree these before the timer starts, ideally as a team:

yes / no / wait / repeat / go-back — the control gestures.
0–9 — number signals. Numpad mapping works well: 2 = down, 4 = left, 6 = right, 8 = up.
Colors — pre-assign numbers to colors before the round.

Keep the dictionary small. Expanding it mid-run is how signals get confused; add a gesture only when you know exactly which miss caused it.

When You Are Not Sure

Signal "repeat" instead of guessing. The Deaf re-describes the state; you re-check the branch. A clean reset is a successful call, not a failure.
Say "unknown" through the chain. If the Blind is unsure of a Braille value, the correct response is to re-scan, not to have the Deaf invent a number.
The priority trap on Calculator: a result can be odd and greater than five. You hold the LED color and the manual — you decide the branch, never the Blind on instinct.
After any mistake, treat the packet as expired. The input may have changed the light, number or stage; re-read the module from scratch.

Common Mute Mistakes

Reading too much at once and forcing the Deaf to memorize a rule chain.
Skipping confirmation because a module looks simple.
Changing gesture names mid-run — a shape with three names is a failed relay.
Answering before the state is complete — an answer to the wrong branch is worse than no answer.
Letting the Blind act on a remembered answer — the panel may have changed since the last correct lookup.

Best role for new players? Some teams put their most comfortable rules-reader here from the start; others argue the Mute is the hardest to do well under pressure. Start on Deaf or Blind to learn the loop, then take Mute when you want the deepest challenge — and consider it the role that most rewards practice.