Manual quick index
Cable / Wire
Count, current LED, wire colors from left to right.
A cut is returned only for a unique target position.Direction
Braille number, current LED, one shared viewpoint.
A reading of 8 requires a recheck; no direction is returned.Calculator
Enter the arithmetic result in game, then report that result and the new LED.
The tool looks up the final key; it does not evaluate expressions.Switch
Four colors and four digits in the same positional order.
Three collected color orders; no sequence for an uncovered comparison.Soundboard
The sounding cell’s Braille number and color.
Coordinates and a source example; no lookup tool yet.Morse
All five dots/dashes for one digit.
Digits 0–9 only; no complete game workflow or audio detection.Symbol
Current shape and stage; exact mappings still need verification.
A recorded Level 8 example, not a complete answer table.Lookups use collected manual references and have not been independently tested on the current build. See each guide for its source and scope; check the manual for the current run.
From panel state to one action
01 Identify: Name Cable, Direction, Calculator, Switch, or the other current panel before reporting values.
02 Report: Send only the fields the module needs and preserve the fixed order of colors, numbers, lights, or symbols.
03 Look up: Mute uses the matching module page; if a field is missing, request it instead of guessing from an old state.
04 Translate: Deaf turns the result into a position, direction, key, or input sequence Blind can execute.
05 Confirm: Blind repeats the action before committing it, then reads the panel again and treats the next stage as a new state.
- Read current state
- Find its rule
- Name the physical action
- Confirm & reread
Use different calls for “repeat the last value” and “restart the whole report.” The first repeats only the final item; the second begins again with the module name and complete state. If a wrong input changes the panel, discard the old answer even when it was correct a few seconds earlier.
How the three players use the manual
Blind handles the bomb and reports the tactile or panel information available to them. Mute holds the defusal manual and finds the rule for the named module, but cannot speak. Deaf can see and speak but cannot hear teammates, so the manual result must be turned into a short instruction that Blind can act on.
A correct lookup is therefore only the middle of the solve. A color may need to become “the second cable from the left,” a direction still needs one agreed perspective, and a sequence must keep its complete order. If the module name, state, or final action is unclear at any point, stop before entering anything and confirm it again.
What to report for each module
For Cable, report the cable count and active light first, then give every color from left to right; the returned instruction must include a physical position. Direction needs the current LED and center number or Braille value in the same packet, plus an agreed left-right perspective. Calculator begins with the complete expression, then becomes a new LED state after that result is accepted, so the arithmetic result is not automatically the final key.
For Symbol, report the visible shape, color order and current stage; the Level 8 reference shows one recorded example. Sound-trigger details and a general mapping remain unverified. Piano needs the Braille octave, active light, and full note sequence. Soundboard first identifies the sounding button before resolving its 3×3 input. Switch preserves four lights, four numbers, and their physical order until every position is confirmed and Enter is submitted. Exact answer rules for Maze, Morse, and Monkey-Says do not yet have focused pages and remain to be confirmed.
Where to find roles, levels, and online help
This manual page routes a known panel to the correct rule and explains how that result becomes one three-player action. For first-session setup, general communication, game modes, or failure review, use the BOMBANANA guide. For Campaign size and practice order, open How many levels?; for the first Calculator checkpoint, use the Level 5 page.
Lobby and player-count questions do not belong in a module answer table. Use the online multiplayer guide to prepare a session and Can two players play? when the group is short a player. Keeping rule lookup, team communication, progression, and network questions separate prevents the team from searching the wrong page during a run.
Why a manual answer did not work
First check whether the input packet was complete: module name, current stage, lights, numbers, colors, and order where required. Then check whether the lookup result became a concrete action such as a physical position, a direction under the shared perspective, or the actual number on a shuffled keypad. Finally confirm whether the panel changed after the previous input; any state change makes the old answer stale.
If the same module fails repeatedly, return to its focused page and verify the rule and required fields. If several different modules lose information at the same point in the relay, the bottleneck is more likely the role workflow, so return to the general guide and reset the team’s signals, perspective, and repeat calls. Any exact rule that cannot be confirmed on the current page stays marked as “to confirm” rather than borrowing an answer from another module.