Roles & Communication
The three monkeys don't have equal access to one shared conversation. Useful information may have to cross more than one player, and the form that leaves the manual is not always the form Blind needs at the bomb. That extra transformation is why communication mistakes become a real game system.
The three seats
Blind
Controls: Reads Braille on the bomb, finds the active module by touch, performs the final physical input.
Best fit: A precise player who stays calm while locating controls and can report spatial info clearly.
Rethink when: Correct calls keep arriving, but the wrong object is still being pressed, cut, moved, or entered.
Deaf
Controls: Sees the bomb state, reads Mute’s gestures, carries information in both directions.
Best fit: A player who can hold several short facts without mixing positions, colors, numbers, or stages.
Rethink when: The team reaches the right rule but keeps attaching the answer to the wrong object or an old state.
Mute
Controls: Reads the defusal manual and converts the current bomb state into a usable answer.
Best fit: A fast rule reader who can turn a complicated lookup into one clear gesture or short sequence.
Rethink when: The lookup is correct, but the other two players regularly cannot tell what the gesture means.
A common mistake: giving Deaf to whoever "talks the most." That seat is really short-term memory management — which module are we on, which value belongs to which position, did the panel change after the last action?
On Blind: end the sentence with something hands can do
A color can be the correct answer on the manual side and still be an unfinished instruction on the bomb side. Prefer physical calls:
- "Second cable from the left" — not just "Blue"
- "top-right button", "press Up", "third slider down", "enter 57", "left selector", "second key"
Blind also becomes a source of information via Braille on the bomb — report what only you can read first, then perform the answer that comes back. Mixing those two moments is how a clean answer becomes a strike.
On Deaf: a correct number can acquire the wrong meaning
Instead of a naked "Two," keep the object attached: "Slider two," "Second is blue," "Top-right is four," "Third slider, down." The call gets slightly longer, but the chance of binding a correct value to the wrong object drops sharply.
On Mute: finish the lookup before hands help
Keep a simple rhythm: read → decide → lower the manual → gesture. A question like "What do we do?" forces Mute to identify the module, find missing fields, locate the rule, solve it, and mime the reasoning — far more than receiving a complete state and returning one action.
A 6-signal vocabulary
Settle a tiny, consistent signal set before the timer gets loud:
| Signal | Meaning |
|---|---|
| Nod / thumbs-up | Yes. Keep that interpretation. |
| Shake / thumbs-down | No. Do not act on that. |
| Finger count (1st/2nd/3rd…) | Identify a physical slot before giving the value or action attached to it. |
| Repeat | Resend the last item — only one number/color/position was missed. |
| Reset | Throw away the current call and start this state again. |
| Hands off | Blind waits. The answer is incomplete, disputed, or may belong to the previous stage. |
The most important distinction is repeat vs reset. If everyone still agrees you're on the same panel and only one number was missed, repeating is efficient. If one player thinks the panel advanced, another still has the old color in mind, and nobody can say whether the previous action was accepted — that's a reset.
Left and right fail across coordinate systems
Direction exposes this immediately. The convention is Blind's perspective while facing the bomb. Freeze it — switching from Blind's left to the viewer's left halfway through makes every later directional call suspect. For a grid, put the location before the value ("Top-right, four").
A solved rule is useless once it belongs to the previous state
After an input, watch the panel before another answer starts moving. Three outcomes: the module clears; the module changes (discard old values); nothing changes (decide incomplete/incorrect/waiting). This matters most on modules that change state mid-solve, like Calculator.
Swap the seat that keeps producing the same mistake
One explosion doesn't mean rotate all three roles — repeated failure in the same place does. If Mute reaches the right rule but nobody reads the gesture, try someone else on the manual. Changing Blind doesn't fix two definitions of "left"; changing Mute doesn't fix a team where "repeat" and "reset" mean the same thing. Repair the convention before moving the players.