PCScheduleSettings

This one's pure configuration - it doesn't touch your prompt text at all. PCScheduleSettings bundles up a handful of numbers a Prompt Control schedule needs to resolve correctly (how many steps you're running, what resolution to rasterize masks at, and SDXL's micro-conditioning values) into a single SCHEDULE_SETTINGS object, which you then hand to PCApplySettings to attach to a schedule.

You will not need most of these fields most of the time. Every one of them has a default, and if you never wire this node in at all, Prompt Control just uses its own internal defaults instead. This node exists for the moment you do need to override something.

The fields, and which ones you'll actually touch

• steps (default 0) - the total step count for the run. Prompt Control's [a:b:0.3]-style scheduling and the at fraction used elsewhere in the pack resolve against a step count somewhere; if you're getting scheduling that doesn't line up with your actual sampler steps, this is the field to set explicitly rather than trust an assumed default.
• mask_width / mask_height (default 512 each) - the resolution masks get rasterized at for regional prompting. If your masks look soft or misaligned relative to your actual output size, check this against your real resolution.
• sdxl_width / sdxl_height, sdxl_target_w / sdxl_target_h, sdxl_crop_w / sdxl_crop_h (defaults 1024/1024/1024/1024/0/0) - the same "original size / target size / crop" numbers ComfyUI's own CLIPTextEncodeSDXL exposes. SDXL was trained conditioned on these values, so setting them to match your actual generation resolution is a small, real quality knob - not a decorative setting.

How to install it

• ComfyUI Manager - search "ComfyUI Prompt Control", install, restart.
• Manual - cd ComfyUI/custom_nodes && git clone https://github.com/asagi4/comfyui-prompt-control, restart ComfyUI.

Needs ComfyUI v0.8.0 or newer, like the rest of the v3 line.

Common issues & troubleshooting

You're not on SDXL and this node feels irrelevant. It mostly is, for you. The sdxl_* fields are harmless no-ops on other model families - leave them at their defaults and move on. There's nothing here that hurts a Flux or SD 1.5 workflow.

Your regional-prompting masks look blurry or offset. Check mask_width/mask_height against the resolution you're actually generating at before assuming your mask image itself is wrong. A 512×512 default rasterization applied to a 1536×1536 generation is a common source of "why is my mask fuzzy."

You wired this in but nothing changed. Confirm you also ran the output through PCApplySettings - PCScheduleSettings only builds the settings bundle, it doesn't attach it to anything by itself. Building the settings and applying them are deliberately two separate steps, so you can build one settings object and reuse it across several schedules.