BOMBANANA Deaf Monkey Guide: Read Panels and Relay Actions

In the BOMBANANA Deaf Monkey role, you send the visible bomb state toward the manual and return its interpreted answer as a physical instruction. These are different messages. Begin by identifying the panel and its relevant fields. After Mute supplies the rule result through gestures, translate it into a location and action Blind can use.

Keep an observation separate from an instruction. Saying a color while you inspect the bomb should not sound like permission to cut a cable. Prefixing a message with the module name and indicating whether you are describing or directing can prevent an eager teammate from acting before the lookup is complete.

Use the field list for the active module. A row of colors may need its order preserved; a grid may need row and column; a display may need a value as well as its stage. If you cannot distinguish a symbol, describe its features consistently or agree on a name before it matters. Do not substitute the answer you expect for the observation you actually have.

Choose one reference frame for physical positions, ideally the operator facing the relevant panel. Make the frame explicit when moving to another module. Viewpoint disagreements can survive several accurate color descriptions, then appear only when Blind reaches for the wrong side. Solve the numbering problem before committing an input.

• Cable: count, light and ordered colors
• Symbol identification and manual lookup

A spoken readback from Blind is not audible to you. The team therefore needs a visible correction route through Mute and an outcome check on the panel. Agree on what Mute will signal if the returned instruction is wrong or not yet authorized. Do not assume that teammates understand an answer because nobody appears to object.

After Blind acts, inspect the visible result before directing the next step. Did a display advance, a control change, or the module reach a different state? Describe what is observable without inventing an explanation. If the expected response is missing, ask the group to stop and reconstruct the previous action rather than immediately repeat it.

A manual result can name a color, digit, direction or sequence. Blind still needs the physical control that corresponds to it. For a keypad, locate the requested digit on the current arrangement. For Cable, connect the selected answer to an ordinal position. For an ordered movement, keep the sequence index attached to the direction.

Consider an invented training exchange: the manual identifies a cable, and you describe “third from the agreed left side; this is the selected cable.” The useful part is the connection between the lookup and the physical target. The number three is only an example and must never be reused as a solution without checking the actual module.

• Calculator: value versus key location
• Blind operating guide

When the loadout includes Pressure or another Chaos duty, agree before the run how the group will interrupt an ordinary lookup. Name the hazard when calling for attention, identify the required physical control, and make clear that the previous task is paused. Watching a hazard does not change which role can operate the bomb.

On return, reread the active module’s current stage. A correct earlier action may have completed while you were redirecting attention. Calculator, Piano and other multi-step work can become confused if the group resumes from the last spoken phrase instead of the observed state. The guide does not establish one universal warning threshold or timing schedule for all hazards.

• Pressure module guide
• Level 9 Piano and Pressure coordination

Outside a live attempt, describe an imagined panel with repeated labels or a simple drawn grid. Have the others record what they understood, then compare their interpretation with the original. Look for lost ordering, unnamed reference frames and values mistaken for positions. These are rehearsal materials, not claims that the game includes a drawing or practice mode.

After a real failure, reconstruct the last observation, the manual answer, the physical instruction and the outcome as separate entries. A screenshot can help if it is available, but remove private player information before sending it to this site. Identify the first disagreement. Improving that transition is more actionable than blaming the entire relay for being slow.

• How to send a useful correction

Can I rely on Blind repeating my command? You cannot hear that readback. Arrange a visible correction signal through Mute and check the bomb’s resulting state. The communication plan must account for the information each player can receive.

Should I relay Mute’s answer immediately? First establish whether you understood its format. A count, position and sequence can be confused. If the signal is ambiguous, request clarification using the team’s agreed method before translating it into an action.

What should I report when a panel behaves unexpectedly? Describe the state you can see and the action just attempted. Keep your theory about the cause separate. That lets Mute check the relevant rule without accidentally treating a guess as another input.

In your next BOMBANANA Deaf Monkey session, focus on naming whether each message is an observation, an action, or a result. Keep the labels short and use them consistently. Once the other roles can tell those messages apart, you can shorten the exchange while preserving its meaning and the visible confirmation that closes it.