Fan-Made Community Wiki
BOMBANANA solver workflow
The solver loop
BOMBANANA is solved by routing information, not by one genius: the monkey facing the module describes, Mute looks the answer up in the manual, the relay speaks it back, and one monkey acts. Describe, look up, confirm, act — every module obeys the same loop.
- Mute reads the manual but cannot speak — answers travel through the relay.
- Blind and Deaf each hold one incomplete view of the module.
- No action before a confirmation read-back — the bomb punishes assumption.
The four-step loop every module obeys — describe, look up, confirm, act.
Why a workflow beats raw knowledge
Nobody memorizes every module: the in-game manual is long, and patches move details. What transfers between sessions is the routing system — who is allowed to speak, who reads, who acts. Squads that stall usually have an information bottleneck: everyone talking, nobody reading, or Mute's answers dying somewhere in the relay.
The four-step solver loop
1. DESCRIBE — the monkey facing the module calls out exactly what is visible: state names, positions, symbols. Raw observations only, no interpretation.
2. LOOK UP — Mute finds the matching manual section. If the description matches nothing, loop back to step 1 — a second description beats a wrong match every time.
3. CONFIRM — Mute's answer travels through the relay and comes back as a read-back: the acting monkey repeats the instruction out loud before performing it.
4. ACT — one monkey acts while everyone else goes quiet until the module's state visibly changes. Overlapping instructions are how two correct answers become one wrong cut.
Callout discipline that keeps the loop fast
Anchor every callout to a position or a printed label, never to 'the thing on the left' from two different viewpoints. Fix the relay owner and the action owner per module type in the lobby — switching owners mid-bomb is the most common source of double-inputs. When a module resists two full loops, park it: solve what is solvable, bank the clock, come back with fresh eyes.
Practice the loop, not the modules
Campaign's early levels are the cheapest place to drill the loop until the handshake is automatic; Endless is where sloppy vocabulary gets punished. Run your first sessions at conversation pace — speed comes from the loop staying clean under pressure, not from talking faster. The communication guide covers the gesture layer for the moments voice is not enough.
Keep reading
Facts checked against the Steam store page.