IO Config (Badman)

This is a genuinely useful pattern even though the node itself is opinionated to the point of being personal: give it a base folder and a shot name once, and it hands back nine pre-built subpaths for the various inputs and outputs a video/character pipeline tends to need - image and video outputs, upscaled versions of each, and input paths for source images, depth maps, pose guides, body masks, and face masks. Wire it in at the top of a graph and every downstream save/load node reads its path from here instead of you retyping folder structure into a dozen separate nodes.

What it's actually for

Look at the shape of the nine output paths - image and video output, upscaled image and video output, plus separate input slots for images, depth, pose, body masks, and face masks - and it's clearly built for a ControlNet-heavy character or video pipeline, the kind that leans on depth and pose guides and separate masking for body versus face. Combined with the rest of this pack (WAN-specific nodes, latent noise injection, chroma cleanup), it reads like plumbing for Marius's own video workflow rather than a generic file-path utility. That's not a knock - it's exactly the shape a "set this up once per shot" node should take when your pipeline has a consistent folder convention across projects.

The honest catch, straight from the author

The pack's own README lists this under its TODO section, in the author's own words: "IO Config (Badman): Refactor to allow for renaming specific I/O paths, currently fixed path names that I tend to use." That's worth taking at face value - the nine output slots (ImageOutputPath, VideoOutputPath, ImageUpresOutputPath, VideoUpresOutputPath, ImageInputPath, DepthInputPath, PoseInputPath, BodyMaskInputPath, FaceMaskInputPath) are fixed to that naming and that folder layout. If your own pipeline needs different subfolders, doesn't use pose or depth guides at all, or splits things differently, this node's structure won't bend to fit - you're either adapting your file layout to match it, or skipping it and building your own path-setter node instead.

Inputs and outputs

Two required fields: BasePath (string, default /tmp/ComfyUI\output\) and ShotName (string, default empty). Note the default BasePath mixes a Unix-style base with Windows-style backslash separators - a leftover from whatever machine the author was on when they set the default, not a value meant to be used as-is. Override it with a real path for your own setup before relying on this node.

Nine outputs, all STRING: ImageOutputPath, VideoOutputPath, ImageUpresOutputPath, VideoUpresOutputPath, ImageInputPath, DepthInputPath, PoseInputPath, BodyMaskInputPath, FaceMaskInputPath - each presumably BasePath plus ShotName plus a fixed subfolder, wire each into the matching load/save node in your graph.

Installing it

ComfyUI Manager: search ComfyUI-BadmanNodes, install, restart. Manual: cd ComfyUI/custom_nodes && git clone https://github.com/MariusKM/ComfyUI-BadmanNodes. No dependencies - this is string path-building, no models involved.

Where people get burned

Set BasePath explicitly before your first real run - the shipped default is a Windows-flavored path baked into a Unix-style root, and it's not going to resolve correctly on most setups without you overriding it. Beyond that, remember the fixed naming from the TODO above: if you're not using half of these nine paths (say, no pose or depth guides in your pipeline), it's fine to just not wire those outputs anywhere, but don't expect to rename or restructure them from within the node - that refactor hasn't shipped yet per the author's own list.