Sigmas Unpad

This node does exactly one thing: it removes an entry from the end of a sigma schedule. It's the companion to Sigmas Pad, and on its own it needs no explanation beyond that - no extra parameters, no options, just "take this schedule, strip the trailing value, hand it back."

The reason it exists as its own node rather than folded into Pad is workflow shape. You often add a padding value as scaffolding - a placeholder final entry that lets some other node (Sigmas Math3's step-range logic, for instance, or a multi-stage chain built with Sigmas Truncate) behave correctly - without wanting that extra value to actually reach a sampler. Unpad is how you clean it back off before the schedule leaves your hands.

The inputs and outputs that matter

One input, sigmas - the padded schedule. One output, SIGMAS - the same schedule with its last entry removed. That's the entire surface area of the node: no threshold, no target value to match, nothing to configure. It doesn't check whether the entry it's removing looks like padding versus a "real" schedule value - it just drops the last one, unconditionally, every time.

That single-purpose design is deliberate rather than a missing feature. Pairing a bare "add one" node with a bare "remove one" node keeps both halves trivially predictable - you always know exactly what each one did to your schedule's length, which matters when you're stacking several Sigmas- nodes in sequence and need to reason about step counts without opening each node's internals.

Installing it

ComfyUI Manager: search RES4LYF, install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/ClownsharkBatwing/RES4LYF/
cd RES4LYF
pip install -r requirements.txt

Portable ComfyUI users should use the embedded pip.exe in place of plain pip. Restart and hard-refresh afterward.

Where people get tripped up

The main thing to watch is pairing: Unpad removes whatever's currently last, regardless of whether it's actually the value Pad added. If your schedule picked up an extra entry from somewhere else in the graph - another Sigmas- node, a manual edit - Unpad will happily strip that instead, and you'll end up one step short of what you meant to keep. Trace where the padding actually came from before dropping this node in, especially in a longer chain with several sigma nodes stacked together.