CR LoRA List (Legacy)

This one's filed under Legacy in the current node menu, and its job is narrow: build a small named list of LoRAs - up to three at a time, each with its own alias, model strength, and CLIP strength - that other Comfyroll nodes can reference by name. It's the LoRA-side counterpart to CR Model List, and its main consumer in this pack is CR Load Scheduled LoRAs, which uses the aliases you set here to look up which LoRA belongs to which point in an animation schedule.

How it works

Each of the three slots takes a lora_nameN (picked from your installed LoRAs), an aliasN (a plain-text name you invent - this is what a scheduler node's schedule_alias field matches against), and separate model_strength_N / clip_strength_N weights. An optional lora_list input lets you chain multiple CR LoRA List nodes together if three slots isn't enough - feed one node's output into the next one's lora_list input to build a longer combined list.

The output is a single LORA_LIST - this node doesn't apply anything to a model itself, it just builds the catalog that a scheduler or apply node further downstream reads from.

Inputs and outputs that matter

• lora_nameN, aliasN, model_strength_N, clip_strength_N for N = 1, 2, 3.
• Optional lora_list - chain another CR LoRA List node's output in here to extend past three entries.
• Outputs: LORA_LIST, show_text.

How to install it

ComfyUI Manager: search "Comfyroll Studio", install, restart. Manual: cd ComfyUI/custom_nodes && git clone https://github.com/Suzie1/ComfyUI_Comfyroll_CustomNodes.git, restart. Your LoRA files still need to live in models/loras - this node just references what's already there.

Common issues

Being tagged Legacy in the node menu is worth taking at face value: if you just need to stack a few LoRAs onto a model with individual on/off control, CR LoRA Stack (in this same pack's Essential section) does that more directly and doesn't require an alias-driven schedule to be useful. Reach for CR LoRA List specifically when you're feeding CR Load Scheduled LoRAs - that's the one place the alias system actually earns its keep.

The alias fields are free text with no validation against what a scheduler node expects - a typo in aliasN here versus schedule_alias on the consuming node means "Schedule" mode quietly finds nothing rather than erroring. Match them exactly, including case. And if the node's missing from the search menu, it's the standard Comfyroll pack-wide caveat: a broken import elsewhere in this large pack can take unrelated nodes down with it - check the console log before troubleshooting this node specifically.