Mpi Multi Text x4

Four is where the "combine text" family stops being cute and starts being structural. If your prompt has a quality block, a subject, a style, and a negative-ish qualifier that all change independently, Mpi Multi Text x4 gives you four multiline boxes that join into one string - so you can flip one piece without rebuilding the whole prompt. It's the ComfyUi-MpiNodes version of a "\n".join() you never have to type.

How it works

Four required inputs - text_1 through text_4 - each a multiline STRING box, joined in order with single spaces into one text output. That's the whole mechanism, and it's the same space-join as the x2/x3/x5 siblings in the pack's Conditioning category.

The space-join detail is the one thing to remember: you provide your own separators. End a box with a comma if you're building comma-separated tags; leave it bare if you're writing natural sentences. The node won't add punctuation, and it won't reorder - text_1 always comes first.

The inputs that matter

• text_1 … text_4 - the four pieces, all required and multiline.
• text (output) - the joined STRING, ready for a CLIP Text Encode or to feed another assembly step.

That's genuinely all there is. This is a value-plumbing node, not a smart one - which is exactly the point. The KB's plumbing essay calls this part of ComfyUI "70% plumbing," and nodes like this are why: they're unglamorous and they carry the graph.

Installing it

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

Restart, or use ComfyUI Manager and search ComfyUi-MpiNodes. No dependencies, no models to download. The pack is AGPL-3.0 at current versions (MIT through 1.2.6).

The honest take

You won't use this every day, and that's fine. But the moment you're doing variation batches - same subject, four style options, keeping the quality block constant - having the shared pieces in separate boxes means changing the style touches one box, not the whole string. If you need more than four chunks, the x5 exists; if you're past five, you're probably building with the pack's real prompt-list system (MpiPromptList + MpiPromptProcessor) instead of hand-assembling strings, which is the right call at that scale.