Latent CropGuides State Info

RES4LYF's latent image guide system - the README covers dual guides, masked guides, and cropped guide regions across its unsampling and img2img workflows - needs to track which parts of a latent were guided and how, as the latent moves through a chain of nodes. Latent CropGuides State Info is the node that manages that bookkeeping specifically for cropped guide regions: it reads and carries the crop-guide state attached to a latent, and can carry your conditioning alongside it so the whole guided setup - latent, positive, and negative - stays consistent as it moves through your graph.

In practice this is a supporting node rather than one you reach for on its own initiative - it belongs in workflows that are already using RES4LYF's guide-crop features (the dual-guides-with-masks style setups the README shows), sitting in the chain to keep the crop bookkeeping intact rather than doing anything visibly new to the image itself.

Inputs and outputs

• latent (LATENT) - required, the latent carrying (or about to carry) guide-crop state.
• positive and negative (CONDITIONING) - optional. If your guide setup needs the crop state to stay aligned with your conditioning, wire these through here too.
• Outputs: latent, positive, negative - passed through, with the guide-crop bookkeeping read or updated accordingly.

The shape of this node - same types in as out - makes it a mid-chain utility: it slots between whatever set up your guide crop and whatever consumes it downstream, rather than sitting at either end of a workflow.

Installing it

Comes with the full RES4LYF pack:

• ComfyUI Manager - search "RES4LYF," install, restart.
• Manual - cd ComfyUI/custom_nodes && git clone https://github.com/ClownsharkBatwing/RES4LYF, then cd RES4LYF && pip install -r requirements.txt, restart.

No extra downloads for this node.

Common issues

Guided regions look wrong or missing after adding this node. Since it's meant to sit inside an already-working guide-crop chain rather than replace anything, check that it's positioned correctly relative to the nodes that actually set up the crop in the first place - inserting it in the wrong spot can disrupt state that was already correct rather than fix anything.

Not sure whether you need this node at all. If your workflow isn't using RES4LYF's latent image guide or cropped-guide features - a straightforward txt2img or img2img run without dual guides or masking - you almost certainly don't need it. It's specifically for the guide-crop pathway the README describes, not a general-purpose latent utility.

Want to check what state is actually attached. Pair this with Latent Display State Info to inspect the bookkeeping before assuming it's correct, especially if you're debugging a chain someone else built or one you haven't touched in a while.