Wildcards Editor for ComfyUI
An extension for ComfyUI that brings interactive management capabilities to your Wildcards system.
Features
- Interactive Wildcards Management: Seamlessly create and modify Wildcards files directly within the ComfyUI interface
- Slot Management: Effortlessly add, remove, or modify wildcards slots
- Easy Preview Generation: Visualize your changes immediately with image generation
- Intuitive Interface: User-friendly controls for managing your wildcards structure
This tool streamlines the wildcards workflow in ComfyUI by providing immediate visual feedback for your modifications, allowing for a more efficient and interactive development process.
Install
Extract files from the zip file
Load wildcard pony generator.json into ComfyUI
Install missing nodes
Copy m.yaml to ComfyUI/custom_nodes/WildDivide/wildcards
Install loras from the asset.md file
Restart ComfyUI
Description
More loras
Filter for values
Probabilities for each value
Auto template
Turn on/off scaler, face detailer, final sampler
FAQ
Comments (13)
Hi there! This workflow is what actually finally convinced me, someone who began on A111, then moved to Forge, then ForgeNext, to actually take a look at Comfy. I've always wanted to do similar things in Forge, but it's an absolute nightmare getting the prompts just right - even with YAML and Dynamic Prompts, even if you have it set up right, it can and will choke on limits unless your breaks are perfect - and even then, due to how breaks work, each further thing along eventually gets less and less attention.
I've got some questions/suggestions:
1) Do you currently support Long Clip? If not, do you plan to do so? This would greatly increase the amount of stuff that could be added into the image. From what my noob-to-Comfy-ass knows, support for Long Clip in Comfy in general was added at least 3+ months ago.
2) Some of the later templates (the ones that skip random character gen entirely) seem to be intended for character LoRAs or something. If this is the case, it's probably better to add some [SEP] tags in here, like the random gen ones do. (Of course, I could add this myself and did so, but there will be people who use this who want something that "just works."
3) Right now it seems like the name of the file this reads is hardcoded (m.yaml) and the "template" bit up top is also what's expected by the workflow to generate the template. While not a dealbreaker, it took me awhile to figure out how to make a new one - IIRC the only place that got mentioned is on your GitHub for WildDivide. (For the sake of anyone reading this, if you want to "roll your own," delete everything after the template: line in your text editor and go from there).
4) Despite the hardcoded filename, you seem to be reading any/all YAMLs in the directory you expect m.yaml to be in. This threw me off for a very bad loop last night when I tried handcrafting my own (with a different filename) and was confused at why it seemed to be making options m.yaml insisted were not inside of it!
5) The documentation seems a bit unclear at times. For example, you mention (on WildDivide's readme) that a conditional tag wrapped in slashes /like this/ is the pattern that will be searched for a find-replace, but yet in the YAML itself this is nowhere to be found - instead, you use a => to seemingly denote it. (A shift in encoding, perhaps? A coder friend of mine mentioned one is pattern-based, one is more regex...).
Sorry for dropping this textwall in a narrow-ass comment box. Please keep up the good work!
1) I didn't know about Long Clip. I will look into it.
3) Yah... I also don't like the hard coding things (m.yaml, template slot).
4) Reading all yaml files was there (original wildcard implementation from Impact pack)
5) I didn't remove /pattern/ thing for backward compatibility, but I will eventually.
Thanks for your comment/suggestions!
this wall broke my nose.
@sdbz2010 I tend to have that effect on people.
tried to implement this into my larger workflow but seems like this node will bugged out when the number nodes reached a certain number :(
Not working for me. I don't see any options inside the node. No idea how to fix it
any screenshot?
Had the same issue when I tried editing catagories for wild card generation manually. Swapping out the m.yaml file with a newly downloaded one fixes it.
quite successful, the wildcard variety is satisfying. After installing the nodes, 1 reboot is sometimes not enough. after a few downloads in the background, rebooting for the 2nd time works fine.
Wayyyy too many loras to download, in my opinion. Great concept but totally unrealistic if the creator expects us to download all those loras. Also, would be easier to download loras if it was in a simple list of urls I could copy and past over without the lora tag involved
i dont know how to use the readme.md, i have to download each one manually?
if you want exact same results. but depending on the image model, some poses/clothings/etc will be drawn without lora.
@julianadventurerdev941 thanks for your reply.