VRGDG_HumoReminderNode

VRGDG_HumoReminderNode is the pack's reminder-in-a-box: a trigger goes in, the node reminds you of whatever it's set to remind you of, and the trigger comes back out. There's an enabled toggle, defaulting to on, so you can silence the reminder without rewiring the graph.

The "HUMO" in the name is a pointer, not a feature. The pack README pitches itself around "HUMO-based multi-scene workflows" - HUMO being the Wan-based image-editing/remix model that's been doing the rounds in ComfyUI - and this node lives in those graphs as a checkpoint marker. Some step in the HUMO scene pipeline benefits from a human doing a thing (checking a frame, saving a state, swapping a reference) before the run continues, and this node is where that reminder lives. The trigger in → trigger out shape is deliberate: it slots into the execution path without altering the data, so the reminder fires on every pass without you having to add a branch.

What you actually set

There's very little to configure, which is the point of a marker node.

• trigger - any wire carrying any type; the node just needs to be in the flow to fire.
• enabled - the single useful knob. Off means the node is a pure pass-through and the reminder stops firing.

Everything the reminder says is baked in by the author for the specific workflow you loaded. There's no text field to edit, so if you've dropped this into your own graph expecting to write a custom message, you'll be disappointed - it's a pre-written nag, not a notepad.

The honest take

Documentation for this one is thin even by this pack's standards, so treat it as exactly what its schema shows: a gate-shaped reminder. If you're running a VRGDG HUMO workflow as-is, leave it enabled and let it do its job. If you've repurposed the graph and the message no longer applies, flip enabled off rather than deleting the node - keeping it in the path means you don't have to rewire when you want the reminder back.

Install is shared with the pack:

cd ComfyUI/custom_nodes
git clone https://github.com/vrgamegirl19/comfyui-vrgamedevgirl

or Manager → search "vrgamedev", restart. It has no model or dependency of its own beyond the pack's kornia/librosa/imageio requirements. It's a utility, not a tool - but for a multi-scene workflow where a forgotten manual step means redoing an hour of generation, a nagging pass-through node is worth keeping around.