ClownOptions Extra Options

Every big configurable node eventually grows more settings than it has room for widgets, and RES4LYF's answer is an escape hatch: a free-text box where you type flags the sampler understands but doesn't surface as knobs. ClownOptions Extra Options is that box. It's the "advanced settings" drawer for the ClownsharK sampler, and it's where a lot of the pack's experimental behavior actually lives.

The README shows the canonical example: to reproduce an older workflow you'd type truncate_conditioning=true into the extra_options box. That's the shape of the whole thing - key=value lines that toggle or tune behavior the developers haven't (or won't) promote to a proper widget.

How it works

It emits an OPTIONS object, exactly like the other option nodes, that plugs into the sampler's options input. Whatever you typed gets parsed and applied at sample time. It also accepts an incoming OPTIONS, so you can chain it after a SharkOptions or another options node - this one adds the raw flags on top of whatever settings came before.

The inputs and outputs that matter

There's really just one:

• extra_options (STRING, multiline) - your flags, typically one key=value per line. Empty is the default and perfectly valid; an empty box changes nothing.
• options (OPTIONS, optional) - the incoming options to layer onto, if you're chaining.

Output is options (OPTIONS) → the sampler, or the next options node in the chain.

The honest catch: the set of valid flags isn't a friendly dropdown. It lives in the pack's code and its example workflows. You mostly discover them by copying a workflow that uses one, or by reading what the author posts.

How to install 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: use the embedded pip. Restart, hard-refresh with F5. No downloads. Grab rgthree-comfy too for the nested menus.

Common issues & troubleshooting

A flag did nothing. Most likely a typo, a wrong key, or a value in the wrong format. These strings are parsed literally - truncate_conditioning=true works, truncate conditioning = True might not. Match the exact spelling from the source you copied it from, one flag per line.

Where do I find valid flags? There's no built-in list. The README documents a couple (like truncate_conditioning=true), and the rest surface in the pack's example workflows and the author's posts. If you didn't get a flag from somewhere concrete, it probably isn't real - don't guess key names.

It's genuinely optional. You do not need this node to run RES4LYF samplers. It exists for the long tail of experimental settings. If you're just here to swap in a res_2m sampler with beta57, skip it entirely.

Order matters when chaining. Extra options layer onto whatever OPTIONS you feed in. If an extra_options flag overlaps with a setting from an upstream option node, the chain position decides who wins - keep this node where you intend its flags to take effect.