Nodes/ComfyUi-MpiNodes/Mpi Multi Text x3
ComfyUI Node

Mpi Multi Text x3

Join three prompt pieces without the string gymnastics

By MadPonyInteractive·Created 11 months ago·Updated 5 days ago· 3
Mpi Multi Text x3
    • text
    text_1
    text_2
    text_3

    Three boxes beat two when your prompt naturally splits into three parts - say, a fixed quality string, a changing subject, and a style suffix you want to swap between experiments. Mpi Multi Text x3 takes three multiline text inputs and joins them into one string with spaces, so each piece stays its own editable box instead of one giant blob you retype or slice apart.

    It's part of ComfyUi-MpiNodes, Mad Pony Interactive's utility pack, and it sits in the same Conditioning family as the x2, x4, and x5 MultiText nodes. The pack uses this pattern internally - its prompt-generation nodes hand you assembled strings, and the MultiText family is how you split the assembly job back into editable chunks.

    How it works

    Nothing magical here: text_1, text_2, and text_3 (all multiline STRING inputs) get joined with single spaces and come out one text string. The mechanism is literally a space-join, which means two things for how you use it.

    First, punctuation is on you - a space only, no commas. If your pieces are comma-separated tags, end each box with its own comma. Second, order is fixed: output is always text_1 then text_2 then text_3, in that order. If you want to swap which piece comes first, swap which box holds what - there's no reordering control.

    What you actually set

    • text_1, text_2, text_3 - the three pieces. All required, all multiline.
    • text (output) - the joined STRING, straight into a CLIP Text Encode or on into a bigger assembled prompt.

    Installing it

    cd ComfyUI/custom_nodes
    git clone https://github.com/MadPonyInteractive/ComfyUi-MpiNodes
    

    Restart ComfyUI. Or grab it via ComfyUI Manager by searching ComfyUi-MpiNodes. No pip requirements or model files - this family is pure Python. Licensing note in case you're building something distributable: AGPL-3.0 from v1.2.7 on, MIT before that.

    When to pick this one over the others

    If you keep exactly three logical chunks separate - "quality block" / "subject" / "style" is the obvious one - this is your node. Two chunks, use x2; four or five, use those. The real lesson from the family: pick the box count that matches your prompt structure instead of stacking joins, because a chain of three x2 nodes is just x3 with extra steps and more places to get the order wrong.

    CategoryMpiNodes/Conditioning

    Inputs (3)

    NameTypeDefaultDescription
    text_1STRING
    text_2STRING
    text_3STRING

    Outputs (1)

    NameTypeDescription
    textSTRING