🐳Clothing Selector (Number Selection)

The 🐳Clothing Selector (Number Selection) node is the odd one out in the Pond clothing family: instead of dropdowns or random generation, you type a number to pick a garment. Each clothing category has an editable numbered list, and you tell the node which entries you want by number - 1, 3, 7 in the dress field gets you those three dresses. It's less pretty than the dropdown version, but it's more powerful in one specific way: the lists are editable text, so you can swap in your own garments and the numbers just keep working.

The mechanism is dead simple. Each category - 连衣裙 (dresses), 上衣 (tops), 下装 (bottoms), 泳装 (swimwear), 运动装 (sportswear), 内衣 (underwear), 外套 (outerwear), 特殊服装 (special) - has a _列表 input holding a numbered list (defaults to the built-in ~25 garments per category, each with its Chinese name and English tag) and a _选择 input where you type the numbers to select. The node parses those numbers, looks them up in the lists, and emits the chosen tags. Because both the list and the selection are plain strings, you can drive them from any text node - that's how you build a programmatic wardrobe.

The inputs that matter

• 连衣裙_选择 / 上衣_选择 / 下装_选择 (and the rest) - the number strings. Ranges like 1-5 work, and the tooltip confirms they accept comma lists.
• _列表 per category - the editable catalogs. Replace the defaults with your own garments (keep one per line, with the numbering) and the node becomes your tag engine.
• separator - comma/space/newline, how tags join.
• output_format - english, chinese, or both. This is the switch that decides which language's tags come out.

Output

One STRING output, tags. There's no separate positive/negative split and no per-category outputs - everything you selected lands in one joined string. Wire it straight into a CLIP Text Encode.

Install and the honest take

From comfy_Pond_Nodes (Manager search, or git clone https://github.com/Pondowner857/comfy_Pond_Nodes + pip install -r requirements.txt). Pure data, no models.

Honest take: this node only earns its keep over the dropdown version if you actually use the editable lists or drive the numbers from elsewhere. If you're just going to click around, ClothingSelector's dropdowns are friendlier. But the editable-list angle is real - being able to maintain your own garment catalog as plain text and reference it by number is a genuinely neat workflow, and it's why this node exists rather than being redundant. Same family caveat as always: the built-in catalog skews heavily toward women's fashion.