BOMBANANA Blind Monkey Guide: Positions, Inputs and Recovery

The BOMBANANA Blind Monkey role is easiest to manage when every instruction names a module, a control and an action. “Blue” might be an observed cable color, a light used in a lookup, or part of a different panel. None of those meanings alone tells your hands what to do. Ask for the physical position attached to the answer before committing an input.

You can repeat a spoken instruction, but Deaf cannot hear that readback. Mute needs to catch a mismatch and signal it visibly to Deaf, who can relay a correction. A readback only helps when the group knows who can receive it. Do not interpret the absence of a spoken objection as permission to continue.

Choose a single reference frame with your teammates before a run. The guide recommends left and right from the operator’s position facing the relevant panel, and row before column for grids. These are team conventions, not extra game mechanics. If someone describes the panel from a different viewpoint, resolve that difference before acting.

For a row of cables, ask for an ordinal position rather than relying only on color. For a keypad, distinguish the digit to enter from the place where that digit appears. “Enter five” and “press the fifth key” are different instructions. If the relay mixes them, state the ambiguity instead of choosing the interpretation that feels familiar.

• Cable inputs and positional lookup
• Calculator: results, LEDs and final keys

Let the relay finish identifying the target before you move from another module. Repeat the intended physical action when that helps Mute verify the message, then execute only that action. Deaf should inspect the panel afterward and describe whether the state changed. Waiting for that observation prevents an uncertain input from becoming the starting point of a longer guessed sequence.

A useful rehearsal instruction might be “Cable, second position from the agreed left side, cut once.” This is an invented communication example, not a solution for your bomb. The real choice must come from the current visible inputs and manual. If the result contradicts the instruction, stop and reconstruct the action rather than testing neighboring controls.

Piano, directional inputs and other ordered tasks add a memory problem to the positioning problem. Ask the team to number a sequence using the format agreed before the attempt. Keep the current action distinct from a list of future actions. If you lose your place, request the current index and the last visibly accepted step instead of starting again from memory.

The guide’s module pages identify which information the team needs, but they do not establish one universal pace or safe interval between inputs. Follow the live module’s requirements. A teammate reading ahead must make clear when they are describing the plan and when they are issuing the next command.

• Piano state and manual inputs
• Direction module preparation

When the team redirects you to Pressure or another Chaos duty, establish which control now has priority. An instruction for the interrupted module must not remain active while your hands move elsewhere. Have the relay name the new target, explain the physical action, and confirm when it is time to return.

On returning, ask for the original module and its current stage. The last thing you remember saying may already have been entered successfully. Calculator makes this distinction especially important: an accepted arithmetic result and a later final-digit choice are separate actions. Repeating the earlier entry without checking the stage can turn an otherwise correct recovery into a new error.

• Level 6: recovering after Pressure
• Pressure module responsibilities

Before a new attempt, rehearse a few descriptions away from the live countdown. One teammate draws a simple row or grid on paper and calls a position; another checks whether everyone means the same place. Use deliberately repeated colors or labels so the group learns when a name alone is insufficient. This is a communication exercise, not an in-game training feature.

After a failed run, distinguish an information error from an execution error. Did you press the location you were told, or did your action differ? Did the team observe the result before issuing another command? Record one example and change one habit for the next run. A vague decision to “be faster” will not resolve a shared coordinate mistake.

Can I solve from a remembered color? A remembered color is not enough when you cannot inspect the current panel. Request the live result of the team’s lookup and its physical location. A solution from an earlier attempt may refer to different inputs.

Who checks my spoken readback? Deaf cannot hear it. Mute can flag a mismatch through the agreed visible communication, with Deaf returning the correction. Rehearse that loop before depending on it under pressure.

Should I replay the whole sequence after an interruption? First establish the current state. Some actions may already have been accepted. The manual and observed panel determine what comes next; an interruption by itself is not evidence that the sequence reset.

For your next BOMBANANA Blind Monkey attempt, insist that every new target is named before an action begins. Combine that with a visible-result check from Deaf and a clear correction route through Mute. Once the loop is consistent, practise shortening the language without removing the fields that prevent mistakes.