Scenario Selector

Scenario Selector is the plainest node in this pack, and that's its whole appeal. It gives you a dropdown of .txt files from a folder, and when you pick one it outputs that file's text. Nothing else. No LoRA logic, no prompt assembly, no LLM - just a reusable library of scene descriptions you can swap from the UI instead of editing strings in the graph.

The point of it is file organization. Once your scenarios become text files on disk, the graph stops being a museum of hard-coded strings. "Night market", "Forest walk", "Rooftop at dusk" become entries in a dropdown, and switching scenes is a click instead of a copy-paste. If you've ever rebuilt a workflow because the prompt lived in three different text nodes, you already know why this exists.

How it works

Drop .txt files anywhere under:

custom_nodes/vsaan212_workflow_utilities/scenarioselector/ScenarioFiles/

subfolders allowed, scanned recursively. The dropdown lists relative paths without the .txt extension - so sets/city/night_market.txt shows up as sets/city/night_market. Select one, and the node reads the file (normalizing \r\n to \n along the way) and returns two outputs:

• text - the full file contents, ready to wire into a prompt builder, another node's string input, or LazyPrompt's scene_context.
• preview - a short status string like Loaded: sets/city/night_market.txt, handy for sanity-checking which file actually loaded.

Your scene files can be anything - plain prose, tag lists, or the pack's tagged [LoraHighA] format if you're feeding them into Text Split. The node doesn't care about the format; it's a dumb, reliable text reader.

Install and gotchas

Install the pack once: ComfyUI Manager → search vsaan212/Vsaan212-workflow-utilities, or clone into custom_nodes and restart. The ScenarioFiles folder is created automatically on first load. No dependencies beyond the standard library.

Two things to know:

• New file not showing in the dropdown? Press R in ComfyUI (or recreate the node) to rescan. The pack refreshes the list when the node is created, but not continuously.
• Same filename in two subfolders? The dropdown shows relative paths, so two night_market.txt files in different folders both appear - pick the full relative path so you know which one you got.

One real footgun worth flagging: this node's folder is not the same one Lazy-subject-and-scene-automation reads. That node uses lazy_subject_scene_automation/ScenarioFiles/. If you build scenario files for the automation node and wonder why the standalone selector's dropdown is empty, that's why - copy or symlink the files into both folders.

It's a small node, but it's the honest workhorse of the pack: a scene library that lives on disk, a dropdown to pick from it, and text out. Sometimes that's all a workflow needs.