TextBox3

Not every node needs a clever mechanism. TextBox3 is exactly what it sounds like - three independent multiline text fields living in one node instead of three separate stock ComfyUI Text nodes cluttering your graph. The value is entirely organizational, and if you've ever tried to keep a big RES4LYF sampling workflow readable, you know that's a real value, not a throwaway one. ComfyUI graphs sprawl fast once you're wiring in multiple conditioning branches, and every extra node is another box to drag, another wire to route, another thing to lose track of when you zoom out.

How it works

Type into text1, text2, text3, and each comes back out unchanged as its own string output. That's the whole node. No merging, no processing, no dependency between the three fields - it's storage and passthrough, not logic. You could get the identical result from three separate stock Text (Multiline) nodes; this just saves you the screen space and the extra wiring of grouping and moving them as one unit.

The inputs and outputs that matter

• text1, text2, text3 (STRING, multiline) - three independent text fields.
• Outputs: text1, text2, text3 - each a straight passthrough of its matching input.

Where this actually earns its keep: RES4LYF's regional and temporal conditioning systems support "unlimited zones," and once you're juggling more than one or two prompt fragments per workflow - subject/style/negative splits, or separate per-region prompts for a multi-zone image, or per-window prompts for a temporal Wan clip - one TextBox3 keeps things bundled and easy to reroute as a group instead of scattering loose text nodes across the canvas. It's a small thing, but small things compound once your graph has forty nodes in it.

How to install it

Via ComfyUI Manager: search RES4LYF, install, restart.

Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/ClownsharkBatwing/RES4LYF
cd RES4LYF
pip install -r requirements.txt

Portable installs: use the embedded Python's pip.exe instead of a venv pip. This node has no model or dependency footprint of its own - it's pure UI convenience, installed the moment the pack is.

Common issues & troubleshooting

There's genuinely not much to break here. If an output isn't showing up where you expect downstream, it's almost certainly a wiring mistake elsewhere in the graph - each output is a direct passthrough of its own input, so the node itself has no failure mode to speak of.

If you're expecting it to combine or concatenate the three fields - it doesn't. For that, reach for TextBoxConcatenate instead, which is built specifically to glue text together rather than just hold it. And if you're expecting it to check or limit token length before you feed a field into a CLIP encoder, that's not this node's job either - TextTruncateTokens is the one that handles per-encoder length limits; this one is purely storage.