T8 战斗运镜配置 / Combat Camera Config

T8CombatCameraConfig is a three-dropdown settings card. It doesn't generate anything, doesn't call a model, produces no video. You wire it into the MiniMax H3 or Seedance 2.0 prompt enhancer from the same pack, and its whole job is to make that enhancer write better camera language for action already in your prompt.

That sounds thin until you've watched AI fight clips. The complaint is never resolution - it's that nobody's home. The punch misses by a metre, the two "fighters" shadow-box past each other, the camera whips around and you lose track of who's where. Not a sampler problem: a direction problem.

What it is, in the wider workflow

The pack is a family of prompt enhancers: type a rough video idea, an LLM (cloud or local GGUF) rewrites it into a native MiniMax-H3 or Seedance 2.0 prompt, and you hand that string to the real video generator. Everything here is text, upstream of the sampler.

It also explains the design. The default failure of an "enhance my prompt" LLM is invention - enemies, weather, slow motion, a dramatic ending nobody asked for. Prompt enhancement is a known subject-drift problem, and this pack's answer everywhere is to narrow the LLM's job rather than trust a free rewrite. This node is the narrowest of those jobs. The author is upfront that it's adapted from a user-supplied handbook, is not a MiniMax official Skill, and is not evidence that anything renders better.

How it works

The three widgets compile to a small dict tagged t8-combat-camera-config/v1, get validated against the node's finite option lists, and travel down a custom socket typed T8_COMBAT_CAMERA_CONFIG. The enhancer turns that into an instruction block - one flavour for H3 (keeps native fields, [Shot N]/time syntax, vocal grammar), a separate one for Seedance (natural language only, at most one primary camera move per shot). What goes in is a menu, not a routine: low tracking for a rush, reveal the crossing point for a dodge, upward tracking for a leap, a brief stabilisation on contact, widening only along existing displacement on recoil, and never an invented next attack.

Two things to know before you spend money:

• No extra model call. The rules ride along in the existing enhancement request - the author's paid A/B measured about +786 input tokens for H3 and +801 for Seedance. Existing repairs and retries can still bill as before.
• 关闭 / Off is a real off. With mode Off the config resolves to nothing, nothing is injected, and requests stay byte-identical to before. That's your A/B switch when troubleshooting.

The inputs that matter (all three)

• mode - AUTO（按已有战斗动作） / 强化（明确轨迹与落点） / 关闭 / Off. AUTO only fills camera gaps in combat that's already present; 强化 materially rewrites weak ones. Neither authorises combat: a displayed weapon or a character title doesn't count, and neither invents opponents, injuries or a winner.
• continuity - 沿用原设定 / Follow (default) or 偏好连续镜头 / Prefer continuous. A preference, not an override: fixed shot count, locked-off camera, POV and first/last-frame anchors all outrank it, and it never changes the count.
• impact - 写实 / Natural (default) or 风格化 / Stylized. Natural wants readable contact in real time, no freeze, ramp, shockwave or particles. Stylized permits a brief emphasis; it doesn't force shake or a held pause.

Output: one 战斗运镜配置 / Combat camera config socket (T8_COMBAT_CAMERA_CONFIG). It only fits the 战斗运镜配置（可选） / Combat camera input on MiniMaxH3PromptEnhancerT8 or Seedance20PromptEnhancerT8 - the resolver throws on anything else, so don't try to feed a generic text node.

Installing it

It ships with the enhancer pack, so there's nothing separate - but you need one of the two enhancers for it to do anything.

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

Manager: search MiniMax H3 / Seedance 2.0 / Music 3 Prompt Enhancer (T8), or run comfy node install minimax-h3-seedance-music3-prompt-enhancer-t8. Restart ComfyUI, then Ctrl+F5. The API key and GGUF settings live on the enhancer, not here. It appears under T8/Utilities.

Common issues and gotchas

Nothing renders. Correct - it isn't an output node. The only visible result is a different enhanced_prompt string. Also confirm it's connected; unconnected or Off is a deliberate no-op.

Node missing after a Manager install. The README warns Manager can quietly fall back to an older "Active" Registry version while a newer one is pending, still reporting success. This node is recent, so an old build won't have it. Clone from GitHub and keep one copy in custom_nodes.

Invalid combat camera option. The config is version-tagged and only accepts the exact enum strings this node writes, so that message means the data didn't come from this build - hand-edited workflow JSON, or two pack copies fighting.

Known defect: timecode punctuation. In the author's paid A/B, H3 fixed-two-shot outputs came back with full-width Chinese commas after timecodes in both the on and off arms. The pack now repairs shot-timecode punctuation locally, without extra calls, leaving numbers, dialogue and on-screen text alone. Same report, funnier: the enhancer once renamed a character's sleeve into an arm guard. Clothing categories are now pinned.

Don't expect a leap. That A/B is honest to the point of self-sabotage - enabled runs scored a couple of points higher on most scenes, and on one H3 case the off arm won. Tiny sample, non-deterministic seeds. A readability nudge, not a guarantee. And the pack's "restore last result" button re-reads the cached response, so it ignores whatever you just changed here.