Modifier Info

Every single-modifier node in this pack is a number from 1 to 20, and numbers are useless without the lookup. That's what Modifier Info is for: punch in an ID and it tells you what that modifier actually says - its full description, its DRY/WET category, and its search tags. It's a documentation tool that happens to live in the node graph, which means you can browse it without tabbing out to the README.

How it works is dead simple. The node instantiates the same PromptOrchestrator the modifier nodes use, then looks up your modifier_id in that orchestrator's modifier table and returns three strings: description (the exact text that gets appended to your prompt), category (dry, wet, or unknown if the ID is invalid), and tags (the comma-joined keywords used for filtering and discovery, like golden-hour, warm, side-light, clear). There's no processing, no state - it's a read-only dictionary access.

Inputs and outputs: one required input, modifier_id (1–20, defaults to 7), and three STRING outputs you can route anywhere - most people just add a text display node or route description straight into their prompt. Category is only meaningful on the dimensions that use DRY/WET at all (lighting, seasonal, weather), so don't read much into it elsewhere.

One honest quirk worth knowing, because it's not obvious from the UI: the underlying lookup only reads the lighting modifier table. The modifier_id space is 1–20 in every dimension, and this node will happily report a valid description for any ID in that range - but those descriptions are all lighting modifiers. If you want the description for, say, mood modifier 13 (Luxurious Elegance), this node won't show it. That's a limitation of the pack's architecture, not something you're doing wrong.

Install is the same zero-dependency story as the whole pack - pure Python, no models, no requirements to pip-install. ComfyUI Manager → search "Variationator" → install → restart, or cd ComfyUI/custom_nodes && git clone https://github.com/MushroomFleet/ComfyUI-Variationator.git. It shows up under Prompt Orchestration alongside its 19 siblings.

Honestly, the best way to use this node is inside a test harness: wire a couple of modifier nodes plus a Modifier Info into one workflow, and you can A/B descriptions side by side without remembering anything. The README points you here as the "can't find the right modifier" answer, and it does serve that role - for lighting at least. If you're deep into mood or camera dimensions and want the real reference, the pack's MODIFIER_REFERENCE.md is the source of truth this node can't fully replace.