Nodes/was-node-suite-comfyui/Text Multiline (Code Compatible)
ComfyUI Node Runs on cloud

Text Multiline (Code Compatible)

A text box that won't mangle your syntax

By WASasquatch·Created 3 years ago·Updated about a year ago· 1,812
Text Multiline (Code Compatible)

      WAS Node Suite ships a plain "Text Multiline" node for writing a chunk of text straight into your graph, and then it ships this one - the "Code Compatible" version - for the same job with a different promise: it won't touch what you typed. If you've ever pasted a JSON snippet or a bit of Python into a multiline text widget and had it come back with your straight quotes swapped for curly ones, or leading whitespace stripped, you know why this variant exists. Prompt-text widgets are built to be forgiving with prose; that same forgiveness is exactly what breaks a snippet where every character is load-bearing.

      What it's for

      Think of it as a plain source node: you type or paste text into it once, and it outputs that text unchanged to whatever's downstream. There's nothing to configure and no upstream input required - it's where a string starts its life in your graph. The single text output is a standard string, so it plugs into anything that expects one: a CLIPTextEncode, a Save Text File, a Text Concatenate, or one of WAS's own text-processing nodes further down the chain (Text Find and Replace, Text Contains, and so on).

      The practical case for reaching for this over the regular Text Multiline is anywhere exact characters matter: a JSON config blob you're routing through a Text Dictionary Convert node, a snippet you want printed verbatim into a saved text file, or a wildcards/token string with brackets and underscores you don't want auto-corrected. If you're just writing prose for a prompt, the plain Text Multiline is fine and arguably simpler - save this one for when formatting fidelity is the point.

      Installing it

      It comes bundled with the whole WAS Node Suite pack, not as a standalone install:

      • ComfyUI Manager - search WAS Node Suite (or "was-node-suite-comfyui"), install, restart.
      • Manual - cd ComfyUI/custom_nodes && git clone https://github.com/WASasquatch/was-node-suite-comfyui/, then inside that folder run pip install -r requirements.txt (use your portable install's python_embeded/python.exe -s -m pip install -r requirements.txt if you're on the Windows portable build), then restart ComfyUI. A was_suite_config.json gets generated in the pack's folder on first launch - that's where wildcard paths and a few other pack-wide settings live, and it's shared by every WAS node, not just this one.

      Common issues

      The one thing worth knowing before you install: WAS Node Suite has been unmaintained since December 2023 - the author (WASasquatch) said outright he doesn't have time to keep developing it and invited forks. The practical fallout shows up as "Import Failed" errors after you update ComfyUI or another pack, because WAS's requirements.txt still pins some shared dependencies to older versions for legacy features, and a newer ComfyUI update can collide with that pin. It's a genuinely common complaint - the author himself has replied to threads about it, explaining that upgrading ComfyUI upgrades packages WAS quietly downgrades for backward compatibility. If you hit "Import Failed," the fix is usually reinstalling requirements.txt fresh inside your ComfyUI venv, or manually reinstalling the specific conflicting package (opencv-python is a repeat offender) at a version WAS expects.

      For this particular node, once it imports cleanly there's not much else to break - it's a text box, not a process. If your text is coming out altered anyway, double check you're using this node and not the plain Text Multiline by mistake; they sit right next to each other in the WAS Suite menu and it's an easy substitution to miss.

      Categoryx

      Inputs (0)

      No inputs

      Outputs (0)

      No outputs