BOMBANANA Switch module guide

The BOMBANANA Switch module is a defusal panel classified as hard. This is a full-state module. Read and repeat all eight values before toggling anything or pressing Enter. Switch uses the complete ordered state of four lights and four Braille numbers. The four resulting switch positions must be repeated before Enter. Observation, lookup, relay, and action give each monkey a checkable stage. Finish the scan with a missing-field check. A short pause here is cheaper than a confident answer built from an incomplete observation packet.

Switch has fixed Campaign appearances in Level 16, Level 17, and Level 20, beginning at Level 16. A fixed appearance names the family, never its live answer. Give each queued panel a position and owner. That small inventory stops observations from neighboring modules being combined when the timer increases pressure. Review the BOMBANANA procedure pre-play and recollect values after loading.

Open with “Switch” so Mute reaches the correct BOMBANANA manual section. Its required packet is Four light colors, left to right, Four Braille numbers, 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. Treat the opening description as a checksum: another player should be able to repeat the panel identity and every required field before the lookup starts.

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: Report colors 1 through 4 as one sequence. Report Braille numbers 1 through 4 as one sequence. Mute returns four numbered switch states. Repeat the full answer, operate, and confirm again before Enter. 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 “Switch.” 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.

Partial lookup is dangerous: one missing color or number shifts the relationship across the whole row, and early toggles make the original state harder to reconstruct. Prevent it by attaching every answer to the Switch 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. Repeat only the current packet after recovery. Recounting the entire run wastes attention and can pull expired values back into working memory. Classify the issue afterward as observation, lookup, relay, positioning, execution, or interruption recovery.

No trustworthy complete public mapping was found, so the in-game manual remains the authority for the final answer. 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. 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. Select a row only after every input is attached to the current stage.

If BOMBANANA changes Switch, 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.

Read eight values as two numbered blocks, pause, return four numbered positions, and require a complete repeat before touching simulated switches or Enter. 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 “Switch,” and collect current fields. The watcher should declare both the warning and the return to stable conditions. Without the second signal, the main caller cannot know when normal traffic may resume.

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 Switch panel, name the module, identify the stage, collect Four light colors, left to right, Four Braille numbers, 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 Switch, 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. Repeat only the current packet after recovery. Recounting the entire run wastes attention and can pull expired values back into working memory. Labeled repetition is safer than combining correct fragments from different BOMBANANA moments.

• Say “Switch” before reporting any values.
• Collect Four light colors, left to right, Four Braille numbers, 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.