🎨 OVERTLI Style Stack (7)

The Overtli Studio Suite loves a style preset. Every generation node in the pack has three style_preset_1..3 dropdowns, and each dropdown holds a few hundred curated entries - "Photograph (Real Life)", "Cinematic Still", "Anime Illustration", "Line Art (Clean)", on and on through categories like 3D/CGI, Concept Art, and the rest. Pick one and it gets layered into your prompt. But three slots is a real limit when your look is "photoreal subject, cinematic light, 80s film grain" and you want each layer to stay a separate toggle.

That's the gap GZ_StyleStackNode fills. It's the "Style Stack (7)" in the node menu: seven style_preset_1 through style_preset_7 inputs - the same curated dropdowns - combined into a single composed layer and handed out one wire.

What it actually is

A pure text utility. It doesn't call anything, doesn't fetch models, doesn't need keys. You choose up to seven styles from the same library the other nodes use, and the node concatenates them into one STRING and returns it on the additional_styles output. That naming is deliberate: the generation nodes' additional_styles input is socket-first (built to accept a wire, not just typed text) and is designed to chain straight from this node.

So the composition recipe across the pack becomes: the node with style_preset_1..3 built in, plus additional_styles fed by a Style Stack, for up to ten layered style slots in total. The suite's README is explicit about the ordering - custom instructions, then the mode preset, then your raw prompt, then the style layers - so the stack lands as the final seasoning rather than competing with your instruction.

Why you'd reach for it

Two honest use cases. The first is reusable looks: keep a Style Stack node per aesthetic ("my default cinematic stack", "client A's product look") and drag in whichever one a workflow needs, without hunting through dropdowns inside a big generation node. The second is systematic A/B testing - because each style stays in its own slot, flipping one layer off and running again is trivial, which is a nicer workflow than fighting three combined dropdowns for a four-part style.

Install and the one gotcha

Installs with the pack: search "Overtli" in ComfyUI Manager, or git clone https://github.com/OvertliDS/overtli-studio-suite into custom_nodes, pip install -r requirements.txt, restart. Nothing else to download - remember, there are no models behind this one.

The gotcha is knowing it's Overtli-shaped output. additional_styles is composed as one text blob that Overtli's own nodes understand as a style layer. Feeding it into a random third-party node's text input generally still works (it's just text), but the clean semantics - "this is a style layer, don't treat it as the whole prompt" - exist inside this suite's nodes. Also note that all seven slots default to Off except style_preset_1, which ships set to "Photograph (Real Life)". That default is a good look, but it means a fresh Style Stack is not empty - if you wire one in and your output suddenly gets more realistic than you expected, check slot one before you blame the sampler.