Pose 2
A second pose bank so you can mix and match
- text
- id
Two pose selectors in one pack looks like overkill until you're generating a scene with two characters, and then it's obvious. Pose 1 describes one character, Pose 2 describes the other - because on a tag-based model, the model mostly binds attributes by proximity and wording, and keeping each character's pose in its own block is exactly the kind of separation that stops the two from bleeding into each other.
The Prompt String Selector pack's pose slots are text blocks, not ControlNet conditions - they describe poses in words (arms crossed, leaning on the wall) rather than enforcing them with a skeleton. That makes them the lightweight option: perfect for "vary the pose, keep the character," less useful when you need exact positioning. Pose 2 is the second bank, and its existence is the pack quietly admitting that one pose dropdown isn't enough for real scenes.
How it works
Lists .txt files in ComfyUI/custom_nodes/ComfyUI-Prompt-String-Selector/data/pose2/. Filename minus extension = dropdown label; leading number = id output; // and /* */ comments stripped; sorted by numeric prefix. Ships with 01_none.txt as a no-op option.
Inputs and outputs
- pose2 - dropdown.
- pose2_custom - multiline override;
custom_inputuses this box's text,idbecomes 0.
Outputs: text (STRING, comma-terminated) and id (INT). With a two-character scene, feed Pose 1's text and Pose 2's text into separate Aggregator slots (or the same one, in the right order) alongside their respective character blocks.
Install
ComfyUI Manager → search "Prompt String Selector", or:
cd ComfyUI/custom_nodes
git clone https://github.com/itom0717/ComfyUI-Prompt-String-Selector.git
Restart. Zero dependencies - pure Python standard library, no models to fetch.
Gotchas
Restart-to-refresh dropdowns, as with all siblings. For multi-character scenes, the order matters more than the node itself: blocks bound by proximity, so put character A's sheet next to pose A's block and character B's after it. Same two files in a different order can change which character does what - that's a prompting fact, not a node bug, but it's why having a second pose bank is genuinely useful rather than decorative.
Inputs (2)
| Name | Type | Default | Description |
|---|---|---|---|
| pose2 | COMBO | 2 options: 01_none, custom_input | |
| pose2_custom | STRING | — |
Outputs (2)
| Name | Type | Description |
|---|---|---|
| text | STRING | — |
| id | INT | — |