BOMBANANA! Roles Explained

BOMBANANA! is built around three asymmetric monkey roles. Each role has a different communication limitation, which turns bomb defusal into a coordination problem rather than a simple information-sharing task.

This page summarizes the public role design, explains the team information loop, and points to focused beginner pages for each role.

Role overview

Role	Public role idea	Beginner page
Blind Monkey	Operates the bomb but depends on teammates for key information.	Blind Monkey guide
Mute Monkey	Can use the manual but cannot directly speak instructions.	Mute Monkey guide
Deaf Monkey	Can see and speak but cannot hear team voice communication.	Deaf Monkey guide

Why the roles matter

The role split means one player cannot simply read everything and tell everyone what to do. The team has to move information through a triangle: Blind Monkey executes, Mute Monkey interprets manual information without normal speech, and Deaf Monkey can speak but needs non-voice feedback.

That triangle is the reason BOMBANANA! needs role guides before it needs complete Puzzle Module solutions. New teams first need to understand who can send information, who can receive it, and where the communication chain can break.

Team information loop

The easiest way to understand the roles is to treat the team as an information loop. Blind Monkey turns instructions into action, Mute Monkey helps translate manual-focused knowledge into signals, and Deaf Monkey can speak useful observations while needing feedback that does not depend on normal voice chat.

Step	Team question	Role focus
Observe	What information is available right now?	Blind Monkey and Deaf Monkey may surface different parts of the situation.
Interpret	Which rule path, option order, or decision seems relevant?	Mute Monkey turns manual-focused information into usable signals.
Confirm	Has the team understood the same instruction?	All roles need short confirmations before action.
Act	What should change on the bomb?	Blind Monkey executes only after the target and action are clear.

Beginner coordination principles

• Agree on short, repeatable callouts before starting.
• Separate observation, instruction, and confirmation so the team does not talk over itself.
• Decide how Mute Monkey can express yes/no, option order, and uncertainty.
• Decide how the team can correct or approve Deaf Monkey without relying on voice.
• Use the demo and public Steam information as the boundary for current claims.
• Expect role-specific strategy to change after full-release details are confirmed.

Suggested reading order

Start with the how-to-play guide if your team needs a first-session communication path. Use the demo guide if you are checking current Steam availability. If you already understand the premise, read the role pages in team order: Blind Monkey, Mute Monkey, then Deaf Monkey. Use the Puzzle Modules index only as an evidence boundary until deeper module information is confirmed.

Choose a role guide by your question

• Read the Blind Monkey guide if you want to understand action timing, callout confirmation, and when to stop before pressing or changing something.
• Read the Mute Monkey guide if you are searching for manual-related help, signal design, or ways to communicate without copying a full manual.
• Read the Deaf Monkey guide if you want to understand speaking callouts, missed voice feedback, and non-voice correction channels.
• Use the FAQ for short questions about Steam access, APK/mobile claims, release timing, site status, and downloads.

What still needs confirmation

Public sources support the high-level role design, but they do not confirm every final rule, every Puzzle Module interaction, or the best strategy for every situation. Deeper strategy should be updated after official release information or reliable testing exists.