Multiply Integer (WLSH)

There's not much mystery here: two integer inputs go in, one multiplied integer comes out. number × multiplier = INT. That's the entire node, and honestly that's fine - not every node needs a backstory, sometimes you just need integer math without leaving the graph to do it in your head.

Where this actually earns a spot in a workflow is anywhere you want one number to derive from another instead of typing both by hand. The README's own example is a common one: if you're generating at a base resolution and want a "quick resolution multiplier" relationship between a working size and a target size - say your SDXL height needs to track some multiple of a base value for a hi-res pass - wiring a multiply node in means changing the base number automatically updates everything downstream instead of you manually recalculating and retyping. It's the same reason spreadsheet formulas beat retyping numbers: one source of truth, computed everywhere it's needed.

Inputs: number (default 2, range 1–10000) is your base value. multiplier (default 2, same range) is what you're scaling it by. Both are plain integer widgets, so you can type a value directly or wire either one in from another node - a primitive, a counter, whatever's producing the number upstream. Output: a single INT, the product.

Wire that INT into anything expecting an integer - width/height fields on a latent node, a batch size, a step count, a counter feeding into a filename. It's generic on purpose; the node has no opinion about what the number means, it just multiplies.

Installing it: the whole pack comes as one install, so grab it through ComfyUI Manager by searching "wlsh_nodes" or "WLSH Nodes", or clone it manually:

cd ComfyUI/custom_nodes
git clone https://github.com/wallish77/wlsh_nodes

Restart ComfyUI afterward. No model downloads, no extra Python dependencies - it's a pure math utility, so once the pack loads you're set.

Troubleshooting: genuinely, there's little to go wrong. The only thing worth flagging is the range cap - both inputs top out at 10000, so if you're chaining multiple multiply nodes together and expecting a much larger number downstream, you'll hit the ceiling and get clamped rather than an error, which can look like the node "isn't working" when it's actually just capping the value. If your output looks wrong, check that you haven't got number and multiplier backwards from what you meant - multiplication is commutative so the math is fine either way, but if you were relying on one specific field to hold your "base" for readability, swapping them can make the graph confusing to read later even though the result doesn't change.