✏️ Literal Float

A single decimal value, sitting on its own wire, that you can fan out to more than one node at once - that's the entire job of Literal Float. It's the pack's plain float-input primitive: no logic, no conversion, just a number you type once and reuse.

How it works

You type a value into the widget and it comes out the other side unchanged. The range is generous - anywhere from -10,000,000,000 to 10,000,000,000, in steps of 0.001 - so it comfortably covers anything from a CFG scale to a LoRA weight to a denoise strength without you running into a clamp.

It exists for the same reason ComfyUI lets you "convert to input" on most float widgets: once a value is a socket instead of a checkbox baked into one node, something needs to sit on the other end and supply it. This node is the plainest possible thing to put there - no math, no randomness, just whatever number you typed.

The inputs and outputs that matter

• value - the float itself, default 0, step 0.001. That's the whole node.
• Output: value (FLOAT), passed straight through.

How to install it

Via ComfyUI Manager: search ComfyUI-mnemic-nodes, install, restart. Or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/MNeMoNiCuZ/ComfyUI-mnemic-nodes

Restart ComfyUI afterward. No dependencies, no models - it's a plain value node.

Common issues & troubleshooting

The main reason to reach for this over just typing a number directly into a widget is reuse: if the same float - say a LoRA strength - needs to feed two or three different nodes and stay in sync, one Literal Float beats duplicating the value in multiple places and forgetting to update one of them later. It's also the natural way to expose a decimal parameter through the ComfyUI API, since a value sitting on its own node is easy to target and override at run time in a way a buried widget isn't.

It pairs naturally with other float-taking nodes in this same pack - feed a fixed component_scale or warp_intensity into Colorful Starting Image from one shared source, for instance, instead of typing the same number into several widgets and having them quietly drift apart the next time you tweak one and forget the other.

The one real gotcha is type mismatches - a node expecting an INT input won't accept a FLOAT connection without an explicit convert node in between, even if the number you typed happens to be a whole number like 5.0. If you actually need a whole number, use the pack's Literal Int instead rather than relying on a float that happens to round cleanly. And watch the step size if you're typing precise values by hand - 0.001 increments mean the widget's arrows move in small jumps, though direct typing isn't limited by that.