BOMBANANA Direction Module: Braille and Lights

The short answer

The BOMBANANA! direction module asks the team to combine two clues before pressing an arrow. One clue is a Braille or number pattern on the panel, and the other is the active light state. Report both, let the manual reader choose the direction, and confirm the team’s left and right perspective before the bomb handler acts.

This module creates two separate risks. The first is reading the Braille or number incorrectly, and the second is turning a correct answer into the wrong physical arrow. Keep those risks separate during the callout so the team knows whether it needs a new value, a new light read, or a perspective correction.

Give the tactile clue an owner

The Blind Monkey is the role associated with touching and operating the bomb. On a direction panel, this player may be the only teammate who can feel the raised-dot pattern clearly, so the value should come from that player rather than from a guess based on the shape on screen. Report the value in a fixed form and ask for a repeat when one dot is uncertain.

The Deaf Monkey can see the bomb and speak, which makes this role useful for identifying the active light and translating the final gesture. The Mute Monkey reads the manual and matches the pair of clues to a directional rule. The exact path can feel slow at first, yet each role exists because no one player is meant to own the complete answer.

Name the module before the clue. Then report the Braille or number value, report the light state, state the agreed perspective, and wait for the manual decision. This order gives the manual reader a chance to open the correct rule page before the team starts describing unrelated details.

Keep the light state separate

The direction rule uses the Braille number and the color of the light. A light color is not a decoration that can be ignored after the number is known. It is part of the input packet that chooses the final arrow.

Use one sentence for the value and another for the light if the team tends to talk over itself. The visual player should name the light exactly as it appears, and the bridge should repeat it before the manual reader resolves the pair. If the light changes, discard the earlier direction and report the new state.

Do not merge “number three” with “press left” until the manual has confirmed the row and light combination. The number identifies a branch, while the light selects a direction within that branch. Treating the branch as the answer is a common reason that a team presses too early.

Make direction words unambiguous

Decide whose perspective controls left and right before the timer starts. The safest choice is usually the bomb handler’s view or the module’s own left-to-right view, yet the game does not define a universal team shorthand. The decision belongs to the players and must stay stable for the whole run.

A good final call names the panel, the direction, and the perspective. The handler can then repeat the physical action before pressing. If the bridge says “left” and the handler asks “your left or mine,” stop the sequence and restate the convention rather than relying on intuition.

The same rule applies to up and down when the camera or hand position changes. Pointing at a screen can be ambiguous when the player at the bomb has a different view. Stable words and a repeatable confirmation signal protect the final input from that mismatch.

Treat old matrices as practice material

A blog post reproduces a four-row matrix that pairs Braille numbers and light colors with arrow directions. It also contains a screenshot reference from a June 2026 Demo context. Those details can help a team understand the shape of the rule, yet the post does not establish that every row is correct or unchanged in the full release.

The complete row and light mapping is therefore To be confirmed for a live build. Do not publish a permanent cheat sheet from one screenshot, and do not press an arrow because an older video used the same number. Read the current manual and record the build when your team verifies a stable rule.

This boundary matters because specific names, observations, and rules may change. The official launch announcement confirms a larger puzzle-module roster, while it does not publish a full public direction solution table. A clear uncertainty label is safer than a confident wrong arrow.

When to stop and recheck

If the tactile player cannot distinguish one raised dot, pause before the manual reader chooses a row. Repeat the value and ask the visual player to report the light again if the panel has changed. A second read is useful only when the team knows which part of the input was uncertain.

If the light changes during the callout, discard the earlier pair and start a new one. If the manual reader finds a conflict between the current page and an older reference, use the current in-game manual as the decision point and keep the exact mapping To be confirmed until it is verified. If the arrow is clear but the perspective is not, restate left or right from the handler’s view before any press.

A failed input can therefore be diagnosed in four small steps. Check the tactile value, check the light, check the manual row, and check the physical perspective. This sequence gives the team a useful correction without turning an uncertain rule into a permanent answer table.

Practice the relay

Campaign gives a structured place to practice the sequence of reading, resolving, confirming, and pressing. Custom can help the team focus on one module family or adjust the bomb conditions once the mode is available. The game modes guide explains how those choices differ.

Run a slow drill with one person owning the tactile value, one owning the light, and one owning the manual. Repeat the pair before the direction is announced, then repeat the direction with the chosen perspective before pressing. After a failure, identify whether the value, light, rule branch, or perspective was the broken link.

Read BOMBANANA! roles for the sensory limits, BOMBANANA! manual for the wider handoff, and BOMBANANA! communication for a fixed callout order. Use the math module guide when your group needs practice with multi-stage state changes.