🐰 McBoaty Tile Prompter - v6 /m

The whole pitch of McBoaty is "upscale with minimal modification," and the Tile Prompter is the tool that makes minimal a choice you can make per-tile. When a tiled upscale runs, most tiles come out great and one comes out wrong - a face smeared, a pattern repeated, a bit of the image the model decided to reinterpret. The v5 Tile Prompter let you edit 64 separate tile prompt boxes by hand. The v6 version flips the model: instead of one field per tile, you write one set of changes and say which tiles they apply to.

What it does

It sits between the Configurator and the Refiner:

Tiler → Configurator → [Tile Prompter] → Refiner

You feed it the McPrompty Pipe that came out of the Configurator (or out of an earlier TilePrompter pass - you can chain them). Then you set:

• tiles_to_process - the selector. Blank means all tiles; otherwise comma-separated indices (1,2,5) or ranges (1-4). Same syntax the v5 Refiner uses.
• positive / negative - the prompts you want to override the Configurator's per-tile prompts with, on the selected tiles. Leave blank to keep what's already there.
• refresh_prompts - a boolean that forces the tile prompts to regenerate (it's a button-style toggle, "Refreshing..." while it runs).
• cfg / denoise - override the sampling for the selected tiles. This is the real power move: one tile's prompt is fine but it's overcooked, so you drop just that tile's denoise.
• strength / start_percent / end_percent - per-tile ControlNet strength. Same idea, for the canny anchoring.

The output is a McPrompty Pipe with the modified per-tile attributes baked in, ready for the Refiner.

Why this matters

In the v5 era, fixing a bad tile meant editing one of up to 64 text boxes and re-running. The v6 design acknowledges what you actually do: you run the upscale, look at the result, and re-run only the problem tiles with a nudged prompt or denoise. That's the workflow the README describes: push denoise to 0.76 on the first pass, then "fine-tune the prompt and denoise for the tiles which went too wild and process the tiles you want again through a second refiner pass."

The per-tile selectors (tiles_to_process, and the strength/percent trio) being in the required list also means you can leave them at defaults and just change prompts - the node skips attributes you leave untouched, so it's non-destructive by design.

Install & the caveat

Same pack install as everything else:

cd ComfyUI/custom_nodes
git clone https://github.com/MaraScott/ComfyUI_MaraScott_Nodes

Restart or use ComfyUI Manager → "MaraScott". No extra models for this node itself - it's pure prompt-pipe surgery.

The pack-level warning applies double here: the README says v6 is broken (issue #187), and the Tile Prompter is the node most likely to have lost a feature in the restructure - v5's version had 64 individual per-tile text boxes plus a requeue input, which some people genuinely prefer for fine control. If the v6 selector approach fights you, the v5 Tile Prompter + v5 Refiner combo is the stable, fully-featured path. Try v6 first if you want the cleaner graph, but know the escape hatch exists.