BOMBANANA! Blind Monkey Guide

Blind Monkey is the hands-on role in BOMBANANA!'s public three-player setup. This player is closest to the bomb, but the role is designed around missing information, so good Blind Monkey play starts with careful confirmation rather than fast guessing.

Role summary

Public Steam information presents Blind Monkey as the player who operates the bomb while depending on teammates for key information. That makes the role action-oriented, but not self-sufficient. Blind Monkey needs the rest of the team to translate what should be done into clear, safe steps.

What the team needs from Blind Monkey

• Report only the information that is actually available to this role.
• Repeat critical instructions before acting when timing allows.
• Confirm completed actions with short phrases such as "done" or "changed".
• Stop the team when an instruction is ambiguous instead of filling in the blank.

What Blind Monkey should ask for

Blind Monkey should not have to guess what teammates mean by a rushed callout. The strongest beginner habit is asking for the exact missing piece: which item, which order, which action, or whether the team wants a pause before anything changes.

• Ask teammates to separate observations from instructions.
• Request one actionable step at a time when the situation is unclear.
• Confirm the target before pressing, turning, moving, or changing anything.
• Ask Mute Monkey to repeat the signal order if two options look similar.

Information flow

Blind Monkey should not be treated as the team's puzzle solver by default. A cleaner flow is: teammates identify what information is needed, Blind Monkey reports or acts on the bomb, then the team confirms the next instruction. This keeps the role from becoming overloaded with both execution and interpretation.

When to stop and confirm

The role is most fragile when the team moves from discussion to action. If a signal, label, or direction can mean more than one thing, Blind Monkey should pause and ask for confirmation. A short delay is usually safer than turning an unclear callout into a wrong action.

First-session tips

• Ask for one instruction at a time until the team has a stable rhythm.
• Use different words for observation and action, such as "I see it" versus "I pressed it".
• Tell the team immediately when two options look similar or when a callout is unclear.
• Do not turn a demo observation into a permanent rule unless a reliable source or later testing supports it.

Common beginner mistakes

• Acting before the team has confirmed the exact target.
• Reporting too many details at once without saying which detail matters now.
• Using the same phrase for seeing something and changing something.
• Letting timer pressure replace confirmation when a callout is ambiguous.
• Assuming a Puzzle Module pattern is final before reliable evidence exists.

How Blind Monkey fits with the other roles

Blind Monkey turns team decisions into action. Mute Monkey may help interpret manual information through signals, while Deaf Monkey may provide spoken callouts that still need a non-voice feedback path. The roles overview explains this triangle in more detail.

If you are checking current play access, use the demo guide. If you are looking for module evidence, use the Puzzle Modules index as an evidence boundary rather than a complete solution list.

What still needs confirmation

This page explains the public role design and beginner coordination logic. It does not claim to know every full-release Puzzle Module interaction, timing rule, or optimal Blind Monkey strategy.