Nodes/noEmbryo nodes/PromptTermList 2 /noEmbryo
ComfyUI Node

PromptTermList 2 /noEmbryo

A second, independent dropdown for your prompt terms

By noembryo·Created 3 years ago·Updated 3 days ago· 33
PromptTermList 2 /noEmbryo
    • Term
    terms
    text
    strength1.00
    store_inputfalse

    PromptTermList 2 is the second of six near-identical nodes in the noEmbryo pack, and the difference matters more than it looks: each one owns a separate term library. PromptTermList 1 reads TermList1.json, this one reads TermList2.json, and the two never touch each other's data. That's the whole point of having six of them - the author deliberately built them so you could dedicate each to a different category without one node's dropdown polluting another's.

    So if PromptTermList 1 is your photography terms, make this one your lighting library. Or your camera list. Or your negative-prompt fragments. Same workflow, different JSON file.

    How it works

    The terms dropdown lists the labels from TermLists/TermList2.json in the pack folder, and the Term output spits out the matching value string when the graph runs. The None label is always available for "no stored term." The file starts out with just None, so this node begins effectively empty - you fill it with your own labels.

    To add a term, wire a text box into text with the label= / value= format, flip store_input on, run once, and refresh the page. The strength input applies ComfyUI's parenthesis weighting ((term:1.3)) when you want a term to hit harder. Or skip the node entirely and edit TermList2.json by hand - careful with the commas, because a broken JSON file means the dropdown won't parse.

    Install

    ComfyUI Manager → search "noEmbryo", or:

    cd ComfyUI/custom_nodes
    git clone https://github.com/noembryo/ComfyUI-noEmbryo.git
    

    Restart, and all six PromptTermList nodes (plus the rest of the pack) appear. No dependencies, no models, and the six JSON files are created automatically on first launch.

    A word of caution

    Like all six of these, the author labels PromptTermList obsolete in favor of the pack's Json Prompt Loader, which keeps the prompt library in one file you point it at instead of six hardcoded ones. That said, if you want a dedicated, dead-simple dropdown per category and don't mind the maintenance, PromptTermList 2 works fine today. It's stable, zero-cost, and does exactly one thing.

    CategorynoEmbryo/Term Nodes

    Inputs (4)

    NameTypeDefaultDescription
    termsCOMBOChoose a term from the TermList with the corresponding number
    textoptSTRINGInput text to store in the TermList Use the format: label=... ... value=.... .... ...
    strengthoptFLOAT1.000.05–2Controls how much the image is allowed to change. 0.0 = almost no change 1.0 = maximum creativity
    store_inputoptBOOLEANfalseStore the input text in the TermList Use the format: label=... ... value=.... .... ...

    Outputs (1)

    NameTypeDescription
    TermSTRING