BOMBANANA Guide
Start here for BOMBANANA demo help: role limits, team callouts, module status, lobby and voice troubleshooting, video evidence, and focused guide pages.
BOMBANANA has strong early Steam and video signals, but public deep guide material is still thin. This site therefore starts with role clarity, communication rules, known issues, and careful module notes instead of pretending to have a complete wiki.
The launch pages should help a new three-player team start faster while clearly marking which module details need manual verification.
Step-by-step guide
- Assign roles before the bomb
Confirm who can see, hear, speak, read, and interact. If the team has to discover these constraints during the timer, every module becomes harder.
- Agree on short callouts
Use short shared words for colors, positions, numbers, buttons, and uncertainty. Long descriptions create more confusion than silence.
- Track confirmed module behavior
Record what each module asked for, which role had the missing information, and what caused failures. Expand exact pages only after verification.
- Check lobby and voice before serious runs
Official community notes mention lobby and voice issues. Treat technical setup as part of the first guide experience.
- Use a first-session checklist
Before optimizing modules, confirm team size, roles, voice delay, one-word callouts, and who records failed attempts. This prevents the first round from becoming pure noise.
- Run a simple during-round loop
Keep the loop short: report clue, translate instruction, confirm action, act, then note the outcome. If two people talk at once, reset to report and instruction.
- After a failed attempt, save one lesson
Do not restart instantly. Write one failure cause: unclear role handoff, bad callout, unverified module behavior, lobby/voice issue, or rushed input.
- Avoid common co-op mistakes
The most expensive mistakes are long descriptions, no confirmation words, role overlap, and publishing module solutions before anyone verifies them in the demo.
Quick reference
First-run team setup
| Area | Setup rule | Why it matters |
|---|---|---|
| Roles | Say each player limitation out loud before starting. | Prevents role confusion under timer pressure. |
| Callouts | Use one short word for repeated concepts. | Keeps communication fast. |
| Modules | Mark unverified solutions as provisional. | Avoids publishing wrong guides. |
| Lobby/voice | Test connection and delay before a real attempt. | Technical issues waste the first session. |
Start here route
| Player need | Do first | Then read |
|---|---|---|
| New team | Assign roles and test voice. | Roles and lobby fixes. |
| First round | Use report -> instruction -> confirm -> act. | Team communication. |
| Module confusion | Label evidence before writing a solution. | Modules evidence index. |
| Repeated failures | Write one failure cause after each run. | Common mistakes section. |
FAQ
Is this a complete module wiki?
No. It is a launch guide hub. Public module evidence is limited, so exact module pages should be expanded after manual demo verification.
What should a new team learn first?
Role limits and callouts. Those two things make every later module easier to solve.
What should we do after a failed run?
Record one cause before restarting: unclear role handoff, weak callout, unverified module behavior, voice/lobby issue, or rushed input.
Sources
- BOMBANANA full Steam page Official full-game facts and media.
- BOMBANANA demo Steam page Official demo facts and role premise.
- SteamDB demo charts Player and review signal.
- Steam Community hub Official hotfix posts and player questions.
- YouTube recent BOMBANANA guide search Manual recent-video validation.