Skip to content
Beginner Guide

BOMBANANA Guide for First Runs, Roles, and Bomb Tips

Use this BOMBANANA guide to prepare three players, understand the Blind, Deaf, and Mute Monkey roles, choose Campaign, and build safe callouts.

9/3/2026 Last updated: 9/3/2026 6 min read

FAQ

How many players does BOMBANANA! require?
BOMBANANA! is an online co-op game designed for exactly three players working together.
Which mode should a new team try first?
Campaign is the clearest starting point because it presents 30 handcrafted levels in sequence.

Start with three players

BOMBANANA! is a three-player online co-op bomb-defusal game. One player takes the Blind Monkey role, one takes the Deaf Monkey role, and one takes the Mute Monkey role. The game gives those players different limits on sight, sound, speech, manual access, and bomb interaction, so the solution has to move through the whole group.

Bring the full trio together before opening a serious run. The official description is built around exactly three monkeys and does not confirm a two-player workaround or a four-player plan. Treat the player count as part of the puzzle design rather than a lobby detail you can solve later.

Learn what each role owns

The Blind Monkey can touch and operate the bomb, yet cannot rely on visual colors or on-screen text. This player reports physical information such as positions, counts, or tactile patterns and waits for a clear action instruction. Guessing because the timer is low turns a missing visual clue into a preventable mistake.

The Mute Monkey is associated with the defusal manual and can read the rule that turns a module state into an action. This player cannot speak the answer aloud, so the team needs gestures, text, pointing, or another agreed signal. The Mute Monkey should send one confirmed action at a time instead of trying to act out a complete rule page.

The Deaf Monkey can see the bomb and speak to the group, yet cannot hear voice communication. This player can supply visual details that the Blind Monkey cannot see and can translate the Mute Monkey’s signal into spoken direction. The Deaf Monkey also needs a way to receive confirmation without depending on sound.

Read the three Monkey roles guide before the first timer starts. The role page keeps the abilities separate from the team workflow, which makes it easier to spot whether a failure came from missing information or from a broken handoff.

Use one callout loop

Every module should follow the same broad sequence. First name the module, then report the smallest state that changes the rule, allow the manual reader to choose a branch, repeat one final action, and wait for confirmation before touching the controls. When the module changes, discard the old answer and describe the new state again.

Keep the first vocabulary small. Agree on yes, no, repeat, stop, left, right, and solved before the round begins. The exact gesture assigned to each word is a team convention, so the important fact is that all three players test the convention once before relying on it under pressure.

Use a fixed perspective for positions. Say whether left and right refer to the bomb panel or to the player handling the bomb, then keep that choice for the whole session. A correct manual answer can still fail when the final instruction changes perspective halfway through the relay.

The communication guide expands this into a reusable callout pattern. If a player cannot speak, leave a visible pause for the gesture or text response rather than filling the silence with a guess.

Choose Campaign for the first session

The full game has three modes called Campaign, Endless, and Custom. Campaign contains 30 handcrafted levels that become progressively more difficult. Endless uses procedurally generated, wave-based levels that keep getting harder, while Custom lets the team adjust bomb difficulty, explosion timers, module types, environmental hazards, and the number of allowed mistakes.

Campaign is the most direct first stop because it gives the trio a shared progression path. The official launch material does not require a new team to memorize a complete solution table before starting. It gives you a place to learn how your own group reports module names, preserves order, and confirms an action.

Endless makes more sense after your basic relay works. Its changing waves can expose whether the team can keep the same vocabulary when the next bomb is less predictable. Custom becomes useful when you want to isolate a weak module, change the timer, or make a controlled practice challenge.

See the game modes guide for the differences. The levels guide also separates the 30-level full Campaign from the seven-tier structure described in older Demo coverage.

Handle the first bomb in order

Before the timer begins, confirm that all three players know their role and can use the agreed communication channel. Decide who owns the spoken relay, who owns the manual decision, and who has the final interaction. Then say the signal vocabulary out loud or show each gesture once so a late correction does not happen beside an active bomb.

When the bomb appears, identify the module before describing every detail. The information holder should report only the state needed for the current rule, and the manual reader should reduce that state to one action. The player at the bomb repeats the action, and the team confirms it before the input happens.

After an input, check whether the module is solved or has changed state. A new display, light, number, switch position, or tactile pattern starts a new information packet. Continuing with the previous answer is a communication error even when that answer was correct a moment earlier.

Diagnose mistakes instead of rushing

If the team fails, identify where the message stopped being useful. A player may have described the right module in the wrong order, the manual reader may have received an incomplete state, the Deaf Monkey may have changed a gesture into a different word, or the Blind Monkey may have acted before confirmation. Each cause needs a different adjustment.

Change one convention before retrying. Add an explicit module name if the manual page was unclear, add a position reference if the action was vague, or add a final yes signal if the handler moved early. A slow clean handoff teaches more than a fast attempt in which everyone talks at once.

Do not treat community tables as permanent rules without checking the current game build. The puzzle modules page records the launch count and the confirmed communication pattern, while detailed individual solutions remain To be confirmed when no current source settles them.

Start with BOMBANANA! roles if the player limits are still unclear. Move to communication when the group knows the answer but keeps losing it between roles. Use game modes when you need to choose between Campaign, Endless, and Custom.

For the manual workflow, read BOMBANANA! manual. For a safe route to the game, use BOMBANANA! on Steam, and avoid unofficial APK, repack, or mirror pages. The best beginner habit is simple and repeatable. Describe the current state, confirm the next action, and only then touch the bomb.

Related Articles

Was this helpful?