These nodes were created to solve challenges in developing AegisFlow Shima, a modular ComfyUI workflow building system. But you might find them useful in your own workflows, so have at them!
The Utility nodes have a variety of "Passer" nodes that can both passs through items targeted by Use Everywhere nodes, as well as secure an input that requires one. This is necessary because Comfy and/or some common custom node will try (and sometimes doesn't succeed) to "fix" required open inputs using any output that matches, even if that doesn't work, breaking the wf (this is an "all workflows problem," not an AegisFlow problem). The key thing is that the INPUTS of these passers are optional, and as such they don't trigger whatever "autofixing" seems to go on behind the scenes. They are a bit of a nameable target AND a plug for the end of a cell's receptors, preventing the WF disease of "let's just wire this to that for giggles."
Most commonly used is an "image" passer, but you can do others like latents, masks, CLIP etc. There is also a "Placeholder Tuple" for times when you need to fill a Tuple but aren't going to actually use it. This is helpful in developing template workflows that are frequently broken when inputs are left unoccupied (ask me how I know). If you need a passer included, suggest it and I'll work on making one.
...And the "multipasser" which gangs them all together so they can be collapsed into the "superlaser."
I was having many users unable to satisfy some great nodes from the ally and thusly integrated them here, and also needed a way to turn them on/off easily, so I extended them with an "enable/disable" switch.
Thanks to the positronic matrix of Dutch Dev mortael, we now have nodes that group automatically when placed in a template, and name themselves after the template name. This is a key QOL improvement that also ensures we can take full advantage of Chris Goringe's Use Everywhere nodes that are used in AegisFlow Shima, which recently added in execution control via group name.
Do you hate the color palette limitations of LiteGraph? I DO. I hate that "yellow" is considered that "burnt ochre" color that you threw away from your crayons because it's so gross. Problem is, until now that was all it could be: the color of the text is grey and the text of the coloring shall be grey. It meant that without developing an entirely new theme, you couldn't use high-brightness colors at all.
But you might have noticed in the first image in the readme that you can actually read those nodes...
The world used to be a dark place. But now, color can come back into your WFs, opening new possibilities for usability:
Note: Zero consideration was made for the eye-destroying light theme. Only the Dark Side here.
The Utility Nodes are a free community resource, as is the classic version of AegisFlow (although I am no longer updating the AegisFlow WF)
That said, my kids like to be able to eat, and you can support me through a Major Studio membership or a one-time $15 payment at majorstudio.gumroad.com that will get you the entire death star and future updates, new modules, and enhancements like the Shima Hub and installer.
