BOMBANANA! Wires Module: Which Cable to Cut

The wires module is the first module most BOMBANANA! teams ever face, and it stays one of the most common modules on every bomb. The manual's entire rule for it fits in one sentence: "Cut the correct cable based on the number of cables connected to the module and the color of the active light." Two visible inputs, one cut. The danger is entirely in the details.

How the Wires Module Works

The module presents three or four colored cables and an indicator light. The Deaf monkey calls out:

1. How many cables are connected to the module.
2. The color of the active light.
3. The color and position of each cable, counted strictly left to right.

The Mute monkey checks the manual's wires chapter for that cable count and light color, finds which cable color to cut, and the relay passes it to the Blind monkey — the only player who can physically cut anything.

Quick-Reference Tables

Community walkthroughs captured these mappings during launch week:

Three cables:

Four cables:

Variant warning, and it matters here more than anywhere: the same walkthrough that produced these tables explicitly says different pattern combinations occasionally appear, and that the manual is the final word in those rounds. Multiple tables from different play sessions would be the only way to spot a variant — so use these tables to learn the shape of the rule (count + light → color), and let the Mute's manual decide the actual cut. If the manual disagrees with a table you memorized, the manual wins, every time.

The Two Counting Traps

• Count cables, not slots. Modules can have empty connector slots, and counting them as cables changes the lookup row. The Deaf should say "three cables" based on actual cables.
• Count left to right, always from the Blind's perspective. "Third cable" means nothing unless everyone shares one perspective. The community rule is that left/right is always defined from the Blind monkey's point of view.

A Workflow That Doesn't Explode

The fastest reliable wires workflow observed in community play:

1. Deaf announces cable count and light color.
2. Deaf calls the cable colors one at a time, left to right — "first: blue. second: red. third: yellow."
3. The Mute nods or shakes their head per cable while scanning the manual row, so the team instantly knows which cable the manual wants — calling one color at a time and confirming against the target color is faster and more stable than reciting the whole sequence and picking afterward.
4. The Blind reads back: "Cut the second cable, the red one."
5. The Deaf confirms. The Blind cuts.

Step 3 deserves emphasis: relaying colors one at a time with a yes/no per color beats a memorized sequence, because it eliminates transcription errors at the point where they are most expensive.

One Cut, One Strike

There is no partial credit on wires. Cutting the correct cable solves the module; cutting any other cable burns one of the team's three strikes. Since wires modules are usually the fastest modules on the bomb, a wasted strike here is the most avoidable loss in the game — which is why even experienced teams keep the full readback ritual on wires modules while speeding through everything else.

If the Module Ignores You

If a cut produces no visible response, do not immediately cut again. Check in order:

1. Did the Bomb open the module's interaction view? (Right-click — a plain click is not enough.)
2. Was the cable count right — cables, not slots?
3. Does the manual's row for this round actually match the light color that was called?

Only after re-observing all three should a second cut happen — and it should be a freshly confirmed order, not a reflex.

For the other lookup modules, see the direction module guide and the math module guide. For every module at a glance, start with the modules overview. In a hurry? The solver gives the single answer for your exact two inputs.