Debug Number to Console

Not documented by name in WAS's README, but it's a clear sibling to the pack's other console-print nodes - "Dictionary to Console" is right there described as "Print a dictionary input to the console," and Debug Number to Console applies that exact same idea to the NUMBER type. It prints whatever number reaches it to the console at the point in your graph where you dropped it, and does nothing else.

The value of that is bigger than it sounds once you're working with WAS's number tooling for anything beyond a fixed value. Number Operation, Random Number, Image to Seed, Number Multiple Of, Latent Size to Number - any of these can produce a number that isn't what you expected, and unlike a boolean or a short string, a number flowing silently through a graph gives you no visual signal that it's wrong until it causes a downstream failure (a seed that's out of range, a resolution that isn't a valid multiple, a count that's off by one). By the time that failure shows up, you're debugging the symptom instead of the cause. Debug Number to Console lets you check the actual value at the source, before it does any damage further down the chain.

The practical pattern: drop it right after whatever node is computing the number you're suspicious of, run the workflow once, and read the value in your server log. If it's what you expected, remove the node (or leave it - it shouldn't interfere with the rest of the graph either way) and move on. If it's not, you've just isolated exactly which step in your number math went sideways instead of guessing.

Same detail applies here as with every "to Console" node in this pack: the output goes to the server console, not anywhere visible in the browser UI. Locally, that's your terminal window. On a hosted platform, that's your run logs - if you add this node expecting to see the number appear somewhere on the canvas, you're looking in the wrong place.

Input is a NUMBER; there's no meaningful downstream output beyond, at most, a pass-through of the same value - the entire point is the console print, not anything the rest of the graph needs to consume.

Installing it: ComfyUI Manager, search "WAS Node Suite," install, restart. Manual: cd ComfyUI/custom_nodes && git clone https://github.com/WASasquatch/was-node-suite-comfyui, then pip install -r requirements.txt (portable: python_embeded\python.exe -s -m pip install -r requirements.txt; manual/venv: activate the venv first), restart ComfyUI. No model, no external dependency - it's a print statement in node form.

Where it bites: essentially nowhere on its own, since there's nothing external for it to depend on. The actual risk sits one level up, as it does for every node in this pack: WAS Node Suite has had no active development since December 2023 (the README says "Retired" outright), and the community's recurring, well-documented complaint is the whole suite failing to import after a ComfyUI or Python update rather than individual debug nodes breaking on their own. If Debug Number to Console (or any WAS node) stops showing up in your search, check your startup console for an import error on the entire suite before troubleshooting this node in isolation.