BOMBANANA Symbol Module Guide and Callouts

Publication status: candidate workflow

This is a candidate observation and communication workflow, not a verified full-release answer sheet. It stays out of the index while the module roster, exact stage rules, Campaign appearances, timer, and mistake behavior remain unverified. Do not treat this page as proof that Symbol appears in a specific level.

Quick answer

Treat the BOMBANANA Symbol module as a staged lookup. Identify which symbol produces the sound, report the current stage, list the available colored buttons, and let the manual reader return one color. The bomb handler repeats that color and waits for confirmation before pressing.

Collected community guidance describes four sequential stages, but a permanent full-release stage table and level appearance map are To be confirmed. Use the manual guide for the current rule and the communication guide for a clean handoff.

Find the sounding symbol first

The first question is which symbol makes the sound. Do not describe every symbol as if it were already the answer. Test or identify the relevant symbol through the current game procedure, then stop the search phase before the team starts discussing colors.

Name the module before the report. A useful packet contains the current stage, the sound-producing symbol, and the colored buttons that can be pressed. If a symbol is hard to identify, report the uncertainty directly and ask for another observation. The three Monkey roles guide explains how to keep tactile operation, visual reporting, and manual reading distinct.

Keep the stage attached to the packet

Symbol uses a sequence of stages. The same visible symbol can require a different answer when the stage changes, so the stage number belongs in every callout. After a correct input, report whether the panel cleared or advanced before collecting the next answer.

Do not reuse the previous color after a stage change. A new stage is a new state. If an interruption makes the current stage unclear, use the agreed stop signal and rebuild the packet from the module name.

A safe Symbol procedure

1. Name the Symbol module.
2. Identify the sound-producing symbol.
3. Report the current stage.
4. List the available colored buttons in a fixed order.
5. Let the manual reader choose the color for that stage.
6. Repeat the color and confirm the physical button before pressing.
7. Report the result and collect the next stage if the panel continues.

This order keeps the search phase, lookup phase, and input phase separate. That is more reliable than shouting several possible colors while the bomb handler is already moving a hand.

Common mistakes

The most common communication error is skipping the stage. Another is describing the symbol with a nickname that changes between players. Agree on short names before a serious run, and use the same name whenever the symbol appears again.

The third error is carrying an answer through an interruption. If a hazard, overlap, or missed signal breaks the packet, do not resume from the last half-remembered color. Start with the current stage and sounding symbol again.

Evidence boundary

The current evidence supports the workflow of finding the sounding symbol, attaching the current stage, and resolving a color input. It does not verify every stage mapping, a universal symbol catalogue, exact Campaign appearances, timer behavior, or a permanent full-release table. Those details remain To be confirmed.

The current in-game manual should decide the live answer. A practice table can help a team learn vocabulary, yet it cannot replace a fresh state read after an update or a stage transition. Link the Modules database when a team needs the broader guide set.