MiniMax H3 Prompt Relay Event / 单事件串联 (Advanced)

MiniMaxH3PromptRelayEventT8Advanced is the Lego brick of the Prompt Relay system: one node, one timed action, and you chain as many as you need by wiring each one's output into the next one's previous_events input. Build a chain of three, four, or twelve events and the last node in the chain hands the whole list to the Plan node, which treats it as the authoritative event source.

The discipline it enforces is the actual feature. Each event's prompt should describe only that time window's action - the tooltip's instruction is worth quoting: don't repeat the global character/scene/sound setup in every event. Global stuff goes in global_prompt on the Plan; the events are purely "she looks at the camera," "she turns and walks," "camera pulls back." Keep them that way and the relay routing has clean local signals to work with.

The inputs that matter

• prompt - the one local action for this window.
• start / end - interpreted by the timing mode of the downstream Plan/Packet bridge. In auto_equal mode they're ignored and events split the timeline evenly. In frames mode, start is an integer frame and end is an inclusive endpoint. In seconds/percent modes, end is a boundary. Multiple events must be sorted by start time.
• enabled - the graceful way to mute an event. Turn it off and it simply isn't added to the chain. Chain every event off and the Plan becomes a global-prompt passthrough - no need to delete nodes or rewire. That's the "additive" design philosophy this whole pack follows: advanced nodes don't change old workflows when they're not doing anything.

Outputs: prompt_relay_events (the chain handle), plus preview_json and report_json per event.

Why chain instead of typing JSON

The event-chain route is the UI-friendly alternative to local_prompts/time_ranges text on the Plan node, and it composes - each event is a separate node you can mute, retitle, and reorder by rewiring instead of editing a blob of text. It also flows through the Studio bridge: MiniMaxH3PromptPacketRelayPlanT8Advanced accepts the same H3_T8_PROMPT_RELAY_EVENTS type, so a chain built here feeds both the hand-written Plan and the compiler-based Packet bridge identically.

One trap worth knowing: because the chain's last node carries the full list, bypassing or deleting a middle node drops everything after it. If an event mysteriously vanishes from your timeline, check the chain isn't broken - the Plan falls back to local_prompts/time_ranges only when the chain input is unconnected, so a silently-broken chain can look like a missing event.

Install

Ships in the MiniMax H3 Audio T8 pack:

cd ComfyUI/custom_nodes
git clone https://github.com/T8mars/comfyui-minimax-h3-audio-T8

or search "MiniMax H3 Audio T8" in ComfyUI Manager and restart. No pip deps. The relay templates under examples/workflows/14-prompt-relay/ show chains in action - start with 2026-08-20_H3_Prompt_Relay_T2VA_Stock20_Advanced_EXP.json and read each event's preview_json to check your ranges before you load a model.