BOMBANANA Mute Monkey Guide: Manual Lookups and Clear Signals

The BOMBANANA Mute Monkey role owns the manual lookup, but a correct rule cannot rescue an incomplete observation. Before choosing a branch, make sure you know which module is active, which stage it is in, and every field that the manual requires. Distinguish a missing value from a value that genuinely is zero, off, or absent.

Your answer needs a receiver. Deaf can see gestures and describe the resulting instruction to Blind. A private understanding of the rule is not yet a completed handoff. Keep the answer stable long enough for the relay to interpret it, and use the agreed correction signal when the spoken instruction differs from the result you intended.

Ask the team to send a compact, ordered packet instead of a stream of unrelated colors and numbers. For Cable, the guide tracks cable count, the LED and the ordered colors. For Calculator, distinguish the arithmetic result from the later LED-dependent choice. Each module page explains its own evidence and missing information; do not assume the same color has the same meaning everywhere.

If a field is ambiguous, request that field again. Reconstructing the entire packet can introduce a second error into information that was already correct. When the stage changes, however, explicitly start a new packet so the earlier state does not silently carry forward. The current manual determines which previous values need to be retained.

• Cable fields before a lookup
• Calculator worked examples

Agree on separate signals for an answer, a correction, a repeat request and an instruction to wait. Choose signals your teammates can actually distinguish using the game’s available communication. This guide does not claim a universal gesture vocabulary or a particular animation that works for every group. Practise the distinction before using it to authorize an irreversible input.

If an answer has several parts, establish its order and length. A direction sequence, a numbered position and a count can otherwise look like the same series of gestures. In a rehearsal, ask Deaf to explain what each signal meant before Blind acts. The point is to test the receiver’s interpretation, not merely whether you performed the intended gesture.

Some lookups use a property of an earlier value after the panel has advanced. Calculator is a useful practice example: the original result, its parity, the later LED and the final digit belong to different fields. If a final digit is odd, that does not make the original result odd. Preserve the field names as well as the numbers.

For cumulative sequences, note which part has already been accepted and which part the team is preparing to input. Do not let a newly observed signal overwrite the previous context simply because it is more recent. When you are uncertain, request a state check; confident delivery of an answer from the wrong stage still produces the wrong action.

• Monkey Says sequence context
• Piano octave and light-color inputs

A Chaos interruption can leave you holding an answer while the other players have moved to a different control. Treat that answer as paused. When the team returns, have Deaf identify the panel and current state before you signal the pending result again. Confirm whether Blind already carried out the previous instruction.

If the rule was selected from a partial observation, rebuild the lookup from the missing field rather than defend the old result. An interruption can reveal a pre-existing ambiguity without changing the underlying rule. Keep that distinction clear during the review: was the input stale, the rule wrong, or the signal misunderstood? Each requires a different correction.

• Level 6 interrupted-handoff rehearsal

This wiki deliberately leaves some exact answer tables and hidden achievement conditions unresolved. An absent table is not permission to fill the gap with a plausible answer. Consult the current in-game manual and have the relay supply the fields it requests. If a public explanation disagrees with the live rule, preserve the version and context before reporting a correction.

The same caution applies to a memorized example from a guide. Worked examples explain a rule using specified inputs; they do not establish what appeared on your bomb. Treat an example as a rehearsal for reading the table. Do not signal its result unless the actual conditions independently lead to that result.

• Source boundaries and corrections
• Report a rule discrepancy

Should I begin solving before all fields arrive? You can find the relevant manual section, but do not authorize an answer while a required branch condition is unknown. Locating the section and selecting the final rule are different steps.

What if Deaf interprets a signal incorrectly? Use the agreed stop or correction signal, return to the answer’s format, and have the interpretation relayed again. Adding more gestures to an already ambiguous stream can make the problem harder to identify.

Does a correct lookup guarantee success? No. The answer still has to become an unambiguous physical action and be executed against the current panel. Review the returned instruction and observed outcome as part of the same task.

For the next BOMBANANA Mute Monkey practice, choose a module the group understands and intentionally withhold one example input during an off-clock discussion. Identify exactly why the lookup cannot finish, request that field, then signal the answer in the agreed format. Review where uncertainty was resolved. This makes the exercise useful even without a successful full run.