BOMBANANA WikiBOMBANANA Roles
BOMBANANA has three roles, and each one is missing something different. Blind has the bomb. Mute has the rules. Deaf keeps those two sides synchronised. Choose each role by the job it actually has to do, not by who talks the most.
What each seat controls
| Role | Controls | Best fit | Time to reconsider |
|---|---|---|---|
| Blind | Reads Braille on the bomb, finds the active module by touch, performs the final physical input | A precise, calm player who can report spatial information clearly | Correct calls keep arriving, but the wrong object is still being pressed, cut or entered |
| Deaf | Sees the bomb state, reads the Mute's gestures, carries information both ways | A player who can hold several short facts without mixing positions, colours, numbers or stages | The team reaches the right rule but keeps attaching the answer to the wrong object or an old state |
| Mute | Reads the manual, turns the current bomb state into a usable answer | A fast rule reader who can turn a complex lookup into one clear gesture | The lookup is correct, but the other two regularly cannot read the gesture |
Deaf is not "the talker" — that seat is closer to short-term memory management: which module are we on, which value belongs to which position, and did the panel change after the last action.
On Blind: end the sentence with something your hands can do
A colour can be the right answer on the manual side and still be an unfinished instruction on the bomb side. "Blue" is not enough if there are several cables. "Second cable from the left" is. The same style works everywhere: top-right button, press Up, third slider down, enter 57, second key.
A more basic failure happens early: sometimes the Blind has not entered the correct interaction view yet. If nothing seems clickable, solve the physical access problem before asking for more rules.
On Deaf: a naked number acquires the wrong meaning
One useful failure started with a single signal — "Two." — read as second control → down. The two was part of a question about which object was being discussed. Stop sending naked numbers. Say "Slider two" first, wait for acknowledgement, then the direction. Keep the object attached: "Second is blue.", "Top-right is four."
On Mute: finish the lookup before the hands are useful
The manual can hold the right answer while the team still cannot use it. The most literal version is trying to gesture with the manual still raised — the book blocks the exact hand movement the Deaf is waiting to read. The rhythm is read → decide → lower the manual → gesture. The worst question to receive is "What do we do?"; the best is a complete state you return one action for.
The six signals
Nod / thumbs up (yes), shake / thumbs down (no), finger count (identify a slot), repeat (send one item again), reset (rebuild the whole state), hands off (Blind waits). The distinction that matters most is repeat versus reset: one missing fact means repeat; conflicting memories mean reset.
When to swap seats
One explosion does not rotate all three roles — repeated failure in the same place does. If the Mute reaches the right rule but nobody can read the gesture, try someone else on the manual. If the Deaf keeps combining one stage's value with another stage's colour, put the strongest information manager in the middle. Some failures are shared-protocol problems — two definitions of "left", or "repeat" and "reset" meaning the same thing — and you fix the convention before moving players.
See also how to play and multiplayer.
Related guides
Multiplayer
Three copies, no friend pass, and how joining works.
Read guideBomb Manual
Every module, what it shows, and how to call it out.
Read guide