Quick start
BOMBANANA is built around three players who cannot all read and manipulate the same information. Blind handles the bomb, Deaf reads and speaks what is visible, and Mute uses the manual and gestures to translate the rule. A clean run begins before anyone touches a panel: confirm the three roles, the time limit, the remaining mistakes, and the words you will use for positions and colours.
🎮 First-run cue: name the roles, call the shared timer, and repeat the first input before anyone presses.
Your first five minutes
1. Read the shared state
Call the timer, strikes, and total stages. If the team knows the remaining margin, it can decide whether to slow down for a second confirmation or keep moving.
2. Name the module
Deaf says the module name before describing details. Mute opens that section of the manual. Blind does not press anything until the target has been repeated once.
3. Use one instruction at a time
Short calls are safer than a paragraph: “Cable, top row, second from left, confirm.” After the input, Blind reports the result and the team advances.
4. Treat Chaos as a shared alarm
Pressure, Slider, and Alarm are managed while the bomb remains active. Pause a normal module when a Chaos state needs attention, then announce when it is stable again. The Alarm guide and Pressure guide give the exact response pattern.
First-session checklist
Before loading the first level, make sure the team has:
- one player assigned to the final physical input;
- one agreed name for each position, color, and stage;
- a shared wait / confirm / rebuild signal;
- a plan for who monitors a Chaos panel;
- a rule that no one presses while another player is still describing the clue.
If any item is missing, use Team Setup before starting. The goal of the first session is not to finish quickly; it is to make a failed callout understandable enough to repair.
Practice order
Start with the Level 1 entry in the Level Lookup tool. Learn Cable, Calculator, Direction, and Symbol before adding memory and audio pressure. Then practise Monkey-Says, Maze, and Morse one at a time. Do not add Endless or Custom difficulty until the team can recover from a wrong callout without arguing about roles.
Mistakes that cost runs
- Using external voice chat when the game’s role restrictions are the challenge.
- Saying “that one” instead of a stable position or colour.
- Giving the manual result before the visual description is complete.
- Forgetting that a stage is part of the whole bomb, not the end of the run.
Next steps
Read Roles and communication, then use the module index as a checklist. When you are comfortable, move to Campaign Progression and plan which late-game modules need a dedicated monitor.
When a module still feels unclear, open its individual guide rather than jumping directly to a full walkthrough. Focus on one field at a time—module name, position, state, rule, action, result—until the three-player relay is repeatable.