How to Play BOMBANANA!
The rules of BOMBANANA! fit on an index card, but the first time you actually sit down to play, it doesn't feel that way — it feels like three people yelling numbers at each other while a timer ticks down. That's normal, and it's kind of the point. This guide covers what your first session actually looks like: getting the right number of people in the room, how roles get handed out, the basic loop every bomb follows, a walkthrough of a typical first bomb, and the mistakes almost every group makes on round one.
You need exactly three players
BOMBANANA! does not have a solo mode or a 2-player mode — it's built around exactly 3 asymmetric roles, and the game simply doesn't function with fewer or more. If you're short a person, the honest answer is to wait for a third rather than try to force it; see how many players you need for more on why the game is locked to this number and what your options are if your group is smaller or larger than three.
Role assignment
At the start of a session, each of the three players is assigned one of the three roles — Blind Monkey, Deaf Monkey, or Mute Monkey — each with a different sensory limitation and a different job. Nobody can see the whole picture alone; the entire game is designed so that information has to physically pass between all three of you before anything gets solved. Before your first bomb, take thirty seconds to read through the roles overview so everyone understands going in what they can and can't do — showing up cold to your own role is the single fastest way to waste your team's first attempt.
The basic loop
Every bomb in BOMBANANA!, no matter how simple or complex, runs on the same four-step loop:
- Open the manual. Only the Mute Monkey holds it, and only the Mute Monkey can read it — but they can't speak a word of what's inside.
- Read the bomb. The Deaf Monkey can see every module, wire, and light on the bomb itself, but can't hear anything anyone says about it.
- Communicate. Between the manual and the bomb, your team has to build a channel out of gestures, pointing, and emotes — whatever gets specific information from one head to the other two.
- Act. The Blind Monkey is the only one who can physically touch the bomb, and does so blind, entirely on the team's word.
Get a module right and the timer eases up; get it wrong and you lose time — sometimes a lot of it. Every wrong guess costs you, so a slower, correct callout almost always beats a fast, sloppy one.
Walking through your first bomb
A typical first bomb starts with everyone just staring at their own piece of the puzzle for a few seconds — that's fine, take the moment. The Mute Monkey should flip to the first page of the manual and start pointing at whatever module type matches what the Deaf Monkey is describing with gestures (shape, color, layout). The Deaf Monkey's job in this phase is less "solve it" and more "translate the bomb into something point-at-able" — hold up fingers for a wire count, trace a shape in the air for a symbol, point at the physical spot on the module. The Blind Monkey, meanwhile, should stay still and quiet until they've actually got an instruction, then act on it exactly as described and wait for confirmation before moving to the next step. Resist the urge to touch anything speculatively — a guess that turns out wrong costs everyone time that a slower, confirmed answer wouldn't have.
Once the first module clears, the relief is real but short — there's almost always another one queued up immediately, and the timer doesn't pause to let you celebrate. Treat the first module as a dry run for your team's communication style, then carry whatever worked into the next one.
Common first-timer mistakes
- Everyone talking at once. Voice chat is one channel with two people trying to describe the bomb and manual simultaneously — it turns into noise fast. Establish who speaks when.
- The Deaf Monkey typing or speaking instead of gesturing. They can't hear replies either way, but leaning on voice out of habit wastes the visual channel that's actually theirs to use.
- The Blind Monkey acting before confirmation. A half-heard instruction acted on immediately is how correct modules turn into wrong guesses.
- Not agreeing on vocabulary first. "The red one" means nothing if there are three red things on the module — get specific before you start, not mid-panic.
Once the basic loop feels natural, the fastest way to level up is to agree on a shared vocabulary ahead of time — see our callout guide for a concrete script you can steal wholesale for your own group.