Int To Number (mtb)

This is a pure glue node, and it's honest about it - the description literally calls it an "addon for the WAS Suite." Its whole job is to take a normal ComfyUI INT and convert it into the NUMBER type that WAS Node Suite uses. If you don't run WAS Suite, you will never need this node, and that's fine. If you do, it's the little adapter that stops two type systems from refusing to talk.

Here's the backstory, because it explains why a node this trivial exists at all. WAS Node Suite is one of the oldest, biggest utility packs in ComfyUI, and it predates a lot of the type conventions the rest of the ecosystem settled on. It defined its own generic NUMBER type - a value that can hold an int or a float - and a lot of its math and logic nodes expect that type on their inputs. Core ComfyUI and most other packs, meanwhile, pass around plain INT and FLOAT. So when you try to feed a core INT (a seed, a width, a batch count) into a WAS math node, the wire won't connect. This node bridges that gap.

How it works

It takes the integer and re-wraps it as a NUMBER. That's the entire operation - a type cast, no computation. It runs instantly and touches nothing else.

The input and output

• int - any integer value, typed in or wired from upstream (a seed, a dimension, a count, the output of some other INT-producing node).

The single output is NUMBER - feed it into whatever WAS Suite node was demanding that type.

How to install it

ComfyUI Manager: search MTB Nodes (comfy_mtb), install, restart. Or manually: cd ComfyUI/custom_nodes && git clone https://github.com/melMass/comfy_mtb and restart. It's pure Python with no dependencies, so if MTB loaded at all, this node is present.

Common issues

There's essentially nothing to break - it's a type cast - but a couple of things are worth saying so you don't go looking for a bug that isn't there.

First: this only helps if you actually have WAS Suite installed. The NUMBER type it produces is only meaningful to nodes that accept NUMBER, which in practice means WAS. Converting to a type nothing downstream wants doesn't accomplish anything.

Second: if you need to go the other direction - a WAS NUMBER back into a core INT or FLOAT input - this node won't do it, and WAS Suite ships its own Number To Int / Number To Float converters for that. Think of Int To Number as one direction of a small family of adapters. The moment your graph mixes WAS nodes with everything else, one of these conversions is usually what unsticks a wire that stubbornly won't connect.