❌ Set Float [Deprecated]

❌ Set Float [Deprecated] is a relic from the early days of the genparams design, back when the pack's answer to "I want to tweak a parameter" was a generic node: give it a genparams, a key string, and a float value, and it would stamp that key into the blob. It still exists so old workflows load, but the pack grew past the need for generic key-stamping nodes - the modern setters are purpose-built for each setting.

What it did

Three inputs: genparams (the blob to update), key (the full dotted path of the parameter to modify - the default was base.cfg, and the tooltip insists the key must include its prefix), and value (a float, default 8, step 0.1). Output was the updated genparams, chainable. So you could theoretically set anything, as long as you knew the exact key name. Which was the problem: it pushed all the knowledge onto you, and one typo in base.cfg vs denoising.base.cfg silently did nothing.

Why it's deprecated

The pack's philosophy evolved from "generic knob with a key string" to "one node per meaningful setting, with a real widget." Today, tweaking CFG means 💪TB | Set Image Details's cfg_shift (which adjusts relative to the style's recommendation, with its own signed range and tooltip), tweaking detail means detail_level, and so on. Those nodes know their own keys, validate their ranges, and integrate with the style system - the old generic node knew none of that. It also predates the rename of the key namespace: the modern genparams uses denoising.base.* prefixes, so a base.cfg key from an old graph may not even map onto anything current.

If you're stuck with one

Check what key it's setting. If it's base.cfg, the honest modern replacement is Set Image Details → cfg_shift (or Select Style, since styles carry CFG defaults). If it's some exotic key that has no dedicated node, you're using a feature that no longer has first-class support - and you're probably better off adjusting the actual setting through the intended node than hunting for a key name the new architecture doesn't recognize. Old workflows that still reference Set Float will load fine thanks to the deprecated shim, but they're running on a version of the genparams schema that's been superseded.

Install

Ships with the pack - ComfyUI Manager search "tinybreaker", or git clone https://github.com/martin-rizzo/ComfyUI-TinyBreaker into custom_nodes, restart. It's hidden from the default menu (deprecated category), so you'll only meet it in old graphs. When you do, replace it with the named setter that matches what it was trying to do. The pack's bet is that you never need a raw "set key X to Y" node, and by and large it's won that bet.