Easy Utility (Koolook)

Easy Utility is a one-trick node, and the trick is padding: it turns an integer into a zero-padded string. 1 becomes 001. That's the whole job. Which raises the question - why does this exist?

Because file naming. When your VFX pipeline writes v001, v002, v010, it needs the version token to be a fixed width, or v2 sorts before v10 and your whole versioned output structure falls apart. The pack's own docs put it plainly: this node exists to drive the version token into EasyAIPipeline and Easy_VideoCombine. You hand it a number, it hands back 001, and a downstream consumer adds the v to make v001. The prefix field exists if you want the v baked in yourself, but it defaults to empty for exactly that reason - keep the padding separate and let the pipeline add the letters.

The inputs

Four widgets, three of which you'll actually touch:

• mode - currently a dropdown with exactly one option, int_to_padded_string. The pack shipped the dropdown from day one on purpose: when they add more conversion modes later, saved workflows won't need rewiring, the new options just appear. Don't be surprised when this grows.
• int_value - the number to convert (0 to 99999).
• pad_width - the minimum digit count. 1 at width 3 → 001. Width 0 is allowed and just means "no padding."
• prefix - optional text prepended. Leave empty for EasyAIPipeline version inputs.

Output is a single string. Feed it into the version field of EasyAIPipeline (convert that field to an input to wire it), or into any filename builder that wants a consistent width.

Install

It ships in the ComfyUI-Koolook pack. ComfyUI Manager → Install Custom Nodes → Git URL:

https://github.com/malkuthro/ComfyUI-Koolook.git

Or:

cd ComfyUI/custom_nodes
git clone https://github.com/malkuthro/ComfyUI-Koolook.git

Restart, and it's under Koolook/Utility. No models, no dependencies - it's a string format operation. And the pack's standing warning: install once. If you already installed via Manager (folder custom_nodes/koolook/), don't also git clone a second copy. Two parallel installs load on every boot, double-register nodes, and corrupt the workflow store until you delete one.

Common issues

There's not much to break here, which is the point. The one real gotcha: zero-padding vs. width. pad_width is a minimum - int_value 123 at width 3 stays 123, not 0123. If you're seeing strings longer than you expected, that's why. And remember the output has no v prefix; if your downstream expects v001, either set prefix to v or let the consumer add it, but don't do both.