VRGDG_BoxIT

VRGDG_BoxIT is a node that does nothing, on purpose. It takes one STRING input called label (default "BoxIT"), stores it, and returns... nothing. No outputs at all. It doesn't save files, doesn't affect the graph, doesn't even log meaningfully. It exists so you can drop a named box into a workflow to hold a label - a visual annotation that survives a graph save and tells you (or the person you share the workflow with) what a region of spaghetti is supposed to do.

In a pack built around a long, multi-stage music-video pipeline, that's less silly than it sounds. The VRGameDevGirl workflows are big graphs - set-math nodes, 16 video inputs, trigger wires everywhere - and a floating label ("SCENE GENERATION", "FINAL ASSEMBLY") turns a wall of nodes into something navigable. When you drag someone else's workflow in and the missing-node list includes a pack you've never heard of, half the confusion is "what is this graph even doing?" BoxIT is the author's answer: a tiny bit of self-documentation in the graph itself.

How it works

There is no "how it works," mechanically. run(self, label) returns an empty tuple. The label you type is what shows in the node's title box, and that's the entire behavior surface. It's a pure UX affordance, the ComfyUI equivalent of a comment block in code - except it renders inline where you placed it, which is often more useful than a comment buried in a text node somewhere across the canvas.

The practical trick: since the label input is a regular STRING port, you can wire a text node into it if you want the label to be dynamic (e.g., showing the current run name or set index). That's a real pattern in the pack's workflows - a BoxIT labeled with the current output_name makes a saved graph tell you what it was doing when it was captured.

Install

Same pack as everything else here: ComfyUI Manager → search "vrgamedev", or git clone https://github.com/vrgamegirl19/comfyui-vrgamedevgirl into ComfyUI/custom_nodes, restart. No dependencies, no models, no requirements beyond the pack itself. If you're looking for something with more function, this isn't it - but if you're tired of squinting at an anonymous 30-node graph trying to remember which branch is the audio route, this is the cheapest documentation you'll ever add.