Bombanana Manual

Every module is solved by the same relay, because each player is missing one sense:

Role	Can	Cannot	Job
Blind Monkey	Touch the bomb, feel braille, speak	See colors or screens	The only hands. Reports touch, executes confirmed actions.
Deaf Monkey	See the bomb, speak	Hear anyone	The voice. Reads the Mute's gestures, speaks instructions to the Blind.
Mute Monkey	See, hear, hold the manual	Speak	The rulebook. Looks up answers, gestures them out.

The loop runs one way: Blind reports what they feel, Mute matches it against the manual and what the sighted players see, Mute gestures, Deaf speaks, Blind acts once and reports.

The callout shape that never changes

Module name. Position. The details that module needs. Wait. Repeat. Confirm. Act once. Report.

Open the live wires solver

What you see

A row of 2 to 6 colored wires and an indicator light. One wire is the correct cut.

The rule

The correct wire is chosen by the number of wires crossed with the light color; that intersection lives in the in-game cable table. Three-wire and four-wire panels can use different rows, so the count comes first, always.

Callout script

Wires, top right. Four wires. Left to right: green, blue, red, yellow. Red LED. Waiting for the cut instruction.

Step by step

1. Count the wires out loud before naming any color.
2. Read the colors from the HANDLER'S left to right. Agree on that perspective before the round.
3. Call the light color and position.
4. Manual holder finds the row for that count and the column for that light, then signals the cut.
5. Caller repeats the target as color AND position. Handler repeats it back, gets a yes, cuts once.

Why teams fail it

Skipping the wire count (wrong table row), reading colors from the wrong side, and cutting while the manual holder is still checking. Cutting is irreversible.

Open the live direction pad solver

What you see

Four arrows around a center value. The center value is embossed braille (the Blind Monkey's job); an indicator light shines red, yellow, green, or blue (the sighted players' job).

The rule

Press one arrow, chosen by the braille number crossed with the light color. The in-game manual holds a grid: each number row meets each color column at exactly one arrow. No single player has enough information.

Callout script

Direction pad, bottom left. Center value is three. Blue LED. Using handler left and right. Waiting for the direction.

Step by step

1. Blind Monkey feels the center value and says it. Nobody guesses dots for them, ever.
2. A sighted player calls the light color.
3. Manual holder finds row (number) times column (color), gestures the arrow.
4. Deaf Monkey confirms it is still a direction module and says it as one word: press left.
5. Left and right mean the HANDLER'S left and right. If that was never agreed, stop and agree.

Why teams fail it

Perspective: two players meant different lefts. Second killer: reusing the old value after a wrong press; the module state can change, so re-read both inputs.

Open the live numpad calculator

What you see

A display with an arithmetic expression (for example 51-17) and a keypad whose keys are NOT in normal order. Sources differ on whether the keys are jumbled printed digits or braille-labeled in random order; both agree on the fix: press the number, never the position.

The rule

The math is step one, not the answer. Solve the expression, then classify the result: odd or even, and greater or less than a threshold (5 in every published example). An LED color selects the manual branch. The manual then names ONE final digit; the handler finds that digit wherever it sits on the jumbled pad.

The priority trap

A result like 27 is odd AND greater than 5 at once, so two branches look valid. The documented rule from every source: the manual holder resolves the branch using the LED color and the manual's own order. The handler reports the full state and waits.

Callout script

Numpad, upper left. Expression is 52 minus 25. Result is 27, odd, greater than 5. Green LED. Waiting for the final number.

Step by step

1. Read the full expression out loud, operator included. A minus misread as plus is the classic fail.
2. Solve it (the calculator does the math and the classification).
3. Report result, odd/even, greater/less, and the LED, in that order, every time.
4. Some numpads take the raw answer typed first and only then show the light that matters. Treat that as step two of the same module.
5. Press the final digit wherever it appears. Position lies; the printed number is the truth.

Open the live switch panel solver

What you see

A row of switches, a strip of colored lights above them, and a number input: a digit string on the panel, a braille value, or both. A final ENTER button commits the whole panel at once.

The rule

Each switch must reach the correct up or down state, driven by the light color order plus the number input; then enter commits everything. The failure is deferred: you can set three switches right, rush the fourth, and lose the panel at the enter press.

Callout script

Switches, top row. Four switches. Light order: red, green, blue, yellow. Digit string: 8972. Waiting for switch states before enter.

Step by step

1. Read the FULL light order and the full digit string first. Context-free single numbers strand the manual holder.
2. Solve one switch per confirmed cycle: name the switch by position, get up or down, flip once, say flipped.
3. Keep a running count out loud. Nobody touches a confirmed switch.
4. Uncertain about one? Use the agreed go-back signal and revisit that exact switch before enter.
5. Press enter only when every state is confirmed. Enter is the trap.

Source conflict, logged honestly

Published guides disagree on what drives the table: one credible source says the digit string, another says braille values paired with the lights. Both may exist on different panels. Give the manual holder both inputs and let the in-game manual decide; the solver collects both.

Open the live braille decoder

What you see

Nothing, unless you are the Blind Monkey. Embossed dot cells only they can feel. Everyone else sees a panel and a light.

The rule

The Blind Monkey is the single source of truth for dots. They read one cell at a time and report it, the caller repeats the number back, and the manual holder matches it to the manual row for the CURRENT light color. If the light shifts mid-module, full stop and re-read.

Decoding dots

A braille cell is two columns of three dots: left column 1, 2, 3 top to bottom; right column 4, 5, 6. Standard braille numerals reuse the letter patterns a through j:

Digit	Dots	Digit	Dots
1	1	6	1, 2, 4
2	1, 2	7	1, 2, 4, 5
3	1, 4	8	1, 2, 5
4	1, 4, 5	9	2, 4
5	1, 5	0	2, 4, 5

Labeled assumption: player reports are consistent with standard braille numerals, but the game does not officially confirm the mapping. If the in-game manual disagrees, the in-game manual wins, and the mismatch goes on the changelog.

Callout script

Braille panel. Dots read as five. Confirm before any input.

Tier	New pressure
1	Single wires module. Learn the relay and the final-confirm habit.
2	Two-module bombs, typically wires plus a direction pad.
3	Numpad math appears. Separate the raw result from the final key.
4	Odd/even and greater/less branching starts deciding numpads.
5	Switch panels join the rotation. Multiple states before one enter.
6	Everything stacks with less recovery time. Fix a module order and stick to it.
7	Full stress test. Same rules, heavier pressure, no new tutorials.

The full game is expected to add modules beyond the demo set. Three candidates are reported by exactly one source each, below this site's two-source bar, so they are watchlist entries, not rules:

Reported module	Single-source description	Status
Password Cipher	Crack a password from cipher clues spread across the bomb.	Unverified
Sequential Activation	Press buttons in a manual-defined order; labels split across roles.	Unverified
Timer Sync	Act exactly when the bomb timer shows a specific value; only the Deaf Monkey sees the timer.	Unverified

The module registry is a data file, so verified full-release modules ship as data drops within 48 hours of launch. The changelog tracks every drop.