Text Multiline

VixMultilineText is the pack's original text-input node, and it's basically retired. It's a multiline text box with a single STRING output that passes the text straight through - nothing more. If you're seeing it in a workflow, it's almost certainly an old one, because the source marks the class as deprecated and modern ComfyUI will warn about it on load.

In the pack's own story, this is the node that got replaced: when the Visionatrix team built the proper VixUI family, VixUiPrompt took over the "let a user type text" job with real UI metadata and dynamic-prompts support. VixMultilineText was kept around for backward compatibility with existing flows, not as a recommendation.

Inputs

• text (STRING, multiline) - the text content. That's the entire input surface.

Outputs

One STRING output containing the text. It can feed anything string-shaped - most commonly a CLIPTextEncode prompt input or another text node.

How it works

do_it returns the text untouched. There is no mechanism to speak of - it's a data carrier, and that's it. (If you want the interesting version of this idea, use VixUiPrompt, which carries dynamic-prompts wildcards and Visionatrix UI metadata.)

Install

If you genuinely need it (i.e. you're loading an old workflow that references it):

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

Restart ComfyUI, or install ComfyUI-Visionatrix via ComfyUI Manager. No model downloads; deps are the stock torch/pillow/numpy.

The honest take

Don't build anything new on this node. It has two problems: it's deprecated, so you start every run with a ComfyUI warning, and it's redundant - the stock CLIPTextEncode prompt box is already a multiline string input, so this node adds a hop without adding capability. If the reason you're here is "this old workflow won't run," the fix isn't to keep this node, it's to replace it with a built-in text widget or VixUiPrompt. Keep it in mind as a compat shim for legacy flows - nothing more.