Multiline String

A text box that outputs its contents as a string. Yes, that's it. The class name (YANC.MultilineString) gives away that it originally comes from YANC - "Yet Another Node Collection" - and ComfyUI-Addoor bundles it in among its own nodes. It's a primitive, and primitives are boring, but you build everything out of them.

What it's for

You need text to enter your graph somewhere: a prompt, a filename template, a snippet you'll paste into a later node. YANC.MultilineString is that entry point - a big multiline field you type into, with a single STRING output. Multiline means paragraph prompts and multi-line notes stay intact instead of getting flattened.

It's also an output node, so it renders on the canvas when the graph runs, which makes it usable as a little display panel - a place to keep notes visible right in the workflow, or to show a value you've routed into it.

Where it fits

Honestly, for a bare prompt you could use core ComfyUI's built-in text primitive. Where a dedicated string node earns its keep is in graphs where you're routing text around - feeding it into a Text Append, a Prompt Replace, or a CLIP Text Encode, and want an obvious, clearly-typed source rather than a widget buried on another node. Keep your prompt fragments in named string nodes and a big workflow stays readable; scatter them across encoder widgets and it doesn't.

If you're writing prompts for a modern LLM-encoded model (the Z-Image / Flux 2 / Anima generation), the multiline field is genuinely handy, because those models want structured, paragraph-shaped instructions - a tag block, a blank line, then a descriptive paragraph - and that's much easier to write and read in a proper multiline box than in a cramped single-line widget.

Anything to watch for

Nothing mechanical - it holds text and emits text. The only "gotcha" is that it's plain text with no weighting logic of its own; what happens to (word:1.2) or BREAK depends entirely on the encoder downstream, not on this node. On CLIP-based models those still do something; on LLM-encoded ones they're ignored. That's a property of your model, not this box.

Installing ComfyUI-Addoor

ComfyUI Manager: Install Custom Nodes → search "ComfyUI-Addoor" → install → restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/Eagle-CN/ComfyUI-Addoor.git
cd ComfyUI-Addoor
pip install -r requirements.txt

Restart and find it under 🌻 Addoor / text. If you already run the full YANC pack you may see this node twice - same thing, pick either.