CR Model List (Legacy)

The checkpoint-side counterpart to CR LoRA List: build a small named list of up to five checkpoints, each with an alias, so other Comfyroll nodes can reference them by name. Like its LoRA counterpart, it's filed under Legacy in the current node menu, and its main job in this pack is feeding CR Load Scheduled Models - the alias you set here is what that node's schedule_alias field matches against when picking a checkpoint for a given frame.

How it works

Five slots, each with a ckpt_nameN (pick a checkpoint from models/checkpoints) and an aliasN (a plain-text name you invent for it - no strengths or weights here, since there's nothing to weight; a checkpoint is either the active one for a given frame or it isn't). An optional model_list input lets you chain another CR Model List node in if five isn't enough.

Output is a single MODEL_LIST - again, this node doesn't load or activate anything by itself, it just builds the catalog a scheduler node reads from.

Inputs and outputs that matter

• ckpt_nameN, aliasN for N = 1 through 5.
• Optional model_list - chain another CR Model List node's output to extend past five entries.
• Outputs: MODEL_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 checkpoints need to already be in ComfyUI/models/checkpoints - this just references what's already installed.

Common issues

This node is basically inert on its own - it doesn't load a checkpoint, apply anything, or change your graph's output by itself. If you've built one expecting to see some effect, remember it only matters once its MODEL_LIST output actually reaches CR Load Scheduled Models's model_list input with mode set to Schedule.

Aliases here are free text with no cross-validation against what the scheduler expects - a mismatched or misspelled alias between this node and schedule_alias on the consumer means the schedule quietly fails to find that checkpoint rather than throwing a clear error. Match them exactly.

Given it's tagged Legacy, treat this as the node you use specifically when you need named, schedulable checkpoints for an animation - if you just want to pick between two checkpoints once, CR Model Input Switch (in this same batch) is the more direct tool. And as always, a missing node in the search menu points to a pack-wide import failure elsewhere in this large pack, not necessarily a problem with this node itself.