Location Modifier (Single)

Location Modifier is the "where" knob of ComfyUI-Variationator. Twenty hand-written environment descriptions - downtown urban, industrial district, city waterfront, open countryside, coastal, desert, mountain - each appended to your base prompt by ID. Same subject, transplanted to a different setting, without retyping anything. If you've ever wanted to see one car (or one character, or one product) in a dozen places, this is the node.

The modifiers run the full environmental range: 1–5 cover urban (downtown, industrial, suburban, commercial, parking structure), 6 is the city waterfront the README likes, 7–8 are countryside and country roads, and the higher IDs move through coastal, desert, mountain, and interior settings. Each description is a compact multi-clause phrase built to slot into a comma-joined prompt - "downtown urban setting, tall buildings, modern architecture, city atmosphere" - which is exactly the vocabulary tag-based checkpoints were trained on.

The inputs: text (base prompt), modifier_id (1–20, default 7), and preserve_base (default true). This is the dimension where preserve_base matters most, because your base prompt almost certainly already names a place. Flip it off and the node strips common location keywords - things like "city", "street", "beach", "mountain" - out of your base text before appending the new location, so you don't end up with "city street, open countryside" contradictions. Output: single STRING, modified_prompt.

Mechanically it's the same orchestration as every other dimension here: a table of 20 descriptions loaded at node init, a string append, zero Python dependencies, no model files. Install is the pack-standard story: ComfyUI Manager → search "Variationator" → install → restart, or cd ComfyUI/custom_nodes && git clone https://github.com/MushroomFleet/ComfyUI-Variationator.git. The repo's install-portable.bat references a requirements.txt that isn't shipped - skip it, nothing needs installing. Look under Prompt Orchestration.

The fun way to use this node is in a batch: take one base prompt, feed it through Location IDs 1, 6, 7, and a coastal entry, and you get a mini location-scouting session - same subject, four very different vibes. The README's day/night cycle idea works the same way here as a location cycle. The trap to avoid is stacking locations: two location modifiers in one prompt (say via chaining) just cancels out or confuses the encoder - one location per scene, always. And as with the rest of the pack, location text is a nudge, not a transport: a checkpoint that's weak on "desert" vocabulary will give you a generic outdoor scene, so treat the output as a brief and judge by the image.