Save 4 hours! We auto-setup your workflow! Free!

Drop your workflow.json — we handle every dependency, custom node, and model. Just open the link and run.

Auto-Setup Workflow Json (Free) Now!
ComfyUI > Nodes > FunUI > FunUI Modifier Settings

ComfyUI Node: FunUI Modifier Settings

Class Name

FunUIModifierSettings

Category
FunUI/Sampling
Author
digital-garbage (Account age: 1276days)
Extension
FunUI
Latest Updated
2026-11-03
Github Stars
0.02K

How to Install FunUI

Install this extension via the ComfyUI Manager by searching for FunUI
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter FunUI in the search bar
After installation, click the Restart button to restart ComfyUI. Then, manually refresh your browser to clear the cache and access the updated list of nodes.

Visit ComfyUI Online for ready-to-use ComfyUI environment

  • Free trial available
  • 16GB VRAM to 80GB VRAM GPU machines
  • 400+ preloaded models/nodes
  • Freedom to upload custom models/nodes
  • 200+ ready-to-run workflows
  • 100% private workspace with up to 200GB storage
  • Dedicated Support

Run ComfyUI Online

FunUI Modifier Settings Description

Combines and validates FunUI modifier settings into a structured configuration for sampling.

FunUI Modifier Settings:

FunUIModifierSettings, displayed as “FunUI Modifier Settings” in the FunUI/Sampling category, prepares your chosen FunUI modifier settings for use in a generation workflow. It brings settings for different modules together into one structured collection, rather than requiring separate controls and connections for every available option. This helps keep saved workflows stable as modules gain new settings. The node checks your configuration against the definitions supplied by installed modules and normally catches invalid settings before the workflow starts executing, helping you avoid loading a checkpoint only to discover a configuration problem afterward. It also handles settings left behind by removed or unavailable modules by warning you and ignoring those entries. This node prepares and checks configuration; it does not modify your model or generate images itself. In the standard FunUI pipeline, other nodes use its prepared settings to apply modifiers and guide sampling.

FunUI Modifier Settings Input Parameters:

settings

A required STRING input presented as a multiline text field, with a default value of "`{}`". Enter a JSON object that groups settings by module ID, following the structure {"module_id": `{"setting": value}`}; the module IDs, setting names, and acceptable values must come from the modules installed in your FunUI environment. FunUI can write this configuration for you, but you can also edit it manually. Empty or whitespace-only text is treated as {}, meaning that you have not explicitly supplied any settings here. The node parses this text, checks recognized modules against their setting definitions, and prepares the accepted configuration for downstream nodes. Entries belonging to modules marked as off or quarantined are skipped without checking their values, while entries for unavailable modules are ignored with a warning during execution. Special reserved control entries are handled separately from ordinary module settings. Normally, configuration problems prevent the workflow from being accepted into the queue; if an installed capability enables full control, setting-validation problems can instead be allowed with warnings during execution. Full control does not make malformed JSON or a non-object JSON value acceptable at execution. Minimum and maximum values are not applicable to this text input, and no fixed option list is defined; restrictions on individual setting values depend on each module’s schema.

FunUI Modifier Settings Output Parameters:

settings

A FUNUI_SETTINGS output containing the checked settings as a dictionary-like object, rather than the original JSON text. Its entries represent recognized module settings after module-specific checking, along with accepted reserved control entries. Unknown module IDs and entries skipped because their modules are off or quarantined are not included. With full control enabled, module checking is instructed to retain invalid values rather than enforce the normal safeguards, so this output should not automatically be interpreted as safe in that mode. Connect it to the settings input of FunUILoadModifiers to supply the configuration used when modifiers are applied to a model; the standard pipeline also connects it to the settings input of FunUISampler. The output is a configuration payload, not an image, model, or confirmation that modifiers have already been applied. FunUILoadModifiers performs its own validation when consuming settings.

status

A STRING output summarizing which entries remain in the prepared settings. Its format is settings for followed by the retained entry names in alphabetical order, separated by commas. If no entries remain, the exact result is settings for nothing set. This gives you a quick way to check whether configuration entries survived processing, particularly when older settings reference modules that are no longer installed. Accepted reserved control entries can also appear in this summary, so it is not exclusively a list of modifiers. The message does not list individual setting values, confirm model compatibility, or prove that any modifier was applied successfully; warnings and validation failures are reported separately.

