BOMBANANA Color Slider 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 rule, Campaign appearances, timer, and mistake behavior remain unverified. Do not treat this page as proof that Color Slider appears in a specific level.

Quick answer

The BOMBANANA Color Slider module should be handled as an ordered state packet. Name the module, number the sliders from left to right, report the color of each slider, and let the current in-game manual return the movement for every position. Repeat the complete numbered instruction and wait for confirmation before moving anything.

The public first-party records do not verify a permanent full-release level map or complete answer table for this module. That part is To be confirmed. The manual guide and communication guide provide the safe relay that remains useful when the exact rule needs to be read live.

Collect the right inputs

Start with the words “Color Slider” so the manual reader opens the correct section. The collected module procedure names two required inputs, Slider order and Color of each slider. Preserve both fields in the same order from the first observation through the final action.

Number the controls before discussing the answer. “The third slider is blue” is a usable observation. “Blue, red, yellow, up, down” is not a safe packet if the team has not agreed which position each word belongs to. The three Monkey roles guide explains why the observer, manual reader, and bomb handler should keep their jobs separate.

Separate observation from the manual result

The player who can see the panel reports the current colors. The manual player resolves the rule. The player operating the bomb repeats the physical sequence and waits for a confirmation signal. No one should convert an uncertain color into an answer simply because the timer is moving.

Keep the manual result in numbered form. If the result is up, down, up, down, say which movement belongs to each slider. If the manual reader is missing one color, request that field instead of accepting a list of guesses. A changed stage or interrupted callout expires the old packet and requires a fresh read.

A safe Color Slider procedure

1. Name the module and agree on the left-to-right numbering.
2. Report every slider color in that numbered order.
3. Let the manual reader check the current rule.
4. Return one movement instruction for each numbered slider.
5. Repeat the full sequence before the bomb handler touches a control.
6. Move one control at a time and report whether the panel clears, changes, or expects another input.

This sequence adds a little speech, yet it removes the most common indexing error. The direction module guide uses the same separation between what one player observes and what the manual decides.

Common failure points

An unnumbered up or down list can shift by one position when a player misses a word. A color without a control number is incomplete, and a movement without a current stage can belong to an older state. When two people speak at once, use a neutral stop signal, discard the last instruction, and restart from the module name.

Do not carry a color sequence from a previous bomb into the next one. The module family may look familiar while the current state is different. The live panel and manual matter more than memory, a screenshot, or a community answer list.

What the evidence does not settle

The current evidence supports the input order and the team workflow. It does not settle a universal Color Slider table, a permanent Campaign appearance list, an exact timer, a mistake allowance, or a full-release answer sequence. Those fields remain To be confirmed until a current reproducible record supports them.

When a later source provides a verified row, record the exact inputs and result together. A failed attempt alone cannot show that the rule changed because observation, lookup, relay, and execution errors can produce the same outcome. Keep the module page useful without pretending that an unverified table is official.