This is to assist image generation models such as Auto1111, or Fooocus and its derivatives apply random keywords within an prompt. It should be saved as a .txt file in the wildcards directory. (Note that Ruined Fooocus uses a different location.)
Usage: Simply put two underscores around the filename prefix. i.e. __womensHairStyles__ in the prompt. For example "Close up shot of a beautiful 18 year old woman with her hair in (((__womensHairStyles__))) style,"
This will then cause one of the items in the list to be inserted into the prompt. For example "Close up shot of a beautiful 18 year old woman with her hair in (((__flip hairstyle__))) style", next prompt in the batch could be "Close up shot of a beautiful 18 year old woman with her hair in (((__360 waves__))) style".
Keep in mind that the checkpoint or lora may not recognize the style and will produce a 'default' response.
Description
100 Unique Styles
FAQ
Comments (5)
Do you have a list with all the different hairstyles?
The file is the list itself. It is just a basic text file, so open it up and you can review and edit as you need to.
@swedishViking Thanks I will check it out, I think you basically already put this information in your post so sorry for asking.
Hi, I see you made several separate wildcards. May I suggest doing one master merge and include a catch-all prompt that pulls in one selection from each of the categories? Check out Billions of Wildcards as an example. Look for the "random" selections.
Basically you could have all of your categories collected, and include just one sample prompt for people to use that automatically would pick a hairstyle, hair color, a top, pants/skirts, etc.
Thanks very much for the suggestion. I'm going to think about it for a day or so; specifically the benefits of a monolithic (single file) structure vs an atomic one from both a development perspective and an end-user perspective.
Off the top of my head, one file to rule them all is clearly easier to manage. On the other hand the end-user needs to understand the structure and syntax of the file making it (slightly) more complex to use than a chain of single files.
The direction I was taking was to generate a library of wildcard files and then build a high level wildcard prompt along the lines of [image type][camera angle][distance][subject[subject sub-properties]+][action][modifiers]
I'll keep building the atomic level files for now. I can always use them as a resource to build the OneWildcard.