BOMBANANA! Roles Explained

BOMBANANA! splits bomb information across three players who cannot communicate freely. No role can solve a module alone — the information is physically separated. This page covers how the roles divide that information, how to assign them before your first session, and where the chain between them breaks. It does not replace the individual role guides — it covers what only the hub can cover: cross-role handoffs and the agreements that require all three players to align.

The information triangle

Information in BOMBANANA! moves around a loop, one leg at a time:

Blind Monkey reports by voice → Mute Monkey hears and reads the manual → Mute signals Deaf Monkey → Deaf speaks the answer → Blind Monkey acts

Each leg depends on the one before it and cannot be skipped. Understanding what each role can and cannot do explains why — each role's gap in the Cannot-do column is exactly what makes the next role in the loop necessary. Note the two spoken legs land on different listeners: Blind's tactile report is heard by Mute, while Deaf's answer is heard by Blind.

Role	Can do	Cannot do
Blind Monkey	Touch and feel the bomb; execute inputs; hear the team; report tactile findings by voice	See colors or screen text; read the bomb's visible state
Mute Monkey	Read the manual; see the bomb; hear the whole team, including Blind's spoken reports	Speak; use voice chat in any direction
Deaf Monkey	See the bomb; speak to Blind; read Mute's gestures	Hear voice chat; receive audio corrections from either teammate

Deaf Monkey is the only role that receives input from one direction (Mute's gestures) and transmits to another (Blind's ears) simultaneously, with no fallback channel if either breaks. This is why Deaf carries the most sustained load, and why diagnosing failures usually starts there.

First-session role assignment

Assign roles before the timer starts — not after the first explosion. The cleanest method when no one has experience is exclusion:

1. Exclude the impulsive player from Blind Monkey. Blind Monkey's entire job is waiting for a confirmed instruction before acting. A player who tends to act on partial information will break the act-gate repeatedly. Give that player Mute or Deaf instead.
2. Exclude the verbose player from Deaf Monkey. Deaf Monkey's output goes directly to Blind, who cannot ask for a shorter version. A player who explains rather than states will overload Blind with more information than they can act on. Give that player Mute.
3. The remaining player takes Deaf Monkey.

This is not optimized assignment — it is functional assignment, which is what the first session needs. If the group has one player with prior experience in a specific role, put them there and use exclusion for the other two. Do not move an experienced player to an unfamiliar role for variety in the first session; variety comes after one successful defusal.

Where the chain breaks

The chain has two handoff points. They fail for different reasons, and diagnosing which joint broke is more useful than restating "communication failed."

Handoff	Common break cause	Who absorbs recovery
Mute → Deaf	Gesture misread, or Deaf relays a guess before Mute's signal fully completes	Deaf — must re-read the gesture or ask Mute to repeat while holding bomb state in memory
Deaf → Blind	Blind acts before the callout is complete, or the game state changed between Deaf's read and Blind's action	Both — Blind stops and holds; Deaf re-confirms the instruction

The Mute→Deaf break is invisible to Blind until a wrong input happens. The Deaf→Blind break is stoppable — but only if Blind follows the act-gate covered in the Blind Monkey guide. That guide treats the act-gate as its central concept precisely because this handoff is the last point where the chain can be caught before an input lands.

The temptation at the Mute→Deaf joint: Deaf has enough context to guess the manual answer, so they relay the guess rather than waiting for Mute's full signal. From Deaf's perspective, the guess looks safe because they can see the bomb state and the answer seems obvious. From Blind's perspective, a guessed callout and a confirmed callout sound identical. A reasonable default — though unconfirmed as an in-game rule — is for Deaf to treat any incomplete gesture as a hold signal rather than as a partial confirmation to fill in.

What no single role can set up alone

Each individual role guide covers per-role pre-round setup. These four items require all three players to agree — no role can lock them in unilaterally.

1. Module reading order. Decide whether Deaf calls modules left-to-right, by urgency, or in a fixed sequence. Without a shared order, Deaf and Mute may work on different modules simultaneously, creating parallel chains that cross and invalidate each other's answers.
2. Mistake-budget callout ownership. Decide that Deaf announces the mistake counter whenever it changes — not only when asked. Blind cannot see the counter; Mute may miss it under manual pressure. Deaf holds the only clear visual readout and is therefore the natural owner. This is a reasonable default inferred from role constraints, not a confirmed in-game rule.
3. Abort signal. One signal that means "stop everything, restart the round" — distinct from any per-module stop signal. Without it, a spiraling session has no clean shared exit that all three roles recognize simultaneously.
4. Who reports which facts. Blind hears the team and speaks tactile findings — wire count, order, dot patterns — straight to Mute, who hears them directly. Deaf supplies the visual facts Blind cannot sense: colors, LED states, the mistake counter. Agree that both report to Mute, so Mute never opens a manual page on half the picture.

Role rotation

Rotating roles teaches each player how the other sensory limitations feel from the inside. Deaf Monkey is the role teams most often want to leave and least often rotate out of — because building a working chain around one Deaf player is hard, and handing that role off disrupts the chain. Rotate it deliberately rather than by default.

Situation	What to do
First session, no experience	Keep roles for at least two full attempts. Most first-attempt failures are setup problems — not role problems — and one attempt is not enough to know whether the role or the setup is causing the failure.
Ready to rotate for learning	Rotate one position: Blind → Mute → Deaf → Blind. Predictable order; no one starts from scratch simultaneously.
One player is struggling	Use the "where the chain breaks" section above to identify which handoff is failing before rotating. Rotating without fixing the underlying habit usually moves the problem rather than solves it.

Deaf Monkey accumulates pressure faster than the other two roles over extended play. It is the only role that receives input (Mute's gestures) and transmits output (spoken callouts) at the same time, with no fallback if either channel fails. Blind waits when uncertain. Mute has the manual as a stable reference. Deaf has neither. A reasonable default — though not an in-game rule — is to treat Deaf as the rotation priority after every few sessions, not only when the player asks.

Which role guide addresses your current problem

Use this table if your team has already had one session and knows where the chain is breaking.

Current team problem	Read first	The habit to fix
Someone acts before the team confirms the instruction.	Blind Monkey guide	Wait for all three act-gate conditions before touching the module.
The manual answer is not reaching Deaf cleanly.	Mute Monkey guide	Add a discard-last-gesture signal and a still-looking signal to the pre-round vocabulary.
Deaf's callout is wrong but nobody catches it before Blind acts.	Deaf Monkey guide	Establish a one-instruction-at-a-time protocol and a non-voice correction path.
Everyone talks at once and callouts get lost.	Team Communication guide	Use a fixed callout sequence: module name → position → details → answer → confirm → act.