h4 - Discombobulator

Let's be direct: H4_Discombobulator does nothing. Backend-wise, literally nothing - its Python method is a noop, and the source says so with a smiley. What it's for is being an easter egg: when it sits on the graph, it's an anchor for a JS glitch engine that rewrites ComfyUI's notifications into binary, leet speak, base64, or "spaced out" glitch text. Pick your flavor, run something, and watch your error toasts come back as b1n4ry nonsense. It's h4's sense of humor shipped as a node, buried in a category called h4_Live/Stealth/Legacy with the description "(b'.')b / t('.'t)".

You should treat it exactly as seriously as the author does. It is not a utility. It won't improve your images, your seeds, or your sampling. It's a personality artifact from a pack that is, by the author's own framing, a "Massive project" built partly because "we got mad at the canvas one night and chose violence." If you find that charming, it's a free laugh; if you find it noise, you're not missing anything.

The one setting

• discombobulation_choice - 1337 (leet speak), b1n4ry, B64 (base64), or V 0 1 D (spaced-out glitch text). That's the entire input surface. No outputs at all - the node's output list is empty.

The caveat that actually matters

Because it's a frontend/JS trick, it's the kind of feature that's most fragile in exactly the environment you might be using: ComfyUI Desktop Edition. The README warns that h4_Live works in CDE but its "tactical flair, HUD overlays, and advanced terminal visualizers may be degraded or disabled by CDE's sandboxed rendering engine." A glitch-text notification interceptor is precisely the kind of thing that sandbox kills. If you add it and nothing changes, that's not you doing it wrong - it's the environment refusing to be possessed.

Installing

Same as the pack: ComfyUI Manager → search "h4_Live", or:

cd ComfyUI/custom_nodes
git clone https://github.com/m3rr/h4_Live

restart. Zero dependencies. The node is marked legacy/stealth, so don't be surprised if it eventually gets shelved entirely - the pack is under active development and pruning old toys is exactly what "Legacy" in a category name implies.

The honest verdict: keep it on your canvas if you're building a weird, personality-driven workflow and want a laugh mid-run. Otherwise, skip it. This is seasoning, not nutrition - and it's refreshing to see a node pack that admits it.