👾 Mega Slider X12

Let's be honest: twelve sliders is a lot, and most workflows will never need them. But the day you do - a big batch sweep, a parameter-mapping experiment, or a single workflow that's accumulated a dozen tunable values - you'll be glad this exists instead of a twelve-node tower. 👾 Mega Slider X12 is the top of the Mega Slider line: twelve universal sliders, twelve float outputs, one optional master range, same engine as the X1/X3/X6 siblings.

What's on the node

Twelve required float sliders, slider_1 through slider_12, each −10000 to 10000 at 0.01 step by default. One output_int toggle (all-or-nothing, casts every value to int when on). One optional master input that drives a single min/max/step across all twelve.

Outputs: value_1 through value_12, all FLOAT, each wiring independently into any node that accepts a float.

How the mechanism works

Exactly like the rest of the family. With a MEGA_SLIDER_MASTER connected, each slider clamps into the master range and snaps to step - round(value / step) * step; without one, raw values pass through at the default range. The pack's JS rescales all twelve live when the master changes, and per-slider overrides exist in right-click → Properties as slider_N_min / slider_N_max / slider_N_step, because no real workflow has twelve values that all genuinely share one range. Plan to use those.

Where twelve actually earns its keep

Two realistic use cases. First, batch diversity: a set of correlated values you sweep together across runs, where keeping every slider on one master range is the whole point - change one number and the whole sweep rescales. Second, big editable pipelines: you've got LoRA strengths, CFG, denoise, steps, sampler settings, blend weights… twelve floats that used to live in a dozen places, now on one surface. For anything less, the X3 or X6 is the saner pick - twelve dials is a commitment, and a graph where you need to find a specific slider gets more painful the more you have.

Installing it

Ships in the MachinePainting Nodes pack. ComfyUI Manager → search "MachinePaintingNodes", or:

cd ComfyUI/custom_nodes
git clone https://github.com/machinepainting/ComfyUI-MachinePaintingNodes.git

Restart ComfyUI. The pack's deps (opencv-python-headless, numpy<3, rembg) are irrelevant here - this node does nothing but pass numbers around.

Gotchas

• Step snapping is silent and bank-wide. With a master at step 0.1, every slider that isn't on a step multiple gets quantized the moment it re-renders. Check the master step before you start dragging.
• No master = ±10000 dead range. Twelve sliders over that range is unusable; attach a master or lean on property overrides before real work.
• output_int is all-or-nothing, so mixed int/float needs mean separate X1 nodes.

It's overkill for most graphs and exactly right for a few. If you're not sure you need twelve, you don't - but when you do, it's nice that the option is one node away instead of a twelve-node rebuild.