Nodes/ComfyUI-H3-Multishot/[deprecated] Prompt Source (txt briefs + json scripts)
ComfyUI Node

[deprecated] Prompt Source (txt briefs + json scripts)

The deprecated name for the H3 prompt source — and why it still loads

By jlucasmcrell·Created 21 days ago·Updated 2 days ago· 31
[deprecated] Prompt Source (txt briefs + json scripts)
    • story_idea
    • character
    • count
    source_file
    load_cap0
    start_index0
    character_override
    manual_path
    folder(all)
    walk_folderfalse

    JoyEcho_PromptSource is the deprecated alias for the H3 prompt source - the file-fed input node that serves .txt briefs and .json scripts to the chain. The node you're actually looking at is RiftPromptSource, and this name is kept alive purely so graphs saved against version 2.0 of the pack open unchanged instead of showing a red missing-node box.

    Here's the confusing bit the README clears up: JoyEcho_PromptSource was never actually published under that name. It was a 2.0 bug - the pack shipped its node menu under a "Rift" category and class names that leaked an internal codename, and this name slipped out in saved workflows. It doesn't appear in the release's real naming, so you'll only ever meet it as a backward-compatibility stub.

    What it does

    Everything the current node does, since it is the current node: a dropdown over LPFF-style .txt prompt briefs and passthrough .json scripts, reading from input/rift_prompts/ (with the older input/joyecho_prompts/ as a fallback), emitting story_idea, character, and count. The optional controls - load_cap, start_index, character_override, manual_path, folder, walk_folder - are the same. See the RiftPromptSource article for the full tour; the difference here is just the label on the node, which the display name marks [deprecated].

    If you're editing an old graph, drag in the current node rather than the alias. Both work, but the alias exists for compatibility, not as a place to build new work - the pack's maintainer moved on to the clean name deliberately, and future changes will land on RiftPromptSource.

    Installing it

    Same pack, same install:

    cd ComfyUI/custom_nodes
    git clone https://github.com/jlucasmcrell/ComfyUI-H3-Multishot
    

    Or search H3 Multishot in ComfyUI Manager. Requires ComfyUI v0.30.0+.

    Gotchas

    The empty-dropdown failure applies here exactly as it does to the current node: the file dropdown reads through the inspire_prompts path registered by comfyui-inspire-pack, and without that pack the dropdown comes back empty with a message that blames the wrong thing. The fix is the same three-way choice - install the pack, register the path in extra_model_paths.yaml, or set manual_path and ignore the dropdown. And if a shared workflow someone sent you has a red JoyEcho_PromptSource, that's a missing-pack symptom, not a missing node - the class resolves the moment the H3-Multishot pack is installed.

    CategoryH3/script

    Inputs (7)

    NameTypeDefaultDescription
    source_fileCOMBO1 options: (no prompt files found)
    load_capoptINT0TXT files only: 0 = all blocks, N = first N from start_index.
    start_indexoptINT0TXT files only: first block index to load.
    character_overrideoptSTRINGForce this character for EVERY emitted item (useful for .json scripts, which carry no name field).
    manual_pathoptSTRINGPoint at ANY .txt (LPFF blocks) or .json (passthrough script) file by full path, ignoring the dropdown. Removes any dependency on the inspire-pack prompts tree or input/rift_prompts/. Leave empty to use source_file.
    folderoptCOMBO(all)Filter source_file to one folder (the pack's frontend script filters the dropdown live). Appended last so saved widget order is preserved.
    walk_folderoptBOOLEANfalseOFF (default): start_index selects a block INSIDE source_file, as always. ON: start_index selects WHICH FILE, walking the folder chosen above in sorted order, and the whole file is emitted. Wire start_index to a PrimitiveInt set to 'increment' and queue N times to render a folder of finished scripts unattended. Needed because an H3 script uses --- for SHOT boundaries, so scenes cannot be concatenated into one file the way LPFF batches can.

    Outputs (3)

    NameTypeDescription
    story_ideaSTRING
    characterSTRING
    countINT