🔀11漫剧资料合流@炮老师的小课堂

The 🐠 漫剧 suite can be wired two ways: serial (one long chain) or branched - asset-image prompts down one line while the storyboard builds from the same script and visual setting down another. When you branch, you eventually need to rejoin, and that's the entire job of DapaoDramaMerge (advanced node 11). It takes two DAPAO_DRAMA_BUNDLE streams (📦 支线A and 📦 支线B), merges their documents into one bundle, and refuses to do anything dumb while it's at it.

Why it exists

In the branch-and-merge topology, both branches start from a shared upstream bundle and each adds its own docs: the image branch produces 图片提示词.md (the IMG identity boards), the storyboard branch produces 分镜.md and then 视频提示词.md. The two must come back together before review and delivery because the video stage wants both the IMG assets and the storyboard in one context. Merge is that junction.

How it works - the safety rules

Under the hood it's clone-both-bundles, then strict conflict checking, then a union of documents:

• Project settings must match. If branch A was stamped from a different project config - different episode number, different aspect ratio, different style - it refuses. You branched from the same project entry, so this only trips when you wired two different episodes' bundles together by mistake, which is precisely when you want to be stopped.
• Same document in both branches with different content = refusal. If both branches somehow produced a 剧本.md and they differ, it errors rather than letting one silently clobber the other. The doc tells you both versions must come from the same upstream before you can merge.
• Stale documents block the merge. Everything in the result is fingerprint-checked against its sources; expired docs make it throw.

If the checks pass, the merged 📦 合流资料包 comes out the first output and a short ℹ️ 合流信息 string lists which docs ended up in the bundle. That's it - two inputs, two outputs, no API key, no LLM call, no cost. It's the simplest node in the pack and it's free on purpose: bookkeeping shouldn't bill you.

When you'd use it (and when you wouldn't)

Use it when you're on the advanced 11-node flow and running the parallel topology (asset-images down one branch, storyboard down the other) - the docs show both 05 → 06 → ... and the branched layout in the example workflows. Skip it entirely if you're on the guided three-node flow (DapaoDramaPrepare → Visual → Finish) - those three pass the bundle forward automatically and you never branch, which is the whole point of the guided path. And if you're running serial, you don't need merge either; it only exists to rejoin forks.

Installing

It installs with the pack - Manager → "dapaoAPI", or git clone https://github.com/paolaoshi/ComfyUI-dapaoAPI into custom_nodes, then restart and Ctrl+F5. No weights, no key, nothing else. If merge keeps refusing on you, check that both inputs really come from the same project node's lineage (same 集号/settings), and that neither branch has stale docs - fix those upstream and merge will behave.