BOMBANANA Get three monkeys in one room

A BOMBANANA! bomb does not start when the timer appears. It starts when three Steam clients agree they are in the same van. Launch on 2 September 2026 added the tools demo groups begged for: a server browser, room codes, and a random role button. You still need exactly three players. Two in a party and a “we will find someone later” plan is not a lobby. It is a main menu.

This page is the host script. Pair it with system requirements so the third PC can actually join, and with the callout sheet so the first module is not where you invent a language. Role jobs stay on the players hub. The co-op guide covers the social contract. Here we only get the room standing.

Three players, no substitutes

Steam’s product is three-player online co-op. There is no solo defusal, no two-monkey mode, and no documented bot seat. Windows and macOS can mix. Consoles and phones cannot fill a slot. If a friend is installing, wait. A host who starts Campaign “to look at the airplane” with two people will not get a practice bomb — they will get a missing monkey.

Before invite, confirm all three launched the full game (app 4656000), not an old demo shortcut, and that everyone restarted after any Steam news download. Mixed builds are a classic join failure; the demo even needed a 16 June 2026 lobby-join hotfix. Patch notes explain how to verify a post without inventing a version number.

Room codes and the server browser

You do not have to be Steam friends first. That is a launch change. Host creates a room, shares the room code in a chat Deaf Monkey can read (text, not a whispered Discord sentence they will never hear in-game). The other two enter the code and appear in the van lobby.

The server browser lists public rooms. Use it when you want strangers, not when you are teaching getting started. Public tables will not pause while Mute studies the gesture dictionary. Name your public room honestly: “Campaign 1 teaching” or “Endless, mics on” beats “asdasd.” If a room is full, it already has three monkeys — look elsewhere instead of sitting in a queue that cannot exist.

Private code first for friends. Browser later for people who already know Blind, Deaf, and Mute.

Role lock versus random role

Default advice for a new trio: lock roles on purpose. Put the most patient speaker on Deaf (they talk constantly and hear nothing back through the game). Put the calmest hands on Blind. Put the person who can read a table under pressure on Mute. Lock those seats in the lobby UI so a late join does not shuffle them.

The random role button exists for groups that already survived a few Campaign levels and want to stop arguing. Randomize before the bomb, never after module one. If you randomize, immediately announce the result out loud and in text: Deaf cannot hear the celebration, Mute cannot shout “I’m Mute.” Keep the roles tier list for theory; the lobby only cares that each seat is filled and known.

Do not “main” a role by sitting in the wrong chair and hoping. The information split is the game. Swapping after a strike is legal as a house rule, but you will throw away the callout sheet muscle memory you just built.

Mic check, because voice is role-restricted

In-game voice is not a full party chat. Mute cannot speak on it. Deaf cannot hear it. Blind can speak and hear but cannot see the LED you are describing. A Steam mic that “works in other games” can still fail here if one person is bound to push-to-talk and another is open mic.

Run this check in the lobby, with mouths visible — launch added voice-synced mouths, which is a useful debug tool:

1. Blind talks. Mute should hear it. Deaf should not hear it in-game. If Deaf hears Blind through the game channel, something else (Discord overlay, nearby speakers) is leaking, which can be a gift or a cheat depending on your house rules — agree it.
2. Deaf talks. Blind should hear instructions. Mute should hear them too. That path is how gestures become words.
3. Mute uses the emote wheel (everyone has one at launch). Deaf must be able to see the gesture. Blind must be told what it meant.
4. Confirm push-to-talk versus open mic. Deaf gets no audio cue that Blind started talking; visual mouth sync helps if they are looking at the monkey instead of the bomb.

Many trios keep Discord (or the official Discord LFG rooms) open so Deaf can read text. That is allowed by physics, not required by Lefto. If you do it, decide whether Discord is “Deaf’s hearing aid” or “illegal extra channel” for your group. Then mic check both.

Session checklist

1. Three clients on Windows or macOS, specs OK, same build.
2. Host opens a private room code (first bombs) or a clearly named browser room (veterans).
3. Everyone joins; count heads. If you see two monkeys, wait.
4. Lock roles or hit random role once, then announce seats in text and voice.
5. Mic check the restricted channel. Test Mute’s wheel. Agree yes / no / wait / repeat / 0–9.
6. Agree a full-stop phrase. Put the callout sheet on a second screen.
7. Options: two colorblind modes exist; full controller support exists; read controls if someone rebound interact.
8. Pick Campaign for teaching, Custom for a long timer, Endless only when the loop is boringly clean. Mode flavor: modes tier list.
9. Start. Do not add a fourth friend “to watch” inside the bomb role slots — they are not a player.

If join fails, do not spam the bomb start. Recreate the room, re-share the code, verify Steam files, and check patch notes only if Lefto actually posted a network hotfix. More tools live on the tools hub. Launch feature context: launch notes. Official invites and socials: wiki hub.