BOMBANANA levels: all 30 Campaign missions

Each row in the BOMBANANA levels table combines four pieces of planning information: the countdown, allowed mistakes, defusal slots, and ongoing Chaos duties. A named module is a fixed slot and can be reviewed before the run. A Random Easy, Medium, or Hard label identifies a difficulty pool. The table never turns that pool into a promised module because the live selection can change between attempts. Use the range tabs to isolate the part of Campaign your team is currently training.

The training-focus column groups BOMBANANA levels by the communication skill they emphasize. Levels 1–7 establish common language. Levels 8–15 lengthen the information packet. Levels 16–20 demand complete state before action. Levels 21–24 add sequence memory, while Levels 25–30 test procedure under stacked Random Hard slots and Chaos. These labels are coaching summaries, not extra in-game rules, and they help a group choose what to rehearse after a failure.

A fixed BOMBANANA slot names the module that occupies that position in the level data. Fixed appearances are useful landmarks: Cable anchors Level 1, Color Slider anchors Level 2, and later missions introduce harder families such as Switch, Maze, Morse, and Monkey-Says. Study the linked module procedure, but do not memorize a color or position from an old attempt. The module family can be fixed while its live state and correct input still vary.

Random slots test breadth. When a BOMBANANA level lists two Random Medium modules, the useful preparation is to make every medium procedure equally callable, not to hope for the same pair you saw last time. Assign stable names to symbols, musical notes, coordinates, and state transitions. If the table lists several Random Hard slots, keep a paper or shared mental ledger for sequences. Randomness changes the loadout, but a disciplined information packet remains reusable.

Early BOMBANANA missions can allow only one mistake, even though the timer feels generous. That combination rewards a slow first read and an explicit repeat. Later levels usually allow three mistakes, but the extra margin should not become permission to guess. Treat mistakes as protection against execution slips, not as a strategy. Before touching a control, Blind should repeat both the item and its physical position in the same vocabulary Deaf used.

Split each BOMBANANA countdown into an opening scan, a main defusal window, and a reserve. During the scan, identify fixed panels, count Random slots, and assign Chaos ownership. During the main window, finish the shortest reliable modules first unless a persistent state makes another order safer. Preserve the final reserve for a full reread, not frantic overlapping speech. The exact split changes with the loadout, but every team benefits from naming the transition into reserve time.

Pressure, Slider, and Alarm compete with the normal BOMBANANA information chain. Pressure and Slider rise over time, so a designated watcher should monitor them without narrating every small movement. Agree on one threshold that justifies interrupting the main module. Alarm is different: its ten-second heated-button window demands an immediate hands-off call. If two copies appear, as they do in the final Campaign data, the team must be ready for repeated emergency cycles.

After any Chaos event, never continue from a half-remembered instruction. The active BOMBANANA panel may have advanced, the selector may have moved, or a player may have forgotten which field was confirmed. Deaf restates the module and current stage; Blind rereads tactile or Braille information if needed; Mute returns a fresh answer. This reset costs a few seconds and protects far more time than rebuilding an unclear conversation after an accidental input.

Choose one BOMBANANA level range and replay it until your wording stays identical across attempts. Rotate roles only between runs, not in the middle of a bomb. After a failure, classify it as observation, lookup, relay, positioning, execution, or interruption recovery. That small vocabulary makes review objective. Instead of saying the team was slow, you can say that the Switch color packet was incomplete or the Alarm restart phrase did not return everyone to the same stage.

Use the individual BOMBANANA level pages as briefing sheets. Each page expands the row into a suggested opening scan, role assignment, module order, Chaos recovery plan, and targeted drill. The next and previous links make sequential study easy, while fixed-module links connect the mission to the exact procedure. When the data says Random, the detailed page stays procedural instead of fabricating an answer that cannot be known before the run.

• Brief the timer, mistake limit, fixed slots, Random pools, and Chaos before starting.
• Give persistent Chaos to one watcher and name a backup.
• Complete one confirmed action before opening a second callout.
• Record the category of each failure and drill that category once.
• Move to the next range only when all three roles can restart cleanly after interruption.