BOMBANANA Morse module guide

The BOMBANANA Morse module is a defusal panel classified as hard. Record each display’s dot-dash rhythm, decode it to a digit, then enter the digits in their original order. Each display loops a dot-dash rhythm that decodes to a digit. Digits must remain attached to their original display positions until final entry. Observation, lookup, relay, and action give each monkey a checkable stage. 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.

Morse has fixed Campaign appearances in Level 21, and Level 22, beginning at Level 21. A fixed appearance names the family, never its live answer. Announce a two-item queue and revise it aloud when conditions change. Silent reprioritization leaves Mute researching one panel while Blind prepares another. Review the BOMBANANA procedure pre-play and recollect values after loading.

Open with “Morse” so Mute reaches the correct BOMBANANA manual section. Its required packet is Dot-dash pattern for each display, Decoded digit, Display order. 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. Finish the scan with a missing-field check. A short pause here is cheaper than a confident answer built from an incomplete observation packet.

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. Keep acknowledgements short and distinctive. Casual agreement can be mistaken for permission, while a fixed confirmation word tells Blind exactly when action is safe. 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. Close every action with the observed result—cleared, unchanged, or new stage—so nobody silently carries an old answer into the next exchange.

The compact procedure is: Watch only one display at a time. Let the pattern loop twice before confirming it. Mute decodes it and returns the digit with its display number. Repeat every display in order before pressing 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 “Morse.” Close every action with the observed result—cleared, unchanged, or new stage—so nobody silently carries an old answer into the next exchange. This predictable BOMBANANA loop exposes skipped steps.

One partial cycle can invert a pattern, and a correct digit can still be entered in the wrong slot when position labels are omitted. Prevent it by attaching every answer to the Morse module, current stage, and physical position. A color without a control, a direction without a stage, or a sequence without numbered places is incomplete. Keep acknowledgements short and distinctive. Casual agreement can be mistaken for permission, while a fixed confirmation word tells Blind exactly when action is safe. 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. 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. 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. Finish the scan with a missing-field check. A short pause here is cheaper than a confident answer built from an incomplete observation packet. Select a row only after every input is attached to the current stage.

If BOMBANANA changes Morse, 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. Write down the first repair for the next run, not a list of every annoyance. One measurable protocol change is easier to test than a general promise to communicate.

Tap short looping patterns twice, have one player transcribe dots and dashes, then return each decoded digit with an explicit display number. 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 “Morse,” and collect current fields. A clean restart has three markers: interruption resolved, original module named, and fresh input acknowledged. Missing any marker leaves roles at different points.

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. Use physical props or drawn panels to verify viewpoint language. If a teammate points to the wrong location, revise the phrase before returning to Campaign. Shared understanding is more useful than one player memorizing a table.

Before touching the BOMBANANA Morse panel, name the module, identify the stage, collect Dot-dash pattern for each display, Decoded digit, Display order, 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. Close every action with the observed result—cleared, unchanged, or new stage—so nobody silently carries an old answer into the next exchange.

If Chaos interrupts Morse, 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. 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. Labeled repetition is safer than combining correct fragments from different BOMBANANA moments.

• Say “Morse” before reporting any values.
• Collect Dot-dash pattern for each display, Decoded digit, Display order 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.