🌀 BV Subgraph Divider

BV Subgraph Divider draws a horizontal separator line across your graph. That's its entire job, and it pairs perfectly with its sibling BV Subgraph Heading: headings tell you what a section is, dividers mark where one section ends and the next begins.

Don't underestimate the layout value. The single most repeated complaint about ComfyUI - covered at length in the ecosystem write-up - is that complex workflows are unreadable walls of boxes and wires. Visual organization tools like this are the cheap fix: a line between the "prompt building" region and the "sampling" region turns one overwhelming wall into two legible chunks. In a Subgraph/Subflow context it does the same trick inside the subgraph, and (per the README) renders on the subgraph node itself when exposed, so the parent graph gets clean section breaks too.

How it works

The backend is a stub: it takes the inputs and returns an empty string as a dummy output. The actual line is drawn by a JavaScript extension that renders the node as a thin horizontal rule at the configured thickness, padding, and opacity. It's pure presentation - no computation, no state, nothing that affects sampling.

Inputs, all cosmetic:

• thickness (INT, default 2, range 1–10) - how thick the line is, in pixels.
• padding (INT, default 10, range 0–60) - vertical padding around the line, so it doesn't hug neighboring nodes.
• alpha (FLOAT, default 0.35, range 0.05–1.0) - opacity. The default is deliberately subtle; crank it toward 1.0 if you want the section break to be unmistakable.

Output: a single _ STRING that's just an empty string - it's there because ComfyUI expects outputs, not because you'd ever wire it anywhere.

Install & gotchas

The usual pack install applies: ComfyUI Manager → BV Node Pack, or clone https://github.com/BlackVortexAI/bv_nodepack into ComfyUI/custom_nodes, restart, and hard-refresh the browser (Ctrl + F5). No models, no dependencies - it's a thin Python node plus a JS renderer.

The gotchas mirror the other UI nodes in this pack, so I'll be brief: no hard refresh means no rendered line (you'll see a plain node instead); ComfyUI's Nodes 2.0 frontend may fall back to a standard widget because it doesn't expose the rendering hooks these nodes need - the pack's own design notes say exactly that; and since it's still a real node, it adds a microscopic bit of execution time per instance. None of that should stop you. Drop one between your logical sections, leave alpha low, and let the line do the talking.