🌀 BV Regional Debug

Regional prompting fails in two ways: visibly (subjects merged, attributes bled) and invisibly (the document itself isn't what you think it is). The second kind is the nasty one - you spend an hour tuning strength sliders on a layout that was never what you intended. BV Regional Debug is the node that makes the invisible visible. It takes any BV_REGIONAL document and hands back the canonical JSON, a human-readable summary, and the document's stable ID.

It's the "am I crazy or is this document wrong" node. It's also the easiest on-ramp to understanding how the pack thinks about documents, because you can see the whole contract laid out.

How it works

One required input, regional (the BV_REGIONAL output from BV Regional Prompt or anywhere else a document flows). One optional input, pretty (default true) - toggles pretty-printed JSON vs. compact. Three outputs:

• regional_json (STRING) - the full canonical document, pretty-printed by default. This is ground truth: canvas, global/background prompt sources, every region with its geometry, strength, and overlap mode.
• summary (STRING) - a condensed read of what's in the document, so you can sanity-check "did my regions actually save?" without wading through JSON.
• document_id (STRING) - the document's stable UUID.

That document_id is more useful than it looks. The image feedback nodes (BV Regional Preview Send / Save Send) require a document ID to target the right editor, and the editor keys its UI state per document. If you're plumbing multiple documents through one workflow - or debugging why a preview sent to the "wrong" editor - this output is how you confirm which document is which. IDs are stable across editing, so the ID you see in Debug is the ID the editor uses.

The debugging loop

When a regional render misbehaves, wire Debug in and check three things. First, summary - did every region you drew actually persist, or did a geometry layer fail to save? Second, the region prompts in the JSON: are the right prompts on the right regions? It's embarrassing how often a misplaced paste puts "red dress" on the left character. Third, the overlap mode: the pack currently executes joint overlap, and if you're expecting hard exclusivity, that mismatch is a conceptual bug before it's a rendering bug.

Install

Search BV Node Pack in ComfyUI Manager, or:

cd ComfyUI/custom_nodes
git clone https://github.com/BlackVortexAI/bv_nodepack.git

Restart, hard-refresh with Ctrl + F5. No dependencies.

The honest take

It's not a node you keep in every workflow - it's the node you drop in when something's off and the editor's masks look right anyway. Debug output is the closest thing this pack has to a source of truth you can actually read, and for a system built on "stable IDs and canonical documents," that's the right tool to reach for when intuition stops working.