选择参数🐠meeeyo.com

SelectionParameter is the most specific node in this pack, and I mean that in the worst way. It gives you two drop-downs - gender (男性/女性, male/female) and version (竖版/横版, portrait/landscape) - plus a multiline text box, and it outputs a string that looks like this:

1+1

附加的多行文本内容

That's it. The gender maps to 1 or 2, the orientation maps to 1 or 2, they're joined with a +, and your additional_text is appended two newlines below. There's no prompt building, no conditional logic, no parsing of the output. It encodes your two selections into a two-digit code and tags your text onto the end.

The Chinese display name is 选择参数 ("select parameter"). It's part of ComfyUI_StringOps, the same pack as everything else branded 🐠meeeyo.com.

Why it exists (and why it probably doesn't fit you)

This is clearly a bespoke node built for the author's own pipeline - almost certainly a commercial Chinese image service where a "male + portrait" request needs to be encoded as a compact code the rest of their system recognizes. The output format 1+1 is an internal convention, not a standard. If you are not running that exact pipeline, the format is arbitrary and you'd be better off with any of the pack's generic string nodes.

The inputs: gender, version, additional_text (multiline, default "附加的多行文本内容" - placeholder text). One STRING output.

If the author's workflow is your workflow - you're a customer of their service and this node is how you compose a request - then this is exactly right, and none of my skepticism matters. But if you googled this node hoping for a general "select A or B and get text" utility, know what you're getting: it's hardcoded to gender and orientation.

Can you repurpose it?

Only barely. The two drop-downs are fixed (male/female, portrait/landscape) and the encoding is fixed (1+1). You can't rename the options in the UI. So while the shape of the node - pick two things, emit a code plus your own text - is a reasonable pattern for building a reusable "settings" node, this implementation is frozen to its creator's needs. If you want a generic version of this idea, the pack's MultiParamInputNode gives you editable fields, and TextConcatenator lets you build the joined output yourself with a separator you control.

Installing it

Pack standard: ComfyUI Manager → ComfyUI_StringOps, or

cd ComfyUI/custom_nodes
git clone https://github.com/MeeeyoAI/ComfyUI_StringOps.git

Restart. No dependencies beyond what ComfyUI already ships.

The honest take

I'll be blunt: unless you're part of the author's ecosystem, skip this node. It's a demo of what this pack's author needed, shipped to everyone. The interesting lesson is the pattern - a compact code + attached text from a couple of dropdowns is a decent way to parameterize a workflow - but you can build that with more flexible nodes and not inherit someone else's 1+1 convention. If you do end up using it, the only thing to remember is that the output is a string, so feed it where strings go: a prompt input, a TextToList, or a display node.