MiniMax H3 Prompt Map

Here's an honest one: the MiniMax H3 Prompt Map is a compatibility shim. Its own docstring says so - MiniMax H3 has no "PromptRelay" or per-step conditioning schedule in ComfyUI's native implementation, so this node exists so that older Shotboard workflow JSONs keep opening without errors. It returns the one static prompt for a given segment, along with the segment's timing numbers. That's not a knock against it; knowing a node is a shim saves you from hunting for features that were never there.

What it does

Give it the cine_linx shot plan and a segment_index, and it pulls that chunk's prompt from the plan. If you connect prompt_override, that wins instead. Then it reports the chunk's start_seconds, duration_seconds, frame_count, and total_segments alongside.

The mechanism is one function: read the plan, grab the chunk, return the prompt string. It's a typed window into the shot plan for graphs that need the prompt as an explicit STRING - for example, to display it, to log it, or to feed it into a prompt-editing chain before it reaches a conditioning node.

The context that matters

This node exists because the older IAMCCS Shotboard graphs were built around a "PromptRelay" concept - a scheduled, per-segment prompt system borrowed from other video workflows. When the author moved the Shotboard onto native MiniMax H3, that scheduled concept didn't map over (H3 takes one prompt per conditioning call), so rather than break every existing workflow file, they kept the node name and made it resolve to the single static prompt. If you load an old IAMCCS H3 workflow today and see this node, it's working - it's just not doing anything a simpler plan lookup wouldn't do.

Inputs and outputs

Inputs: cine_linx, segment_index, and an optional prompt_override (multiline). Outputs: prompt (STRING), start_seconds and duration_seconds (FLOAT), frame_count and total_segments (INT), and report. The report is your friend here - it spells out the segment, slot label, frame count, and the plan's prompt_mapping setting, so you can confirm which segment's prompt you actually pulled.

Installing it

Standard pack install: ComfyUI Manager (search "IAMCCS") or git clone https://github.com/IAMCCS/IAMCCS-nodes.git into custom_nodes, then restart. No extra dependencies.

Should you use it?

If you're building a new workflow, probably not - the Shotboard Backend and the FLF Conditioning nodes read the prompt from the plan internally, so you don't need a separate lookup. Reach for this one if you're maintaining an older IAMCCS workflow, if you need the prompt as an explicit string output for display or logging, or if you want to intercept and override a plan prompt cleanly before conditioning. It's a fine tool - just don't expect scheduling features that the class name might suggest.