Nodes/FunUI/FunUI Modifier Settings
ComfyUI Node

FunUI Modifier Settings

One JSON box that stands in for forty widgets

By digital-garbage·Created about a year ago·Updated a day ago· 21
FunUI Modifier Settings
    • settings
    • status
    ◄settings{}►

    Here's a genuinely odd-looking node: it has exactly one input, a multiline text box containing JSON, and it exists because FunUI has a couple of dozen "modifiers" - small per-step things that nudge sampling - and if each one had its own socket on a node, that node's shape would change every time any module gained an option, and every saved workflow would refer to sockets that had moved.

    So instead: one payload. FunUIModifierSettings carries the values you picked as {"module_id": {"setting": value}}, and a companion node, FunUI Load Modifiers, reads them and installs whatever the model in front of it can actually use.

    What it does, mechanically

    Honestly, not much - and that's the design. It parses the JSON, checks every module id and every value against the schema that module announced, and passes the cleaned dict out on a FUNUI_SETTINGS socket. The interesting part is when it checks.

    Validation runs at queue time, not when the node executes. That matters on a rented GPU: without it, a typo'd module id would be discovered only after the checkpoint had been loaded and the time paid for. ComfyUI's own validator sees this input as an opaque string, so the pack's validate_inputs hook is the only place it can be understood before the queue accepts the run.

    Three behaviours fall out of that, and they're all reasonable:

    • Unknown module ids are skipped, out loud. Saved settings outlive modules - removed, renamed, or one that failed to load today. Refusing the run would break every project that ever touched that module, so you get a log line: saved settings for 'x' ignored: no module with that id is loaded.
    • Bad values are refused before the run. Not cosmetically - a NaN reaching a modifier is how you get a modifier that silently does nothing while reporting that it was applied, and the source calls that out specifically.
    • "Full control" turns the guards off. That module is in the same payload it's checking, and when it's on, a bad value is accepted and warned about at execution instead of blocking the queue. The log then says, more or less, that the consequences are yours.

    Outputs are the settings payload and a status string naming what was set.

    How you use it

    You mostly don't type in it. The FunUI app writes this payload for you - every module announces its own settings, so the Engine screen is always complete, and the app bungs the result into this node. Editing by hand is explicitly supported by the author, and mistakes are reported rather than silently swallowed.

    The wiring is the standard value-node pattern: one source, many consumers.

    FunUI Modifier Settings ──settings──> FunUI Load Modifiers ──model──> sampler
                              └─settings──> FunUI Sampler (optional settings input)
    

    FUNUI_SETTINGS is a custom socket type, which is worth knowing because it has a consequence: a raw API prompt can hand that socket a dict that never passed through this node. Load Modifiers therefore re-validates everything it receives. If you're writing prompts by hand against the API, that's where the real gate is.

    Why this shape is a defensible choice

    The KB's plumbing doc makes the general case: value nodes exist to fight repetition and illegibility, and the alternative to a payload is a node whose socket list grows forever. FunUI picked the payload because its node set is generated by whichever modules are switched on - a socket-per-setting design would be unstable by construction.

    The cost is real, though. There is no autocomplete and no dropdown here. If you do this by hand you're guessing at module ids, and the failure mode is a log line you might not read. The app's Settings screens are the supported interface; this node is the carrier.

    Installing it

    cd ComfyUI/custom_nodes
    git clone https://github.com/digital-garbage/FunUI
    pip install -r requirements.txt
    

    Or FunUI from ComfyUI-Manager, or comfy node install FunUI. Restart. Then check that the node exists at all - FunUI's features are modules, and a module that's switched off in Settings ▸ Modules (or that failed to load) takes its nodes with it while the rest of the run carries on. A missing FunUI Load Modifiers is the more common complaint than anything about this node, and it's almost always a module switch.

    Where people get burned

    Malformed JSON. You get this is not valid JSON -- … with the parser's own complaint. Trailing commas are the usual culprit; the payload is strict JSON, not JSON5.

    Editing a value to something out of range and being confused that the queue refuses. That's the point - it refused before loading a 33B model. Loosen it with Full control if you truly know better, but don't file a bug about the guard.

    CategoryFunUI/Sampling

    Inputs (1)

    NameTypeDefaultDescription
    settingsSTRING{}{"module_id": {"setting": value}}. The app writes this; editing it by hand is fine, and mistakes are reported.

    Outputs (2)

    NameTypeDescription
    settingsFUNUI_SETTINGS—
    statusSTRING—