BOMBANANA Cable module guide

The BOMBANANA Cable module is a defusal panel classified as easy. Use the cable count and LED to find a target color, then translate that color into a physical position Blind can use. The lookup produces a target color, while Blind needs a numbered cable position. Deaf must perform that final translation after comparing the target with the live left-to-right cable sequence. Observation, lookup, relay, and action give each monkey a checkable stage. Read stable values first and changing values last. The order reduces the chance that a live state expires while Mute is still searching a rule branch.

Cable has fixed Campaign appearances in Level 1, Level 3, and Level 6, beginning at Level 1. A fixed appearance names the family, never its live answer. Start with the clearest shared state, then move toward the most demanding procedure. Early confirmation establishes rhythm without sacrificing a volatile panel. Review the BOMBANANA procedure pre-play and recollect values after loading.

Open with “Cable” so Mute reaches the correct BOMBANANA manual section. Its required packet is Cable count, LED color, Cable colors, left to right. Read those fields in their displayed order and attach numbers or coordinates wherever position matters. If a value is uncertain, name the missing field instead of supplying alternatives. Use numbered positions during the first scan, because a later color, symbol, or direction is only useful when the team can attach it to one control.

Keep observation separate from interpretation: Deaf describes visible state, Blind contributes tactile or Braille state, and Mute performs the rule lookup. An observer who suggests an answer too early can anchor the group to a previous run. The relay should sound like a transaction: one labeled observation, one lookup result, one physical translation, one repeat, and one explicit confirmation. For this BOMBANANA panel, familiarity never replaces a complete current packet.

For this BOMBANANA module, Deaf begins with its name and visible values in stable order. Blind adds tactile information while keeping clear of actionable controls. Mute checks the matching branch and returns only the requested result; Deaf translates that result into Blind’s viewpoint; Blind repeats, waits for confirmation, acts once, and reports the outcome. Keep acknowledgements short and distinctive. Casual agreement can be mistaken for permission, while a fixed confirmation word tells Blind exactly when action is safe.

The compact procedure is: Deaf reports the cable count, LED, and color sequence from left to right. Mute checks the manual and returns the target color. Deaf converts that color into “cable N from the left.” Blind repeats the position and cuts only after confirmation. The pace may slow, but the fields should retain their order. If Mute signals missing data, return only that field unless a full reset is requested. A changed stage expires the old packet and restarts at “Cable.” Mute should return the answer in the same field order used by the procedure. Stable ordering lets Deaf notice a skipped value without understanding the full table. This predictable BOMBANANA loop exposes skipped steps.

Teams often say only a color or silently change their counting direction. Both errors can preserve a correct manual lookup while producing the wrong physical cut. Prevent it by attaching every answer to the Cable module, current stage, and physical position. A color without a control, a direction without a stage, or a sequence without numbered places is incomplete. A role that notices missing context should stop the chain immediately. Repairing one field preserves the packet; guessing forces the team to rebuild after a strike. Blind should be able to repeat the final action without needing the manual logic.

A second BOMBANANA failure is continuing through uncertainty because the timer is audible. “Hands off” is a neutral correction: recheck one missing field, or request a full reread after a state change. A clean restart has three markers: interruption resolved, original module named, and fresh input acknowledged. Missing any marker leaves roles at different points. Classify the issue afterward as observation, lookup, relay, positioning, execution, or interruption recovery.

A public community table is included, but it remains community evidence and must be paired with the current live inputs. The cited structured and community sources supporting the callout order were checked September 3, 2026. A BOMBANANA table is a lookup aid, not a replacement for reading the panel. Read stable values first and changing values last. The order reduces the chance that a live state expires while Mute is still searching a rule branch. Select a row only after every input is attached to the current stage.

If BOMBANANA changes Cable, compare live behavior with the source date before blaming the player. Record the exact inputs, result, and stage, then seek an official announcement or reproducible community correction. One failed attempt is not enough to patch a table because execution errors and expired state can imitate a rule change. Change one variable between drills—role assignment, panel position, or interruption timing—so the team learns the protocol instead of memorizing one performance.

Lay out four colored objects, call the LED and sequence, then answer with both target color and ordinal position. Change the order after every repetition. Keep the exercise outside a serious Campaign attempt until every role can finish without inventing vocabulary. Then add a timer and one deliberate interruption. Rehearse the full BOMBANANA recovery: hands off, identify the break, declare stability, restart at “Cable,” and collect current fields. Use “hands off” as a state-control command, not criticism. Neutral language makes it easier to stop a nearly completed action when the evidence changes.

Measure packet accuracy before raw speed. Count missing fields, ambiguous positions, premature actions, and failed confirmations; only shorten pauses after the packet is reliable. Rotate BOMBANANA roles so everyone experiences observation, manual search, relay translation, and physical execution. Change one variable between drills—role assignment, panel position, or interruption timing—so the team learns the protocol instead of memorizing one performance. Shared understanding is more useful than one player memorizing a table.

Before touching the BOMBANANA Cable panel, name the module, identify the stage, collect Cable count, LED color, Cable colors, left to right, and convert the manual result into a physical instruction. Repeat the whole action and wait for confirmation; after one input, report whether the panel cleared, changed, or expects another stage. Mute should return the answer in the same field order used by the procedure. Stable ordering lets Deaf notice a skipped value without understanding the full table.

If Chaos interrupts Cable, stop its callout and clear the emergency first. Treat the packet as expired until every role confirms otherwise; reread the panel, reopen the correct branch, and send a fresh physical instruction. A clean restart has three markers: interruption resolved, original module named, and fresh input acknowledged. Missing any marker leaves roles at different points. Labeled repetition is safer than combining correct fragments from different BOMBANANA moments.

• Say “Cable” before reporting any values.
• Collect Cable count, LED color, Cable colors, left to right in a fixed order.
• Keep the live observation separate from the manual interpretation.
• Translate the answer into Blind’s physical viewpoint and confirm once.
• After a state change or Chaos event, discard the old packet and reread.