WanModelTypeSelector

This is the most boring node in the pack, and that's exactly the point. It's a pass-through: you pick a Wan model type from a dropdown - Wan 480p, Wan 720p, or Wan 2.2 - and it outputs that choice as a value other nodes can read. It holds a setting in one place so the rest of your graph can refer to it by wire instead of by retyping the same dropdown in five different nodes.

That's the value-node pattern from the plumbing playbook: one authoritative source, fanned out to many consumers. When you're building a Wan workflow with several nodes that all need to know the model tier - a resolution calculator, a sampler, a LoRA stack - this lets you change the model once and have every downstream node pick it up. Change "Wan 720p" to "Wan 2.2" in one place, and the whole chain re-targets itself instead of you hunting through every node's widget.

How it works

The mechanism is about as deep as a puddle: return (model_type,). The dropdown's value is passed straight through to the output. The clever bit is the socket typing - the output is declared as * (the wildcard), so it can plug into any node in this pack (or others) that accepts a string-ish value, while staying loosely typed enough not to fight the ecosystem's conventions.

What it doesn't do: load a model, check your checkpoints folder, or validate that you actually have that model downloaded. It's purely a named wire - a labeled value that travels down the graph.

The inputs that matter

• model_type - the dropdown. The three choices correspond to the Wan generations this pack is built around: the 480p and 720p tiers from Wan 2.1, and Wan 2.2 (the last open-weight Wan - everything newer is API-only).

One output: Model Type, wildcard-typed.

Installing it

Part of ComfyUI-Przewodo-Utils. ComfyUI Manager → search the pack, or:

cd ComfyUI/custom_nodes
git clone https://github.com/przewodo/ComfyUI-Przewodo-Utils.git

Restart. Zero dependencies.

Where people get tripped up

The one thing to internalize: this node's output is meaningful only to nodes that understand it. Because the type is *, ComfyUI won't stop you from plugging it into something random, but a sampler that expects a real model won't accept "Wan 720p" as a model. The intended use is feeding it to this pack's own model-aware nodes (the resolution calculator, the sampler, the mode selector) - the ones that treat the model type as configuration rather than as weights.

And if you're honest about it, a single-node workflow doesn't need this at all. It earns its place when your Wan graph grows to a dozen nodes that all need to know the tier. If you're not there yet, you're not missing anything - but the day you are, this is the kind of plumbing that prevents "I changed the resolution node but forgot the sampler's dropdown" bugs.