Read the LED color and the Blind player’s number together. Find that pair in your in-game manual, relay one arrow direction, then read the next clue before pressing again.
See a recorded sequence ↓Two clues. One clear instruction.
The recorded panel has arrow controls and a central raised-dot clue. The players initially describe the dots differently, but the Blind player can report the number. Counting visible dots is not a substitute for that reported value.
Identify the panel and its LED.
Start the callout with “Direction,” followed by the light color. Keep clues from another module out of the exchange.
Get the number from the Blind player.
Pair it with the current color: “Blue, seven.” Do not replace the number with “two dots” or a description of the dot pattern.
Find that exact pair in the manual.
The manual reader chooses the direction for both clues together. One color alone is insufficient: the recorded Blue examples below include both Up and Down.
Relay one direction and press once.
Use Up, Down, Left or Right, with a communication method your team has agreed on. Confirm the meaning before touching the control if a gesture is unclear.
Read the next clue afresh.
The example changes color and number between presses. When the panel advances, collect both clues again; do not reuse the previous color while reading a new number.
Follow one recorded sequence.
At 21:16 in Stumpt’s Demo recording, the transcript moves from Wires to Direction. It records these four clue–answer pairs before the players move on to Switch:
- STEP 1Blue · 7Down
- STEP 2Yellow · 5Up
- STEP 3Red · 9Up
- STEP 4Green · 2Up
The useful pattern is the exchange: new color, new number, one answer. The last three answers happen to be Up; that does not make Up a default for these colors or for later stages.
The supplied transcript contains the four pairs and then a description of the Switch panel at 22:04. This supports a reported transition to the next module. It is not independent frame-by-frame confirmation of the Direction success indicator; the team later runs out of time on Switch, so this is not a successful whole-bomb example.
Compare the recorded pairs.
These ten pairs come from selected moments in the same Demo transcript. They help explain the relationship between the clues and the answer. Missing combinations are unknown here, not invalid inputs.
| LED | Number | Reported arrow | Video segment |
|---|---|---|---|
| Blue | 5 | Up | 12:11–12:39 |
| Blue | 2 | Down | 12:39–13:06 |
| Blue | 7 | Down | 21:16–21:39 |
| Green | 1 | Left | 12:39–13:06 |
| Green | 2 | Up | 21:39–22:04 |
| Red | 7 | Right | 19:47–20:20 |
| Red | 5 | Left | 20:20–20:52 |
| Red | 9 | Up | 21:39–22:04 |
| Yellow | 1 | Down | 20:20–20:52 |
| Yellow | 5 | Up | 21:16–21:39 |
For example, Blue 5 is followed by an Up instruction and a new clue around 12:11–12:39; Blue 2 receives Down around 12:39–13:06. Preserve the full pair when passing information between players.
Do not lose a correct answer in translation.
How do we communicate Left and Right?
Agree on distinct signals before the round. In the recording, the team chooses one finger for Left and two for Right, then initially mixes them up around 11:44. That convention is their team agreement, not a game rule. Rehearse whichever signals you use and keep their meaning consistent.
One player sees dots, another reports a number.
Pass the Blind player’s reported number to the manual reader. Around 10:34 and 13:38–13:57, the recorded team discusses why descriptions of visible dots were causing confusion. Do not infer a number by counting dots or applying an unverified Braille chart.
Should we reread the LED after every press?
Yes, confirm it with the next number. The recorded sequence goes Blue, Yellow, Red, then Green. Keeping the previous light color can create a different clue pair even if the new number is correct.
Our color–number pair is not listed here.
Read the matching entry in your current in-game manual. This page contains ten transcript observations, not every possible input. Do not extend a pattern, assume a default arrow or treat an absent row as an error in the game.
We pressed an arrow and it did not advance.
Check the panel identity, current LED, reported number, manual entry and communicated direction before trying again. If the screen has changed, obtain a fresh pair. An uncertain gesture is a reason to repeat the message, not to press another arrow at random.
Source and version limits.
The examples use Stumpt — Defuse while being Deaf, Blind, and Mute! - Bombanana. The source describes the game as a Demo and discusses its future release near the end. The Direction observations on this page were extracted from the supplied transcript; no full-release playtest or independent frame-by-frame verification is claimed.
The complete direction mapping, allowed number range and full-release compatibility are still unconfirmed here. Video timestamps lead to surrounding segments because the transcript groups several speakers and actions together.
Continue with the manual overview for team communication, compare the separate Switch module, or return to the module directory.
Transcript reviewed September 9, 2026. Demo examples are retained with their evidence limits. About this independent guide.