Nodes/mc_cascade_res/MC Prompt Text Dynamic
ComfyUI Node

MC Prompt Text Dynamic

A prompt box that actually knows about wildcards

By tester4488·Created 10 months ago·Updated 9 months ago· 0
MC Prompt Text Dynamic
    • prompt
    prompt

    This one looks pointless for about ten seconds, until you notice the word that matters in its name: dynamic. MC Prompt Text Dynamic is a multiline text node that passes your prompt through untouched - the pass-through part is boring - but its input is registered with dynamic prompts enabled, which is ComfyUI's way of saying "this field expands wildcards when you run."

    ComfyUI's dynamic prompt system is the {option one|option two} alternate syntax plus __wildcard__ folder lookups: type a {cat|dog} in the rain and each queue run picks one, or drop a __style__ token that pulls from a wildcard file. It's how people build workflows that never generate the same image twice. The catch has always been that whether expansion actually fires depends on the input being marked for it - and that's the one thing this node guarantees.

    How it works

    prompt (string, multiline, default empty) goes in, prompt (string) comes out. The node's execute is literally return io.NodeOutput(prompt) - there is no processing, no API call, nothing clever. All the behavior lives in the schema flag that marks the input as dynamic-prompt-capable, so the frontend expands wildcards when you queue. It's a primitive string node with the right flag already set.

    Wire it into a CLIP Text Encode the usual way: right-click the prompt input on the encoder and convert it to a socket, then drop this node's output on it. Same dance as any value node, covered in ComfyUI's plumbing docs.

    Why you'd reach for it

    The honest take: this is a convenience, not a superpower. Core ComfyUI's PrimitiveStringMultiline can pass a prompt through too. The value here is that the dynamic-prompts flag is already set, so you don't have to remember which text nodes expand wildcards and which silently don't. If you've ever stared at a prompt full of {alternates} that came out verbatim, you know exactly why a node whose only job is "this input expands wildcards" is worth having on the canvas.

    If you never use wildcards, though, this node is redundant - grab the core primitive and move on. It earns its slot precisely for people who build prompt-variation workflows and got tired of the expansion not triggering.

    One gotcha

    Because dynamic prompt expansion treats {a|b} as "pick one," you can't use curly braces for anything else in that prompt. A prompt that literally wants to say "a {lion} in the savanna" will treat it as a one-option wildcard group. That's the price of the feature itself, not a bug in this node - but it's the thing that will confuse you once, so now you know.

    Install

    Part of the mc_cascade_res pack, under MC nodi/Text. Install once for the whole pack: ComfyUI Manager → search mc_cascade_res, or:

    cd ComfyUI/custom_nodes
    git clone https://github.com/tester4488/mc_cascade_res
    

    Restart after cloning. No model downloads, no Python dependencies. Like the rest of the pack it's written against ComfyUI's newer V3 extension API, so a stale ComfyUI will refuse to load it - update if the node doesn't appear.

    It's a small node from a small one-person pack, and the author's framing - a labeled text source with dynamic prompts on by default - is genuinely the right call for anyone who lives in prompt-variation land. Just don't ask it to hold a literal { in your prompt.

    CategoryMC nodi/Text

    Inputs (1)

    NameTypeDefaultDescription
    promptSTRING

    Outputs (1)

    NameTypeDescription
    promptSTRING