BOMBANANA Maze module guide

The BOMBANANA Maze module is a defusal panel classified as hard. Identify the maze, start, and destination before sending one complete route with step counts. The Braille identifier selects a maze, while a red start and green destination define the route. Directions become usable only inside one agreed coordinate system. Observation, lookup, relay, and action give each monkey a checkable stage. Separate what the bomb shows from what the manual concludes. That boundary makes a bad observation easier to locate without reopening every earlier decision.

Maze has fixed Campaign appearances in Level 18, Level 19, Level 20, and Level 24, beginning at Level 18. 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 “Maze” so Mute reaches the correct BOMBANANA manual section. Its required packet is Braille maze number, Red-dot start, Green-light destination. 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. Separate what the bomb shows from what the manual concludes. That boundary makes a bad observation easier to locate without reopening every earlier decision.

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. 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. 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. The relay should sound like a transaction: one labeled observation, one lookup result, one physical translation, one repeat, and one explicit confirmation.

The compact procedure is: Confirm the Braille maze number. Use the agreed coordinate system to locate the red start. Confirm the green-light destination. Bundle the route as direction plus step count; after an interruption, resume from the current cell. 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 “Maze.” 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. This predictable BOMBANANA loop exposes skipped steps.

A route can be logically correct but physically reversed when players use different viewpoints, or lose its place after Chaos interrupts a long sequence. Prevent it by attaching every answer to the Maze module, current stage, and physical position. A color without a control, a direction without a stage, or a sequence without numbered places is incomplete. 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. 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.

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. 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. Select a row only after every input is attached to the current stage.

If BOMBANANA changes Maze, 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. Rotate roles after a clean attempt. Experiencing each information limit helps players request only what the next person can actually observe or communicate.

Draw small grids with a fixed top-left origin. Call routes as direction plus count, stop at checkpoints, and practice resuming from the current cell. 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 “Maze,” 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. Score the rehearsal by missing fields, ambiguous positions, early movements, and failed confirmations. Those counts identify a fix more clearly than completion time alone. Shared understanding is more useful than one player memorizing a table.

Before touching the BOMBANANA Maze panel, name the module, identify the stage, collect Braille maze number, Red-dot start, Green-light destination, 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. 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.

If Chaos interrupts Maze, 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 “Maze” before reporting any values.
• Collect Braille maze number, Red-dot start, Green-light destination 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.