EmberFrame Wildcard Config Combiner

EmberFrame Wildcard Config Combiner is the least glamorous node in the pack, and it's here so the pipeline stays clean. It takes up to six rule lines - the token | file | mode | start_line | repeat_each_line strings that EmberFrame Wildcard Rule Builder produces - and joins the non-blank ones into a single multi-line config string for the EmberFrame Wildcard Prompt Assembler.

You could skip it and type the config directly into the Assembler's wildcard_config box. You absolutely could. But once you have more than two or three tokens in a prompt, the combiner is what lets you build the config visually instead of maintaining a wall of hand-typed text that's one stray pipe away from a parse error.

How it works

Nothing clever happens here, and that's the point. combine_rules takes rule_1 through rule_6, strips whitespace, drops anything blank, and joins the survivors with newlines. Blank inputs are the way you leave slots unused - wire up three Rule Builders and leave the rest empty, and you get a clean three-line config.

The rule_count output tells you how many rules actually made it through. It's a genuine sanity check: if you think you wired five rules and it says 2, a blank slot is eating your rules.

Inputs and outputs

• rule_1 … rule_6 - six STRING inputs. Wire Rule Builder rule_line outputs into them.
• wildcard_config (output) - the joined multi-line config, feed it to the Prompt Assembler's wildcard_config input.
• rule_count (output) - the number of non-empty rules, as an INT.

Installing it

With the rest of the EmberFrame Nodes pack:

cd ComfyUI/custom_nodes
git clone https://github.com/emberframe/emberframe-nodes.git

Restart Comfy, or install "EmberFrame Nodes" from ComfyUI Manager. No dependencies, no model files, and it shows up under EmberFrame/Prompt.

A note on scope

This node deliberately doesn't parse or validate the rule lines - validation happens later, in the Assembler, which is the only node that actually reads the config and resolves tokens. So if a rule is malformed, the combiner will happily pass it through and the Assembler will be the one that throws. For a quick setup, wiring one Rule Builder straight into the Assembler skips this node entirely; the combiner earns its keep when you're juggling several tokens at once.