TTP Smart Tile Composite Override

Smart Tile 2.0's automatic tile ranking (TTP Smart Tile Semantic Rank) does a decent job of guessing which tiles should sit on top and how they should composite, but it's a guess - and this node is how you correct it by hand for specific tiles, before the workflow reaches TTP Smart Tile Assemble. Per the README's own Core Nodes summary, it lets you "filter selected tiles and set composite mode, replace shape, layer, priority, occlusion priority, blend, and importance before assembly."

How you pick which tiles to affect. selector_type gives you ten ways to target tiles - index (the default, e.g. T3), name, label, prompt_tag, source, semantic_category, semantic_role (the latter two only meaningful after Semantic Rank has classified your tiles), prompt_contains, regex, or all. Whatever you pick, selector is the actual match string. unmatched_mode decides what happens to everything else: keep (default) leaves non-matching tiles alone, drop_unmatched removes them from the set entirely - genuinely useful for edit-style workflows where you only want a handful of tiles to go through the sampler at all, and want Assemble to fall back on source_image for everything you didn't touch.

The README's own worked example is the clearest way to understand this node: selector_type=index, selector=T3, composite_mode=replace_tile, replace_tile_shape=mask_first, occlusion_priority_mode=max - described as putting the selected tile above lower layers and making it hard-replace the canvas. mask_first uses the tile's object mask when one exists and hardens its interior (similar to an inpaint stitch); tile_box_first ignores any mask and replaces the entire rectangular tile box regardless.

The repeating pattern worth learning once, since it covers five separate inputs. layer, priority, occlusion_priority, blend, and importance each come with a matching _mode selector using the same five options: keep (leave the tile's existing value untouched - the safe default on most of them), set (hard overwrite with the value you specify), add (increment by the value), max/min (only move the stat if the new value would push it up or down respectively). Once you recognize that pattern, you don't have to memorize five different controls - you're always deciding "should this override completely replace, nudge, or just clamp the existing value."

Outputs: tile_set (the modified set, feeding forward to the rest of the loop or straight to Assemble), composite_json (the override you just applied, in case you want to inspect or reuse it), and summary (a text readout of what changed).

Install. ComfyUI Manager, search "Comfyui_TTP_Toolset", or cd ComfyUI/custom_nodes && git clone https://github.com/TTPlanetPig/Comfyui_TTP_Toolset, then restart. No models or heavy dependencies - this node only manipulates the tile_set data structure.

Common issues. There's no dedicated troubleshooting entry for this exact node in the README, and it has no measurable search or community traffic yet, so treat the following as informed practice rather than sourced fixes. If a face or detail tile is still getting buried under a larger tile after Semantic Rank ran, this is the node to reach for directly - target that specific tile with selector_type=index or label, and push its priority_mode/layer_mode to set or max rather than relying on Semantic Rank's automatic classification to have gotten it right. And remember this node only edits metadata on the tile_set - it doesn't touch pixels or re-run sampling, so if your change isn't visible in the final image, check that you actually reconnected this node's tile_set output into the rest of the chain rather than leaving the original, unmodified set still flowing to Assemble.