FunUI Modifier Settings Usage Tips:

  • Start with {} when you do not need to supply custom module settings. This keeps the configuration minimal and lets downstream nodes and module definitions determine their applicable behavior without unnecessary overrides.
  • Prefer settings generated by the FunUI application when possible. If you edit the JSON manually, use exact installed module IDs and documented setting names; the outer keys identify modules, not their display labels.
  • Keep your JSON syntax strict: use double quotes around keys and text values, use lowercase true and false for JSON booleans, and avoid comments or trailing commas. These small formatting checks prevent failures before generation begins.
  • Connect the first output to FunUILoadModifiers, and connect that node’s model output to your sampler. Follow the standard pipeline by also passing the prepared settings to FunUISampler when using its settings connection. Merely placing FunUIModifierSettings in the graph does not apply a modifier.
  • Use the status output to check which entries were retained, but inspect warnings as well. A missing module can be ignored without stopping generation, so a completed run does not necessarily mean every saved modifier setting was used.
  • Leave safeguards enabled for routine work, especially when paying for GPU time. Queue-time checks can catch invalid configuration before checkpoint loading; full control deliberately relaxes those checks and can allow settings that cause a later failure.
  • When reopening an older workflow, review warnings about unavailable module IDs. Restore the intended module or remove obsolete configuration entries rather than assuming that saved settings are still active.
  • If a module is off or quarantined, do not assume its saved values have been validated: this node skips those entries. Review the settings when you enable the module again.

FunUI Modifier Settings Common Errors and Solutions:

FunUI Modifier Settings: this is not valid JSON -- ...

  • Explanation: The text cannot be parsed as JSON. The final part of the message describes the parsing problem, such as a missing quotation mark, an extra comma, or an unfinished object. This can be caught during queue validation or raised during execution.
  • Solution: Check that keys and text values use double quotes, that brackets and braces are balanced, and that there are no comments or trailing commas. If you need to isolate the issue, temporarily replace the text with {}, then restore your settings a small section at a time.

FunUI Modifier Settings: expected an object keyed by module id, got ...

  • Explanation: The text is valid JSON, but its outermost value is not an object. For example, [] produces a list, null produces NoneType, and a quoted sentence produces a string. The node requires an object so that each entry can be associated with a module ID.
  • Solution: Use {} for an empty configuration, or place your actual module settings inside an object keyed by the appropriate module IDs. Do not wrap the entire JSON object in quotation marks.

FunUI Modifier Settings: followed by module-specific validation problems

  • Explanation: A recognized module’s settings do not pass its schema checks, or a reserved control entry fails its dedicated check. The exact details depend on the installed module and its definitions; this node does not define a universal list of setting names, types, or numeric limits. Multiple problems can appear in one queue-validation message, separated by semicolons.
  • Solution: Read each reported detail and compare the affected setting with the module’s documented options. Correct the value, restore a known working configuration, or remove an unnecessary override. Keep safeguards enabled while troubleshooting so the workflow stops before expensive processing begins.

saved settings for 'module_id' ignored: no module with that id is loaded

  • Explanation: This is a warning, not a fatal error. The configuration refers to a module that is absent from the current registry, possibly because it was removed, renamed, or failed to load. The node omits that entry and continues; it does not apply the saved settings for that module.
  • Solution: If you still need the module, confirm that it is installed and loading successfully, then check its current ID. Otherwise, remove the obsolete entry. The warning is logged once for the corresponding module warning key, so it may not appear repeatedly.

Invalid settings are accepted into the queue but warnings appear during execution

  • Explanation: This can happen when an installed capability reports that full control is enabled. Queue validation then allows reported setting problems, and execution uses the warning-oriented path instead of normal refusal. Invalid values may be retained, and a later modifier failure can end the run. Malformed JSON and a non-object outer value still fail during execution.
  • Solution: Disable full control through the relevant installed module’s controls and correct the reported settings before running again. Do not rely on full control to repair a configuration; it relaxes protection rather than correcting mistakes.

FunUI Modifier Settings Related Nodes

Go back to the extension to check out more related nodes.
FunUI
RunComfy
Copyright 2025 RunComfy. All Rights Reserved.

RunComfy is the premier ComfyUI platform, offering ComfyUI online environment and services, along with ComfyUI workflows featuring stunning visuals. RunComfy also provides AI Models, enabling artists to harness the latest AI tools to create incredible art.