Character Clothing

Character Clothing is the wardrobe department of the Fictiverse pack's Character Crafter family. You pick a top, a bottom, colors, and accessories from dropdowns - or a full-body garment like a dress, suit, or armor - and it assembles a sentence describing what the character is wearing. "wearing a jacket in black and pants in blue with a belt." Wire that into your prompt and you've got a consistent outfit that survives across a whole batch of images.

The pitch is the same as Character Appearance and the rest of the family: consistent phrasing beats hand-typed prompts when a character has to stay the same across many renders. If you're generating a character sheet, a comic, or a multi-frame animation, you want "wearing a sweater in red and pants in black" to be byte-identical every single time - which a dropdown guarantees and a human won't.

How it works

You've got three "slots" - top, bottom, and full-body - and the node decides which to use. The logic: if full_body is set to anything other than None, the top and bottom choices are ignored entirely, and the sentence describes only the full-body garment. Set full_body to None and the node looks at top and bottom separately. This is the thing to internalize - it's not "dress + shirt", it's "either full-body or top-and-bottom", and whichever path you didn't choose gets dropped.

Colors work per garment: each slot has its own color dropdown, and the color only applies if the garment is set. The accessories dropdown (Belt, Necklace, Ring, Hat) appends "with a belt" style phrasing at the end.

The "No" vs "None" trap

This is where beginners get burned, and it's worth reading carefully:

• None means "not specified" - the node stays silent about that item, and the model decides.
• No means "explicitly absent" - the node says the character isn't wearing that thing.

Pick top = "No" and you get "nothing on top." Pick full_body = "No" and the node literally writes "nothing and is naked." These produce very different prompts, and "No" is a real instruction to the model while "None" is a shrug. If your character is supposed to be shirtless, that's "No", not "None" - and if it's just "whatever looks good," that's "None".

Inputs and outputs

The dropdowns: top and top_color, bottom and bottom_color, full_body and full_body_color, accessories. All have None as their first option, and the garment lists include explicit "No" choices. Plus the optional prefix wildcard for prepending a character name or style tag.

Output:

• clothing_text (STRING) - the assembled outfit sentence.

Feed it into your prompt build (a text concat, or the pack's Prompt Assembler) alongside the appearance, expression, and makeup nodes for a fully dropdown-built character.

Installing it

In ComfyUI Fictiverse Nodes. ComfyUI Manager → search "ComfyUI Fictiverse Nodes" → install → restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/Fictiverse/ComfyUI_Fictiverse

No dependencies, no models. Apache 2.0.

Common issues

Pack gotcha: ModuleNotFoundError: No module named 'custom_nodes.ComfyUI_Fictiverse' means the folder isn't exactly ComfyUI_Fictiverse; rename and restart.

Node-specific: the full-body-overrides-top-bottom behavior surprises people who set a dress and a top expecting both. And remember the color dropdowns are independent - setting top_color = Red with top = None does nothing, because the color is tied to the garment. If the outfit looks wrong, double-check you didn't leave a stray color set on a garment you thought was off.