LoRA Preset Selector

The LoRA Preset Selector is the node that makes "which LoRAs am I using today" a dropdown choice instead of a graph-editing decision. It reads your saved presets, lets you pick one, and hands the whole stack forward as a list - usually straight into the LoRA Preset List Loader & Encoder, which does the actual applying. Keep a selector per stack you care about, wire them all into one list loader, and switching between "sci-fi set" and "portrait set" is a couple of clicks on the graph.

How it works

The selector maintains a running list of preset file paths. Each time it runs, it appends the preset you've selected to that list - skipping it if it's already there - and outputs the result as lora_list. Chain selectors together by feeding one's lora_list into the next's lora_list input, and the list grows as it passes through: selector A picks a base style, selector B adds a character, and the loader at the end applies them all in order.

A couple of details worth knowing:

• bypass is the kill switch. Flip it on and the selector passes the list through untouched - the preset you picked isn't added. This is how you leave a stack in the graph but switch it off without deleting anything.
• subfolder filters the preset dropdown. Presets live in your loras folder, and subfolders there become options here. "root" shows the top-level presets only.
• refresh rescans the disk. Toggle it and the node re-scans your loras folder, so a preset you just saved with the Saver appears without restarting. The pack's little JS extension also lets the subfolder dropdown talk to the preset dropdown over the pack's /lora_presets web endpoints.
• The weight widget is a trap. It exists on the node, but in the current source it's accepted and never used - the list loader reads strengths from the preset files themselves. Set weights in the Saver instead.

The inputs and outputs

Required: subfolder, preset (both dropdowns), weight (dead, as above), bypass, and refresh. Optional: lora_list for chaining. The single output is lora_list, a LIST of preset paths. Wire it to the list loader's preset_list, or stash it in a dict_bus's list slot and let the loader pull it from there.

Installing it

Same pack, same easy setup:

cd ComfyUI/custom_nodes
git clone https://github.com/JEONG-JIWOO/ComfyUI_Eugene_Nodes

Restart ComfyUI (or install via ComfyUI Manager, search "Eugene Nodes"). No pip requirements, no models to download.

Where people get burned

The dropdown is only as good as what the pack finds on disk, so the recurring frustration is a preset that should exist but doesn't show up - usually because it wasn't saved into the loras folder, or the refresh wasn't hit. If a preset disappears from the list, it's almost always that the file moved or was renamed.

And keep the bypass semantics straight: bypassing means "don't add this preset," not "remove it from the list." The list only grows - if you want a shorter stack, rearrange or drop the selector entirely. That, plus the fact that order is application order, is the whole game.