MODULE / CHAOS / 13
Keep lowering the rising Chaos control until the bomb is defused. Slider is not the color-based up/down puzzle called Color Slider.
By BOMBANANA! Wiki · Updated September 7, 2026 · Full-release guide
Need the colored up/down puzzle? Open the Color Slider guide. This page covers the continuously rising Chaos control.
PROCEDURE
Suggested role split: Deaf watches the slider and warns Blind before it becomes urgent.
Pause the defusal instruction and guide Blind to the Slider control.
Blind pulls down; Deaf checks the visible height and calls the return to the interrupted panel.
Recheck that panel’s stage and last completed action before any new input. Keep monitoring Slider until the bomb is defused.
The v1.0.0 reference lists these 16 fixed placements. Random slots and custom settings are not included.
BOMBANANA! PLAYER GUIDE
Identify the right slider, divide observation from physical control, and restart the interrupted module without repeating a completed action. Team routines below are suggestions, not official required methods.
Identify the panel before opening a rule. Both names occur in the early Campaign, including together in Level 4, but they ask the team to do different jobs.
| Module | Task | When the task ends |
|---|---|---|
| Slider (Chaos) | Keep pulling down the control as it rises. | When the bomb is defused; one pull does not complete the module. |
| Color Slider (defusal) | Set sliders up or down using their colors and the manual. | When the panel is solved. |
Suggested role split: Deaf watches the rising control and calls its location when intervention is needed. Blind performs the pull-down action. Mute stays with the interrupted manual task and can signal a correction. A “Slider owner” is a coordination responsibility, not a fourth role or permission for everyone to touch the bomb.
Deaf cannot hear a spoken “done.” Deaf should check the visible control and announce when the team can return to the defusal panel. Keep monitoring afterward; “lowered” is a temporary observation, not a permanent solved state.
Suppose Calculator’s original result has been entered and Deaf is about to call the new LED. A Slider warning arrives before the final key is chosen. Suggested call: “Slider — pause Calculator.” Deaf guides Blind to Slider, observes the lowered control, then says “Calculator — check stage two.” Mute retains the original-result context while the action is paused.
Before resuming, identify what was actually entered. If the final key was already pressed, check the outcome before repeating it. If it was not, combine the retained original parity with the current LED and locate the required key. If the team cannot establish the stage or saved result, do not turn a half-remembered number into an instruction.
The cited reference describes continuous rise and repeated pull-downs. It does not establish a universal safe percentage, rise speed, or maximum unattended interval. Choose an early, recognizable warning point using your current game’s feedback; do not wait for a guessed number from this page.
Review two different mistakes after a run: noticing the control too late, and resuming the wrong action after handling it. An earlier warning can help the first. Naming the interrupted module and stage addresses the second. Repeating the pull-down instruction more loudly does not identify which failure happened.
Start with Level 4: Slider accompanies Color Slider and Direction. Level 5 adds a useful exercise in preserving Calculator’s two-stage state. Level 12 introduces a different coordination test because Slider and Pressure are both present. The fixed-appearances list above links all 16 levels; these placements are versioned reference data, not a claim about every custom setup.
A simple rehearsal is to interrupt one mock callout before an action, and another immediately after it. The team should produce different restarts: one authorizes the still-pending input; the other checks its outcome. This is a suggested communication drill, not evidence of a measured in-game success rate.
