LC Any Empty Int

The integer member of the LC123 "Any Empty" family. You wire a pile of optional upstream sockets into it, and it tells you whether any of them came up empty by emitting one of two integers you define: empty (default 0) when any plugged source is empty, muted, or bypassed, and not_empty (default 1) when every plugged source delivered a live value. One output, type INT, named int.

The niche this fills in real workflows: integer selectors and indices. A 0/1 pair is exactly what a switch or index node wants to route somewhere - feed it into an LC Any Index Switch's INDEX or an LC Combo Selector and the graph can flip between a fallback and a primary path on its own. You can also treat the output as a counter or gate ("no images upstream → emit 0, so the batch step skips"), or invert the meaning by setting empty to 1 and not_empty to 0 if you'd rather have "live" be the nonzero case. It's a plumbing node in the truest sense - it makes the workflow's state (is anything broken upstream?) available as data the rest of the graph can branch on.

Mechanically it's the same detector as its siblings, LC Any Empty Bool and LC Any Empty Float, and knowing one means knowing all three. Up to 20 autogrow sockets, any_01–any_20, all type *, so models, latents, images, strings - anything plugs in. Two rules: only plugged sockets are tested (empty sockets are "not part of the test," not "empty input"), and "empty" is a broad church - None, whitespace-only strings, empty tensors, empty lists and dicts, plus any source node that's muted or bypassed in the workflow graph. The Bool version returns a truth value, the Float returns a decimal, this one returns a whole number in the ±2^31 range (widget min/max from the node's schema).

The inputs you set are empty and not_empty themselves. They look like outputs until you realize they're the constants to emit - that's the single most common confusion across all three nodes. Set them once and forget them; the values ride along with whichever state the test finds.

Same two gotchas as the rest of the family, worth restating because they bite here too. Wire up nothing and the node returns the empty value - if you built a detector and forgot to connect anything, it quietly reports "empty" forever. And a bypassed upstream source counts as empty, because LC123's Bypasser/Mute nodes work by setting the workflow modes this detector watches for. Bypassing the node that feeds a socket reads as a dead socket.

If you only need one of the three, pick by what you're feeding: a switch/index selector wants this INT one, an opacity or strength knob wants the Float, a plain condition wants the Bool. They share one installation - ComfyUI Manager → search "LC123" (repo ComfyUI_LC123_nodes), or clone https://github.com/lonecatone23/ComfyUI_LC123_nodes into ComfyUI/custom_nodes and restart. No extra pip dependencies, no models to fetch. If you unzipped a release into an existing clone, mind the nested-folder trap (__init__.py must sit directly in the pack folder), and on hosted Comfy platforms the pack needs pre-installing by the host.