BOMBANANA Slider module guide

The BOMBANANA Slider module is a chaos panel classified as chaos. The slider rises continuously. Pull it down repeatedly and clearly announce when you return to the main task. The Chaos slider rises continuously and must be pulled down before it reaches danger, then released so the watcher can return attention to the main chain. Observation, lookup, relay, and action give each monkey a checkable stage. Finish the scan with a missing-field check. A short pause here is cheaper than a confident answer built from an incomplete observation packet.

Slider has fixed Campaign appearances in Level 4, Level 5, Level 7, Level 12, Level 13, Level 15, Level 17, Level 19, Level 21, Level 23, Level 24, Level 25, Level 26, Level 27, Level 28, and Level 29, beginning at Level 4. A fixed appearance names the family, never its live answer. Start with the clearest shared state, then move toward the most demanding procedure. Early confirmation establishes rhythm without sacrificing a volatile panel. Review the BOMBANANA procedure pre-play and recollect values after loading.

Open with “Slider” so Mute reaches the correct BOMBANANA manual section. Its required packet is Slider height. Read those fields in their displayed order and attach numbers or coordinates wherever position matters. If a value is uncertain, name the missing field instead of supplying alternatives. Treat the opening description as a checksum: another player should be able to repeat the panel identity and every required field before the lookup starts.

Keep observation separate from interpretation: Deaf describes visible state, Blind contributes tactile or Braille state, and Mute performs the rule lookup. An observer who suggests an answer too early can anchor the group to a previous run. Close every action with the observed result—cleared, unchanged, or new stage—so nobody silently carries an old answer into the next exchange. For this BOMBANANA panel, familiarity never replaces a complete current packet.

For this BOMBANANA module, Deaf begins with its name and visible values in stable order. Blind adds tactile information while keeping clear of actionable controls. Mute checks the matching branch and returns only the requested result; Deaf translates that result into Blind’s viewpoint; Blind repeats, waits for confirmation, acts once, and reports the outcome. Use Blind’s viewpoint for the final instruction even when Deaf sees the panel from another angle. Viewpoint translation belongs before, not during, the movement.

The compact procedure is: Assign one permanent watcher. Use one shared threshold for intervention. Pull it into the safe zone and report that it is stable. Confirm the last main-chain action before returning. The pace may slow, but the fields should retain their order. If Mute signals missing data, return only that field unless a full reset is requested. A changed stage expires the old packet and restarts at “Slider.” A role that notices missing context should stop the chain immediately. Repairing one field preserves the packet; guessing forces the team to rebuild after a strike. This predictable BOMBANANA loop exposes skipped steps.

A watcher may leave the main task without announcing it or return after missing the last instruction, creating an invisible gap in shared state. Prevent it by attaching every answer to the Slider module, current stage, and physical position. A color without a control, a direction without a stage, or a sequence without numbered places is incomplete. Use Blind’s viewpoint for the final instruction even when Deaf sees the panel from another angle. Viewpoint translation belongs before, not during, the movement. Blind should be able to repeat the final action without needing the manual logic.

A second BOMBANANA failure is continuing through uncertainty because the timer is audible. “Hands off” is a neutral correction: recheck one missing field, or request a full reread after a state change. A clean restart has three markers: interruption resolved, original module named, and fresh input acknowledged. Missing any marker leaves roles at different points. Classify the issue afterward as observation, lookup, relay, positioning, execution, or interruption recovery.

No trustworthy complete public mapping was found, so the in-game manual remains the authority for the final answer. The cited structured and community sources supporting the callout order were checked September 3, 2026. A BOMBANANA table is a lookup aid, not a replacement for reading the panel. Use numbered positions during the first scan, because a later color, symbol, or direction is only useful when the team can attach it to one control. Select a row only after every input is attached to the current stage.

If BOMBANANA changes Slider, compare live behavior with the source date before blaming the player. Record the exact inputs, result, and stage, then seek an official announcement or reproducible community correction. One failed attempt is not enough to patch a table because execution errors and expired state can imitate a rule change. End practice with one deliberate failure and recovery. A group that only rehearses perfect packets has no shared language for the first real disruption.

Practice the phrases “slider warning,” “hands off,” and “slider stable, repeat last field.” The main caller pauses at a field boundary. Keep the exercise outside a serious Campaign attempt until every role can finish without inventing vocabulary. Then add a timer and one deliberate interruption. Rehearse the full BOMBANANA recovery: hands off, identify the break, declare stability, restart at “Slider,” and collect current fields. Use “hands off” as a state-control command, not criticism. Neutral language makes it easier to stop a nearly completed action when the evidence changes.

Measure packet accuracy before raw speed. Count missing fields, ambiguous positions, premature actions, and failed confirmations; only shorten pauses after the packet is reliable. Rotate BOMBANANA roles so everyone experiences observation, manual search, relay translation, and physical execution. Rotate roles after a clean attempt. Experiencing each information limit helps players request only what the next person can actually observe or communicate. Shared understanding is more useful than one player memorizing a table.

Before touching the BOMBANANA Slider panel, name the module, identify the stage, collect Slider height, and convert the manual result into a physical instruction. Repeat the whole action and wait for confirmation; after one input, report whether the panel cleared, changed, or expects another stage. A role that notices missing context should stop the chain immediately. Repairing one field preserves the packet; guessing forces the team to rebuild after a strike.

If Chaos interrupts Slider, stop its callout and clear the emergency first. Treat the packet as expired until every role confirms otherwise; reread the panel, reopen the correct branch, and send a fresh physical instruction. A clean restart has three markers: interruption resolved, original module named, and fresh input acknowledged. Missing any marker leaves roles at different points. Labeled repetition is safer than combining correct fragments from different BOMBANANA moments.

• Say “Slider” before reporting any values.
• Collect Slider height in a fixed order.
• Keep the live observation separate from the manual interpretation.
• Translate the answer into Blind’s physical viewpoint and confirm once.
• After a state change or Chaos event, discard the old packet and reread.