Nupoma (Shinsplat)

Let's get the name out of the way. "Nuclear Popcorn Machine" was suggested by the author's wife, "it has no meaning except to be goofy," and the source file says he thinks that's brilliant. What it actually is: a small controller node that packages a few values into a Python dictionary string. That's it. The name is the most exciting thing about it, and that's fine - in the context of the pack it fills a real slot.

How it works

You get four inputs - enabled (default true), string (default "empty"), int (default 4), and float (default 0) - and the node assembles them into a dictionary-formatted string on the _control output, with strings quoted and numbers left bare:

{
    "enabled": true,
    "string": "empty",
    "int": 4,
    "float": 0,
}

If enabled is off, it returns an empty dictionary instead. The intended consumer is the pack's control_ inputs - the same "controller dictionary" pattern used by Tensor Toys and Clip Tokens Encode - letting you bundle a set of parameters into one value you can carry on a single wire. Think of it as a typed little settings bag: set your values, pipe _control somewhere that expects a dictionary, done. There's also a help output that repeats the explanation.

The inputs and outputs

• enabled - master switch; off produces an empty dict.
• string, int, float - the values to bundle. int defaults to 4, which the author chose as a test value, not a meaningful constant.

Outputs: _control (the dictionary string) and help.

How to install it

Part of ComfyUI-Shinsplat:

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

or ComfyUI Manager → "ComfyUI-Shinsplat" → restart. No extra deps.

Common issues

• "Where's the output for my values?" - everything goes into the single _control string; if you needed the values individually you'd use this node's siblings (Seed, Sum Wrap) instead. It's a bundler, not a distributor.
• Empty _control - check that enabled is on. That's the only failure mode worth debugging here.
• Don't overthink it - it's a goofy little utility. If the pack's control_ pattern isn't in your workflow, this node has no job and you can ignore it.