BOMBANANA Direction module guide

The BOMBANANA Direction module is a defusal panel classified as easy. The LED and Braille number determine one directional input. Read the state again after the panel advances. The current LED color and a Braille number select one direction for one stage. After the press, the next visible state must be treated as a new lookup. 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.

Direction has fixed Campaign appearances in Level 4, beginning at Level 4. A fixed appearance names the family, never its live answer. Prefer the packet the team can complete cleanly, but never ignore a live interruption to chase an easy clear. Stability comes before cosmetic progress. Review the BOMBANANA procedure pre-play and recollect values after loading.

Open with “Direction” so Mute reaches the correct BOMBANANA manual section. Its required packet is LED color, Braille number from 1 to 9. 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. 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: Read the current LED color. Blind reports the Braille number. Mute checks the table and returns one direction. Press once, then check whether the panel advanced. 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 “Direction.” 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.

The most common failure is carrying a previous LED or Braille value into the next stage because the first answer was still being discussed. Prevent it by attaching every answer to the Direction 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. After any break, ask whether the panel is unchanged, advanced, or reset. That classification determines whether the old lookup is valid or must be discarded. 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. 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 Direction, 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.

Run rapid one-action rounds. After every simulated press, everyone says “new stage,” clears the old values, and waits for a fresh LED and 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 “Direction,” and collect current fields. Restart from the module name after an interruption, then re-establish stage and current inputs. Resuming from a remembered answer joins two different moments of bomb state.

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 Direction panel, name the module, identify the stage, collect LED color, Braille number from 1 to 9, 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 Direction, 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. After any break, ask whether the panel is unchanged, advanced, or reset. That classification determines whether the old lookup is valid or must be discarded. Labeled repetition is safer than combining correct fragments from different BOMBANANA moments.

• Say “Direction” before reporting any values.
• Collect LED color, Braille number from 1 to 9 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.