BOMBANANA! Field Guide
BOMBANANA Guide: Start Your First Run
A direct, verified starting point for a three-player bomb-defusal session.
The short answer
BOMBANANA! is a cooperative puzzle game for exactly three monkeys: Blind, Mute, and Deaf. Gather three players before starting because the asymmetric information design is built around the complete team.
The official materials do not establish a standard two-player or four-player substitute. Start with the confirmed team size, then learn what each role can and cannot communicate.
Know the role boundaries
Blind Monkey can touch the bomb but cannot see the bomb, its colors, or the screen. Mute Monkey is the only role that can read the bomb disposal manual but cannot say what it knows. Deaf Monkey can see the bomb and team gestures but cannot hear sound.
These are the official boundaries, not a complete list of every interaction. Do not add fan-made limits or assume that a role has an ability that the sources do not state.
Set a communication plan
The official materials do not require one universal callout system. As a practical recommendation, agree on a short confirmation signal, identify who announces visible information, and say when an action is complete.
Keep observations separate from instructions during the countdown. This recommendation helps the team coordinate, but it is not a mandatory keybind, menu path, or answer sequence.
Join through official routes
The launch information confirms a Global Lobby Browser, a server browser, and room codes. It also says players do not need to add one another as Steam friends first.
The exact button order, room-code format, and default controls are To be confirmed in the current build. Use the labels visible in-game instead of relying on an old screenshot.
Make the first bomb manageable
Identify who can see the device, who can read the manual, and who can interact without visual information. Ask for one observation at a time and confirm each action before moving to another part of the bomb.
The verified sources do not publish a universal first-bomb solution, timer, mistake allowance, or fixed module order. A careful communication rhythm is safer than an invented shortcut.
Use Campaign to learn
Campaign contains 30 handcrafted levels that become harder, and defusing bombs unlocks new levels. That makes it the clearest confirmed progression route for learning the communication loop.
Level names, module pools, exact timers, and fixed answers are not established in the verified material. Detailed walkthrough claims remain To be confirmed until version-matched.
Avoid common assumptions
The sources do not confirm solo bots, split-screen, role substitution, cross-platform play, or host migration. Those features are not inferred from the general multiplayer label.
If a player cannot use an expected channel, restate the observation using what that role can actually perceive. This keeps the first session grounded in verified information.
What this guide deliberately omits
This page uses official Steam and Steam Community information for player count, roles, communication options, and modes. It does not publish default controls, module answer tables, role-swapping rules, or invented values.
Where the current build has not been checked, the wording is To be confirmed. That boundary keeps a BOMBANANA guide useful without turning guesses into instructions.
Evidence used for this page
This page answers the search for a first BOMBANANA guide using the verified material collected for the project. It combines the exact three-player team, the three role boundaries, official joining options, and broad mode structure rather than treating every search result as equally reliable.
The page combines the official Steam listing with the dated Steam Community material available in the project research. Source links are kept with the page so readers can distinguish a first-party statement from a future research lead.
What is confirmed here
The confirmed scope is deliberately specific: the exact three-player team, the three role boundaries, official joining options, and broad mode structure. These statements are written as facts because they are supported by the sources attached to this page.
The scope is also designed to prevent keyword drift. Related topics can be useful links, but they do not become facts on this page merely because they are popular in community discussions.
What is deliberately absent
This page does not claim default keys, fixed module answers, solo replacements, and unsupported multiplayer features. The collected research does not provide enough first-party or reproducible current-build evidence for those details.
Each missing item remains To be confirmed. That label is part of the answer because a precise-looking number, code, mapping, or release claim would be misleading without a verified source.
How players should use this page
Use the confirmed facts to frame the search and the practical checklist: Learn the role boundaries first, then agree on a confirmation signal and use an official lobby or room-code route. This keeps the page useful without turning a recommendation into an official mechanic.
When a live situation differs from the wording here, check the current build, record the visible state, and compare it with the source date. Do not solve an evidence gap by importing rules from another game.
Version and update standard
A future update should preserve the distinction between historical facts, current snapshots, player recommendations, and unverified claims. If a new player asks for a number or a control path that is not in the verified sources, label it To be confirmed instead of guessing.
Game builds, storefront labels, prices, and community explanations can change. A future revision should add the new check date, preserve the old context when it matters, and replace a statement only when a reliable source supports the change.
Research boundary
The page is one part of the larger BOMBANANA knowledge structure: role pages explain information limits, the manual page explains communication, and the modules pages isolate rules that still need testing.
Keeping those boundaries visible prevents one uncertain page from silently supplying facts to another. Until the missing evidence is verified, the correct wording remains To be confirmed.