DJZ Zero ENH Profile Info

DJZ Zero ENH Profile Info is a utility node, not a generator. It doesn't touch a prompt and it produces no image conditioning - it prints a formatted report about a ZeroENH enhancement profile. Pick a profile from the dropdown and you get back its name, description, version, the size of every vocabulary pool, the template count, the rules, how many anti-pairing rules it has, and the total number of unique enhancements the profile can produce (both plain and scientific notation, because these combinatorial numbers get silly).

So why would you wire this into anything? You generally don't, in a finished render graph. It earns its place while you're building - specifically if you're writing custom JSON profiles. When you drop a new .json into nodes/profiles/ and restart, this node is the fastest way to verify it parsed correctly and see whether you've actually given it enough vocabulary per pool. A pool with three entries is going to repeat noticeably across seeds; the report makes that obvious at a glance instead of after a dozen boring outputs.

It's also a decent picker tool before you commit: run it over each shipped profile and you'll immediately see which one is data-rich (more entries, more combinations) versus a thin starter. That's useful because the profiles are wildly uneven - the default and cyberpunk profiles are the polished originals, while some of the community ones are more experimental.

Inputs and output

Just one input: profile, the same auto-discovered dropdown of .json files from the nodes/profiles/ folder that V2 uses. The single output, info, is a STRING containing the formatted report - wire it into any text display node (Show Text / Save Text or equivalent) to read it.

Install

Identical to the rest of the pack. ComfyUI Manager → search "ZeroENH" → install, then restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/MushroomFleet/ComfyUI-ZeroENH.git
cd ComfyUI-ZeroENH
pip install -r requirements.txt

The only real dependency is xxhash>=3.0.0, no models to fetch. It lives under DJZ-Nodes alongside V1 and V2.

One quirk worth knowing: since profile discovery happens at startup, a profile you just added won't appear in this node's dropdown (or V2's) until you restart ComfyUI. And if a profile is malformed, this node is where you'll actually see the error - it returns Error loading profile: … as its info string rather than silently falling back, which makes it the first thing to grab when a custom profile behaves wrong. That alone justifies keeping it in your node drawer while you iterate.