BOMBANANA Symbol module guide

The BOMBANANA Symbol module is a defusal panel classified as medium. Rotate the selector to find the symbol that makes a sound, then use the current stage to identify the button. The selector is scanned until one symbol produces sound. That symbol, the current stage, and the available button colors form the useful packet. 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.

Symbol has fixed Campaign appearances in Level 8, Level 10, and Level 11, beginning at Level 8. A fixed appearance names the family, never its live answer. Choose the first target only after the scan. A simple known module is a good opener unless another panel is already heating, moving, or storing sequence state. Review the BOMBANANA procedure pre-play and recollect values after loading.

Open with “Symbol” so Mute reaches the correct BOMBANANA manual section. Its required packet is Current stage, Sound-producing symbol, Available colored buttons. 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. 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. 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. 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.

The compact procedure is: Describe only the currently selected symbol. Stop scanning when the sound-producing symbol is found. Use a consistent team nickname to check the manual. Repeat the stage and color before pressing. 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 “Symbol.” Keep acknowledgements short and distinctive. Casual agreement can be mistaken for permission, while a fixed confirmation word tells Blind exactly when action is safe. This predictable BOMBANANA loop exposes skipped steps.

Creative symbol names change between players and stages, making a correct shape hard to match in the manual. Continuing to scan after the sound also adds noise. Prevent it by attaching every answer to the Symbol module, current stage, and physical position. A color without a control, a direction without a stage, or a sequence without numbered places is incomplete. The relay should sound like a transaction: one labeled observation, one lookup result, one physical translation, one repeat, and one explicit confirmation. 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. 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. 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 Symbol, 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. Replay the longest exchange once without a timer and once under pressure. Compare where vocabulary changes, because that is usually where reliability disappears.

Create a shared list of short symbol nicknames from screenshots or the live manual. One player describes, another points, and the group keeps one permanent name. 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 “Symbol,” and collect current fields. Repeat only the current packet after recovery. Recounting the entire run wastes attention and can pull expired values back into working memory.

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. End practice with one deliberate failure and recovery. A group that only rehearses perfect packets has no shared language for the first real disruption. Shared understanding is more useful than one player memorizing a table.

Before touching the BOMBANANA Symbol panel, name the module, identify the stage, collect Current stage, Sound-producing symbol, Available colored buttons, 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. Keep acknowledgements short and distinctive. Casual agreement can be mistaken for permission, while a fixed confirmation word tells Blind exactly when action is safe.

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

• Say “Symbol” before reporting any values.
• Collect Current stage, Sound-producing symbol, Available colored buttons 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.