How to Read the BOMBANANA! Defusal Manual

In BOMBANANA!, the defusal manual is the single source of truth for every module solution. Only one player — the Mute monkey — can read it. Teams that learn how the manual is organized defuse bombs several times faster than teams that treat it as a random stack of rules. This guide explains its structure and the mistakes that manual readers commonly make.

Who Holds the Manual

The manual belongs to the Mute monkey. The Mute cannot speak and cannot touch the bomb, but is the only player allowed to read the defusal manual — in-game it appears as a book that the Mute player opens and pages through. The manual has multiple pages, organized into chapters by module type.

This design is the heart of the game: the player who knows the rules cannot see the bomb, the player who sees the bomb cannot know the rules, and the third player has to carry messages between them.

How the Manual Is Organized

Three structural facts about the manual matter in every round:

1. Chapters are per module type. Wires, directions, math, piano, and every other module family has its own section. When the Deaf announces the module name, the Mute should already be turning to that chapter.
2. Rules are keyed to observable details. Each chapter maps things the Deaf can see — LED color, number of cables, braille number — to the action the Blind must perform. For example, the wires chapter is built entirely on the number of cables connected to the module plus the color of the active light.
3. The manual has multiple rounds/columns. Several chapters contain tables with a column per round. You must look up the answer in the column matching the current round number — reading the wrong column is one of the most common ways experienced teams still explode.

Example Rules, Straight From the Manual

These are examples of how the manual phrases its rules, as captured during play:

• Wires module: "Cut the correct cable based on the number of cables connected to the module and the color of the active light."
• Direction module: "Press the correct button direction based on the number written in Braille."
• Math module: the manual maps the arithmetic result's parity (odd or even) combined with the light color to a number key — for example, "if the number is even and the color is green, then what you're supposed to press is nine."
• Piano module: the manual maps the braille number (the row) combined with the light color to the key position that must be pressed, sometimes several keys in sequence.

Note the pattern: an observable input (count, color, braille) plus the round produces one unambiguous output. The manual never asks for opinions — it asks for exact details, which is why vague callouts kill teams.

The Two-Stage Pattern

Some modules — most famously the math module — require two inputs in a single sequence. The arithmetic answer is typed in first, then a light activates, and only then does the manual's lookup table give you the second number to enter. Skipping the first input makes the module completely unresponsive, even if the second number is correct.

The general lesson for the manual reader: always check whether the chapter requires a staged input before telling the team a single answer is enough.

Manual Variants and Why Cheat Sheets Fail

Community-captured solution tables circulate online, and they do work — for the bombs those players happened to see. But community observations have also documented that the same module can appear with different pattern combinations, so a table copied from one play session can be plain wrong for your bomb.

The defusal manual inside your game always matches your bomb. That is why every guide on this wiki repeats the same rule: the in-game manual is the single authority. Use community tables as a learning aid, never as a replacement for the Mute's lookup.

One more thing players noticed during the demo era: the manual content repeated every round, so the Mute could eventually memorize it. Whether that stays true across all launch-version content is not guaranteed — and it is another reason not to rely on memory over the book.

Reading the Manual Fast Under Pressure

• While the Deaf is still describing the module, the Mute should already be on the right chapter — module names are announced first for exactly this reason.
• Confirm the round number before reading any table.
• Listen for the details the chapter actually needs, and ask (via gesture) for a re-read if a callout was ambiguous. One extra re-read beats one wrong cut.
• When the answer is found, gesture it clearly and let the Deaf relay it — do not rush the relay because the timer is low. A wrong answer under pressure wastes a strike you cannot spare.

For the full module-by-module breakdown — including every module family and the community-verified lookup tables with their variant warnings — continue to the BOMBANANA! modules guide.