Rolling Character

Rolling Character is a prompt printer with a dice roll in it. It pulls one or more characters out of a 34,416-row Danbooru table and emits their prompt tags as plain text you wire straight into a text encoder. No model, no sampling, no VRAM.

The reason to care isn't the randomness. It's that each row ships with core_tags - the character's actual visual definition. Ask for Raiden Shogun and you get raiden_shogun,genshin_impact,1girl,purple eyes,mole under eye,purple kimono,obi. You don't have to know about the mole. Danbooru's taggers did that work years ago and the pack ships the result.

What you actually get back

With character_count = 3, a genshin_impact filter and seed 1234, the prompt output is literally this (tags trimmed):

rosaria_\(genshin_impact\),genshin_impact,1girl,nun,purple eyes,veil,bare shoulders,
scaramouche_\(genshin_impact\),genshin_impact,1boy,purple eyes,red eyeshadow,blunt ends,
raiden_shogun,genshin_impact,1girl,purple eyes,mole under eye,purple kimono,obi

One character per line, fields joined by commas, a trailing comma on every line except the last. That last detail is deliberate: the sibling RollingArtist node ends its output with a comma too, so you can drop both into one concat with no glue.

Turn off describe_character and you get the short form - hakurei_reimu,touhou - for when a LoRA already supplies the appearance and you only need the identity tag.

Inputs

Four are required and they are the whole node:

• character_count (1–10) - how many characters per run.
• character_top_ratio (0.01–1.0) - the popularity pool, as a fraction of the candidates left after the copyright filter. The CSV is sorted by post count descending, so this means "take the first N rows," the most-drawn characters on the board. At the default 0.01 with no filter, that's the top ~345.
• character_top_count (1–10) - how many picks are guaranteed to come from that pool. The knob that stops you rolling nine nobodies.
• seed - reproducibility, with a caveat below.

Then the ones you'll actually use: copyright_pick is a combo box of all 3,460 franchises in the shipped CSV, sorted by total post count, type-to-filter, (不限) for no filter. exclude_characters and force_include take comma-separated names; force wins over exclude, and names not in the CSV still work - they just arrive with no copyright and no description. Turn off use_top_priority for a flat uniform draw. The two advanced fields (custom_csv_path, tested_db_path) are folded away; leave them blank. If you do point custom_csv_path at your own table, copyright_pick won't follow it - that dropdown is built once, from the default file, at node registration.

One thing this node deliberately doesn't do: weights. The artist node in the same pack assigns (name:0.8); character tags are identity, not style, and (raiden_shogun:0.7) isn't something you want.

Outputs

prompt is the text block above. characters_json is the same draw in structured form - name, copyright, top, count, core_tags - for when something downstream parses rather than encodes. tested_count is a string (it changed from INT in 4.1.0) counting rows logged in rollingcharacter.sqlite.

Install

ComfyUI Manager → search the pack title, or by hand:

cd ComfyUI/custom_nodes
git clone https://github.com/StarAsh042/ComfyUI_RollingArtist.git

Restart ComfyUI. That's it - requirements.txt in this repo is empty. No pip step, no model download, no compiled anything: stdlib Python plus SQLite, and both working CSVs (50,018 artists, 34,416 characters) are committed to the repo. The two large *_full.csv files are Git-LFS pointers, but they're only inputs to the optional rebuild scripts - ignore them.

The README is Chinese-first, which is probably why you've never heard of this pack. The node's labels and tooltips follow your ComfyUI locale (Comfy.Locale), and English strings ship in locales/en/.

Where people get burned

Your seed is not as reproducible as it looks. The node avoids repeats across the last 10 outputs, and that window lives in memory, not in the database. Same seed, same settings, different result depending on what you generated five minutes ago. Restarting ComfyUI clears it; tested_db_path does not - that's a different thing, and the tooltip says so.

The seed widget rolls. It's an ordinary integer control, so it ships with ComfyUI's control_after_generate dropdown. Find a character you like, leave the control on fixed, and every queue gives you that same one - either exactly what you want, or the reason you think the node is broken.

Small franchises run dry. Filter to a 40-character series, ask for 10, and the avoidance window eats everything. It won't error - it logs a WARNING and starts repeating, which is why you'll occasionally see the same face twice.

About 22% of characters have no core_tags, so those lines come out short: name plus franchise, nothing else. That's the data, not a bug.

The two advanced path fields read and write whatever you type, with no sandboxing. Fine on a box only you touch. If your ComfyUI is reachable from the LAN with workflow execution enabled, anyone can make this node read a CSV or write a SQLite file anywhere on your disk.

The honest caveat

Stacking three random characters into one prompt does not give you three characters. SDXL-family anime models have no syntax for binding an attribute to a character, so hairstyles and eye colours bleed across everyone in frame and the better-known character tends to win. Keep character_count at 1 unless you're deliberately chasing a fusion - which is exactly what this node is good at.