Dependencies Edit

Fair warning up front: the pack's README doesn't document this node at all, so what follows is read directly off its inputs and outputs rather than the author's own description. Take the mechanism as reliable - it's what the node's typed fields say - but treat the framing as inferred.

DependenciesEdit takes a DEPENDENCIES bundle - ArtVenture's own manifest object, separate from the PIPE system used by the parameters nodes, likely covering "everything needed to run a generation": checkpoint, VAE, CLIP, a prompt pair, a LoRA stack, a ControlNet stack - and lets you override some of those fields while leaving the rest untouched. The defaults are the tell: the checkpoint, VAE, and prompt fields all default to the literal string "Original", which reads as "don't change this, keep whatever the incoming bundle already had." That's an override node, not a builder - it exists to let one part of a shared manifest vary per run without reconstructing the whole thing from scratch.

How it works

You pass in an existing dependencies bundle. Anything you leave on its default ("Original", or unwired) passes through unchanged; anything you actually set - swap the checkpoint, override the prompt, attach a different LoRA or ControlNet stack - replaces that one field in the outgoing bundle. The result is a new DEPENDENCIES object, same shape as the input, with your overrides applied on top.

The inputs and outputs that matter

One required input:

• dependencies - the bundle to edit.

A handful of optional overrides:

• ckpt_name / vae_name - dropdowns defaulting to "Original" (and "Baked VAE" as a second VAE option) - leave on default to inherit, pick a name to override.
• clip - swap in a different CLIP object entirely.
• clip_skip (default 0, range -24–0) - the standard CLIP-skip mechanism: negative values skip that many layers from the end of the text encoder. -2 is the common value for anime-lineage checkpoints that expect it.
• positive / negative - multiline text, both defaulting to "Original" - override the prompt pair, or leave them alone to inherit whatever the bundle already carried.
• lora_stack / cnet_stack - swap in a different LoRA or ControlNet stack.

One output: DEPENDENCIES, the edited bundle, presumably consumed by another ArtVenture node further down the chain that actually reads it and drives generation.

How to install it

Comes with the Art Venture pack. ComfyUI Manager: search comfyui-art-venture, install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/sipherxyz/comfyui-art-venture

Restart ComfyUI. No model downloads for this node itself.

Common issues & troubleshooting

Nothing changed even though I set a field. Double-check you didn't leave it on "Original" by accident - that value means "inherit," not "use a checkpoint literally named Original." If you want an override to take effect, pick an actual name or type actual text.

Not sure what feeds dependencies in the first place, or what reads it back out. Neither is documented in the pack's README as of this writing. If you're working from a template workflow that already uses this node, trace the dependencies wire both directions to see what's building and consuming it in your specific graph - the node's own behavior (override-or-inherit) is straightforward; the surrounding system it's part of is the part worth mapping before you rely on it.

This feels like unnecessary indirection. For a single generation, wiring a checkpoint loader and text encodes directly is simpler and easier to debug. This node is for cases where a shared manifest gets reused across many runs and you need to vary one piece - a prompt, a LoRA - without touching the rest.