PC: LoRA Hooks From Text (non-lazy)

HOOKS is ComfyUI's own native type for schedulable model patches - the same type its built-in CreateHookLora and hook-apply nodes produce and consume. Prompt Control's LoRA scheduling is built on exactly that system, and PCLoraHooksFromText is the node that gives you the raw HOOKS object directly, parsed straight from text, instead of having Prompt Control apply it to a model for you automatically.

What "non-lazy" means here

The display name spells it out: "(non-lazy)." Prompt Control's usual approach - the one behind PCLazyLoraLoader - is lazy: it defers building the actual node graph so ComfyUI's caching can skip re-encoding parts of the schedule that haven't changed. This node skips that. It parses your text and builds the HOOKS object eagerly, in one pass, no deferred graph generation. Simpler and more predictable, at the cost of the partial-recompute caching benefit the lazy path is built around.

What it's for

According to the pack's own description of the closely related PCLazyLoraLoaderAdvanced node, its hook output is provided "in case you want to use it elsewhere" rather than applied automatically - the assumption being you might want to feed those hooks into ComfyUI's own native hook-application machinery yourself, combine them with hooks from somewhere else entirely, or apply them at a different point in the graph than Prompt Control would by default. PCLoraHooksFromText gives you that same raw material, without the lazy machinery wrapped around it.

The input and output

• text (required, multiline) - your prompt text with LoRA scheduling syntax in it.

Output: a HOOKS object - the set of hooks Prompt Control built from parsing that text.

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.

Requires ComfyUI v0.8.0+.

Common issues & troubleshooting

You're not sure what to do with a raw HOOKS output. If you don't have a specific reason to want the hooks exposed separately - combining with other hooks, applying them somewhere non-standard - you probably don't need this node. PCLazyLoraLoader or ScheduleToModel apply hooks to a model for you directly and are the simpler path for the common case.

The category says "v2," and that's confusing next to a "v3" pack. That's a leftover namespace from a previous generation of the node schema, kept for compatibility rather than actively promoted - similar in spirit to how LoRAScheduler is kept under promptcontrol/old. It still works; it's just not where new development attention goes.

Caching doesn't behave like the lazy nodes. That's the whole trade-off of "non-lazy" - you lose the benefit where changing one scheduled value avoids re-encoding unrelated parts. If caching efficiency matters to your workflow more than having the raw hooks exposed, the lazy nodes are the better fit.