BOMBANANA Wires Guide: Read Colors and State

The short answer

BOMBANANA! wires are solved by preserving the full panel state until the manual reader chooses a target. Start with the number of wires, report their colors from left to right or another fixed order, include the indicator state, and wait for a confirmed physical position. The handler should cut only after the team repeats the position using the agreed perspective.

Wire modules are often the first place a team learns the full information relay. A color may be visible to one player, a count or physical position may be available through the bomb interaction, and the rule itself belongs to the manual reader. The final answer has to travel through those roles without losing the difference between a color and a position.

Build a complete wire report

Name the module first. Then give the wire count, list every color in a fixed order, and report the indicator or light state if the panel shows one. This ordering helps the manual reader select the correct rule branch before comparing the colors.

Never start with a single color when the count can change the rule. A red wire in a three-wire panel may belong to a different branch from a red wire in a four-wire panel. If the order is omitted, the manual reader may know the target color yet still be unable to tell the handler which physical wire to cut.

Repeat uncertain colors rather than guessing from a similar shade. The team can agree on a short vocabulary for colors before the first bomb, and the visual player can report them one at a time. A brief repeat costs less than an incorrect cut followed by a confused argument about what was seen.

Move from color to position

The manual may return a target color, a target condition, or another rule result. The bomb handler needs a position on the live panel. Translate the result into a stable physical instruction such as the first wire from the left or the third wire from the agreed top-to-bottom order.

The Deaf Monkey can see colors and indicator states and can speak the result to the group. The Mute Monkey reads the manual and converts the report into the selected target. The Blind Monkey is associated with touching and operating the bomb, so this player needs the final position rather than a visual label alone.

Use one confirmation cycle for one cut. The bridge repeats the target position, the manual reader confirms it, and the handler performs the action. If the panel changes after the cut, stop and report the remaining state again instead of carrying the old color list forward.

Keep the indicator in the packet

Wire rules can use both the wire arrangement and an indicator or LED state. The light can select a different branch even when the visible colors stay the same. It should therefore be reported as part of the initial state and repeated when it changes.

A useful callout has four pieces. Identify the wires, state the count, read the color order, and name the indicator state. The manual reader then returns one target, and the team turns that target into one position before the cut.

Do not let the handler act when only the target color has been announced. “Cut blue” is incomplete if several blue wires exist or if the handler uses a different left and right reference. The last sentence should contain a unique position and a confirmation signal.

Exact color rules are To be confirmed

Community quick references cover wire counts, light colors, and target positions. Broader module pages describe the callout fields without publishing a complete release-stable answer table. Those details are enough to define a safe reporting method, yet not enough to guarantee one exact mapping for every current bomb.

The permanent color-to-position rules are therefore To be confirmed unless the live in-game manual supports the row you are using. Do not copy a table from an old Demo clip into a full-release page as if it were universal. Record the current build and verify the rule again when a patch changes manual text or module behavior.

This distinction protects the player at the bomb. A careful uncertainty label tells the team to check the rule, while a guessed target color can turn directly into a failed input. The puzzle modules overview keeps the launch module count separate from detailed answers that still need stronger verification.

Handle a changed panel

Treat each cut as a new information state. The remaining wire count, order, indicator, and position can change the next decision, so the visual player should report the panel again instead of assuming the first description still applies. The manual reader should resolve the new packet only after the handler confirms the current layout.

A stop signal is useful when two players describe different colors or positions. Freeze the action, repeat the count, and read each wire in the agreed order from the beginning. This method keeps a disagreement visible and gives the team one clean state to match against the current manual.

The same habit helps when several modules appear on one bomb. Finish or pause one wire decision before sending a different module’s clue, and name the module at the start of every new report. Separate state packets reduce the chance that a target from the wires page is carried into a switch, direction, or math decision.

Practice wires before stacking modules

Campaign is a natural first training path because it gives the team a progression through bomb situations. Custom can later isolate module types, adjust the timer, or change how many mistakes are allowed. Use the game modes guide if the group is unsure which setting fits the practice goal.

Before a run, agree on the panel perspective and the words for repeat, stop, and confirmed. During the run, let one player own the color stream and one player own the final position. After a failed cut, ask whether the count, color, light, rule branch, or physical position was missing.

Read BOMBANANA! manual for the role handoff, BOMBANANA! roles for sensory limits, and communication for the team vocabulary. When another panel appears on the same bomb, use the switch module guide or the direction module guide and start a separate state packet.