Nodes/RuiquNodes for ComfyUI/EvaluateMultiple9
ComfyUI Node

EvaluateMultiple9

Run your own Python across nine inputs at once

By ruiqutech·Created 2 years ago·Updated 2 years ago· 0
EvaluateMultiple9
  • in1
  • in2
  • in3
  • in4
  • in5
  • in6
  • in7
  • in8
  • in9
  • out1
  • out2
  • out3
  • out4
  • out5
  • out6
  • out7
  • out8
  • out9
expression
input_count9
print_to_console

The largest fixed size in this pack's evaluate family: nine inputs (in1in9), nine outputs (out1out9), one expression box of Python running across all of them. Past this you're not switching nodes anymore - every EvaluateMultiple variant shares the same input_count widget up to 20, so if you need more than nine lanes, this is the one you drag the slider on rather than hunting for an "EvaluateMultiple12."

What actually lands here

At nine lanes you're squarely past "quick inline calculation" and into "this replaced a small script." That's a completely legitimate use - deriving nine related values from a shared computation, remapping a batch of settings, building nine formatted strings from the same inputs - but it's worth being honest about the trade-off: a nine-wide node with a dense block of Python inside it is exactly the kind of thing that's unreadable to future-you in three months, because none of that logic is visible from the graph itself. If the expression is doing anything non-trivial, keep it commented, or consider whether the logic actually belongs in a real custom node instead of a text box.

Inputs and outputs

  • expression (multiline STRING) - blank by default.
  • input_count (INT, 1–20, default 9).
  • print_to_console - debug echo.
  • Optional: in1in9 (type *).
  • Outputs: out1out9.

The caution, one more time

This is unrestricted Python - the pack's README says it runs "any fragment of Python code," and nothing in the schema suggests otherwise. rgthree-comfy's comparable Power Puter node deliberately does the opposite (AST-parsed, allowlisted, no file or network access) precisely because its author was asked whether an expression-evaluator is an arbitrary-code hole and wanted a defensible answer. RuiquNodes doesn't make that claim, so don't assume it. Write expressions you understand; don't drop one you found in someone else's shared workflow without reading through it.

Installing it

ComfyUI Manager: search RuiquNodes, install, restart. Manual:

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

then restart. No models to download.

Common issues

Some of the nine outputs never populate. Your expression has to explicitly assign every outN that something downstream reads - an output your code never sets stays None, silently, not as an error.

The node is unwieldy on the canvas. That's the trade-off of nine sockets on one node. Group it, collapse it when you're not actively editing the expression, and keep the logic itself as short as the task allows.

Debugging a wrong value. Turn on print_to_console and check the ComfyUI terminal rather than guessing - it's faster than threading a Show Text node onto each of nine outputs.

You only actually need three or four outputs. Nine sockets doesn't mean nine obligations - leave the rest of in4in9 and out4out9 unwired. There's no penalty for using a node below its maximum size, and it beats swapping to a smaller variant later if the job grows.

Categoryruiqu/evaluate

Inputs (12)

NameTypeDefaultDescription
expressionSTRING
input_countINT91–20
print_to_consoleCOMBO2 options: False, True
in1opt*
in2opt*
in3opt*
in4opt*
in5opt*
in6opt*
in7opt*
in8opt*
in9opt*

Outputs (9)

NameTypeDescription
out1*
out2*
out3*
out4*
out5*
out6*
out7*
out8*
out9*