BOMBANANA Monkey-Says module guide

The BOMBANANA Monkey-Says module is a defusal panel classified as hard. Map the current color, append the new button to the stored sequence, and replay the complete history. Each stage maps a current heated color to a new button, then appends that button to a cumulative sequence that must be replayed from the beginning. 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.

Monkey-Says has fixed Campaign appearances in Level 23, and Level 24, beginning at Level 23. 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 “Monkey-Says” so Mute reaches the correct BOMBANANA manual section. Its required packet is Current heated color, Confirmed sequence history, Stage. 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. When two voices overlap, discard the last instruction and repeat it from the module name. The extra seconds buy one shared version of the current state. 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. When two voices overlap, discard the last instruction and repeat it from the module name. The extra seconds buy one shared version of the current state.

The compact procedure is: Assign one player to maintain the cumulative sequence. Read the current heated color and check its mapping. Append the new button to the end of the sequence. Replay from item 1; never press only the newest item. 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 “Monkey-Says.” The relay should sound like a transaction: one labeled observation, one lookup result, one physical translation, one repeat, and one explicit confirmation. This predictable BOMBANANA loop exposes skipped steps.

Teams often press only the newest answer or let two players maintain different histories. One disagreement late in the sequence invalidates every following input. Prevent it by attaching every answer to the Monkey-Says module, current stage, and physical position. A color without a control, a direction without a stage, or a sequence without numbered places is incomplete. 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. 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. 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 Monkey-Says, 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. Score the rehearsal by missing fields, ambiguous positions, early movements, and failed confirmations. Those counts identify a fix more clearly than completion time alone.

Assign one history keeper and use numbered sequence readbacks. Add one item per round, then replay from item one before extending the list again. 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 “Monkey-Says,” 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. 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. Shared understanding is more useful than one player memorizing a table.

Before touching the BOMBANANA Monkey-Says panel, name the module, identify the stage, collect Current heated color, Confirmed sequence history, Stage, 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. The relay should sound like a transaction: one labeled observation, one lookup result, one physical translation, one repeat, and one explicit confirmation.

If Chaos interrupts Monkey-Says, 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 “Monkey-Says” before reporting any values.
• Collect Current heated color, Confirmed sequence history, Stage 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.