bombanana: The Real Puzzle Is Shared Information

bombanana is a three-player co-op bomb-defusal game built around divided information. The blind player can touch and manipulate the bomb but cannot see it; the deaf player can see the bomb but cannot hear the team; the mute player can read the disposal manual but cannot speak. The winning skill is not fast clicking. It is precise information transfer.

Each role holds a different kind of evidence. The player who can see the device is not simply a narrator; they must encode the layout so someone else can turn it into an action. The tactile dot panel creates another asymmetry: the person who can read it is not necessarily the person who can consult the manual. No one gets the whole answer for free.

A workable call has a fixed order: module, reference frame, full visible state, requested action. Start by naming what is in front of you—wires, arrows and dots, a calculation panel, or a lever. Then fix the viewpoint. Only after that should the team select an action.

For a wire module, report the lamp color, the number of slots, the complete color order from left to right, and every blank position. If a position is empty, say so; an absent wire makes later position calls unsafe. Wire count by itself is not a reliable answer.

The most dangerous shortcut is “cut the third wire.” That phrase is incomplete until everyone shares the same reference frame. “Third from the operator’s left” is safer than simply saying “third.” If two layouts start with the same color, repeat the full sequence from the beginning instead of sending a partial clue.

The lamp is a recurring trap. In some calls it sounds irrelevant; in another table it determines the correct row. This disagreement is easy to miss: one person may report no light while another expects one. The safest inference is to report the lamp state every time, even when somebody thinks it does not matter. That is a conservative operating rule, not a claim that every module uses the same test.

Some directional layouts show arrows and dots without a number. Other layouts combine a colored light with dots or a value. A lever may already be up or down, so say its current state and its intended state. A command such as “push it” is incomplete if the correct solution is to leave a lever down.

Left and right create another failure point. A direction must be anchored to the operator’s viewpoint or to a fixed edge of the panel. “My left” and “your left” are not automatically the same place.

The manual is not one flat answer sheet. It can contain separate tables or schemas for different combinations of light, position, dots, number, and direction. A matching color or number can route the team to the wrong schema if the module itself was misidentified. The safest opening move is to name the module before naming the action.

There is no universal gesture language waiting to rescue the team. A rotating hand can mean “give me more,” while a directional motion may be understood as “up” or something else. Hand gestures are not a substitute for structure; they are a low-bandwidth channel. Use them for repeat, yes, no, and confirmation—not for carrying the entire state of the bomb.

Calculation panels expose another hidden disagreement. The visible equation is only the first layer. The team may still need the result, the lamp or extra cue, whether the result is odd or even, and the correct selection. Skip one of those steps, and even a mathematically correct answer can arrive at the wrong button. Report the lamp state and the requested condition together. Pressing harder will not resolve a reporting error.

After every accepted action, restate what remains. Do not assume that an old color or order still applies. Repetition is not wasted time when the clock is running; it filters out partial messages before they become mistakes.

Role rotation matters for the same reason; it changes the team’s information map, not just its difficulty. A player who previously supplied visual information may suddenly depend on another player’s description. A communication habit that worked on one stage can fail immediately after the roles change.

The answer is simple: winning depends less on reflexes than on transmitting a complete, shared description of the bomb. The bomb is only one object; the real puzzle is keeping three incomplete descriptions aligned.

A complete call is a packet: module name, fixed reference, every visible condition, intended action, and acknowledgment. A correct rule can still fail when one link in that chain is vague.