LatentCompositeMaskedWithCond (🚫Deprecated)

This one node does two jobs at once: it composites a source latent into your pipe's latent using masks, and it combines or replaces the associated conditioning (prompt) text at the same time. That's a lot of behavior riding on a single box, and it's now sitting in the pack's Deprecated category - which, if you've read enough about why compound "does everything" nodes tend to fall out of favor, tracks with a pattern the wider ComfyUI community has pushed back on more than once: convenience nodes that fold multiple concerns together are genuinely handy right up until something goes wrong inside them, at which point you can't see which half misbehaved.

What it did

You'd feed it a pipe, a source_latent you wanted composited in, source_mask and destination_mask to define where the composite happens, and a text_combine list plus a text_combine_mode (add, replace, or cover) to control how the conditioning text tied to that composited region got merged into the pipe's existing prompt. In effect: paste this latent region in, and simultaneously adjust the prompt so the conditioning matches what's now in that part of the image - a regional-prompting-adjacent trick, bundled into one node rather than built from separate composite and conditioning steps.

The inputs and outputs

• pipe - the pipe carrying the destination latent and existing conditioning.
• text_combine (LIST) - the text data to merge in.
• source_latent - the latent being composited into the destination.
• source_mask / destination_mask - define the region for the composite.
• text_combine_mode - add, replace, or cover, controlling how the conditioning text merges.
• replace_text - the literal text used depending on the mode.
• Outputs: pipe (pass-through), latent (the composited result), and conditioning (a list - the merged prompt conditioning).

Why it's deprecated, and what to do instead

Bundling a latent composite and a conditioning merge into one node makes the common case fast but makes debugging genuinely hard: if your composited region looks right but the prompt influence is wrong (or vice versa), there's no way to isolate which half is misbehaving without pulling the node apart. If you're building something similar today, you'll get a clearer, more debuggable graph by doing it in two explicit steps - a standard masked latent composite, followed by whatever conditioning-combination node your current toolkit offers - even though that's more boxes on the canvas. It costs you a slightly busier graph and buys you the ability to actually see what each step is doing.

Installing it

Ships with the base pack, no separate step for a deprecated node. ComfyUI Manager: search ComfyUI Easy Use, install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/yolain/ComfyUI-Easy-Use

then install.bat on Windows or pip install -r requirements.txt, restart.

Common issues & troubleshooting

Composite region looks right but the prompt influence is wrong, or vice versa. This is exactly the debuggability problem described above - with both operations fused into one node, you can't inspect the intermediate state between the composite and the conditioning merge. If you're maintaining a workflow that already uses this node and hitting this, the pragmatic fix is to replace it with separate composite and conditioning-merge nodes so you can see each stage independently.

text_combine_mode behaves unexpectedly. add, replace, and cover are three genuinely different merge strategies, and it's easy to reach for the wrong one - replace and cover in particular sound similar but aren't interchangeable. If your merged conditioning isn't what you expected, try the other modes rather than assuming the node is broken; the mode you want depends on whether you're layering additional detail onto existing conditioning or fully overriding it for that region.

Mask mismatch between source and destination. If source_mask and destination_mask don't correspond to compatible regions (wildly different shapes or areas), the composite can look distorted or misplaced. Preview both masks independently before wiring them in if the result looks off.