90 detailed dynamic prompts with fantasy, sci-fi, video game, mythological and historical themes. Each prompt includes setting, background, pose and (mostly) gender-agnostic character details. Now with booru tags!
For ComfyUI, please use https://github.com/adieyal/comfyui-dynamicprompts, and https://github.com/GrvBdgr/comfyui-negativewildcardsprocessor.
The wildcards contain negative wildcards (text surrounded by <! .. !>). If you do not wish to use these, simply remove the <! .. !> text in the wildcards files with your favorite text editor. Use the following regex:
<!.*!>As of v3.0 the wildcards no longer require Loras or embeddings, for compatibility with all models.
Older versions of the wildcards are not recommended for use.
Usage:
Add a description of the character you'd like in the generated image (feel free to use character LoRas), plus any style/quality keywords necessary for the model you're using, then add __ffpc-booru__.
Example:
best quality, masterpiece, 1man, russian (male:1.1), solo, aquamarine eyes, long brown beard, __ffpc-booru__
Some example characters are provided in the character.txt in the downloaded archive, so if you just want to run a few tests, you can use the following prompt:
best quality, masterpiece, __character__ __full-prompt-fantasy__
More diverse character wildcards can be found here: https://civarchive.com/models/118508?modelVersionId=128565
Negative prompt should be whatever the model necessitates, or your preferred negative prompt. Some models have race or gender bias due to the material that was used for training, you can usually use negative prompts to compensate. eg. if your generations come out with female characters despite describing the character as male, add "woman, girl" to the negative prompt, use weights if necessary.
Additional usage notes:
Other than the above, feel free to experiment with additions to the prompt, though most of the wildcards are rather long, so if you want to have a significant impact, weights may be necessary. The prompts rarely use weights above 1.1, so if your additions seem to have no effect, try weights of 1.15 or more.
Description
FAQ
Comments (10)
1.4 is my first version, it's OK if I only download those Loras? Also some of them may be updated with a higher version that the one posted. How can I work around that?
im not sure if this is a solution for you but it may be possible to go into the text file and find the lora and replace it with the updated lora file name. A month ago i downloaded this wildcard and realized i was missing a whole bunch of the loras and then figured it was a solution for loras where the file names have been changed.
I've tried to keep up-to-date with the used LoRas, but it is possible I missed a few updates. Do you mind listing which are the ones that have newer versions/different names than the ones in the list?
As for the question: you should be fine if you rename the LoRas to the names listed in the description. If the names match, the wildcards will work with the LoRas, regardless of the version.
Your prompts are fantastic! Thank you for putting it together.
One quick note about the prompts.
Dra9onScaleAI has lora:lora, instead of lora: in the prompts. I don't know if that is an issue for everyone, but it was a problem for me so I did a search and replace in the txt and it works now.
Also, it might be helpful to have a list of the version/filename of the lora that we can check to verify the filenames. This might help with new versions, etc. ie: some are loraname-000001, when the download is just loraname, so it won't work without renaming. Food for thought, maybe for v1.5!
Thanks for the heads up, I'll fix the dragonscale LoRa for the next version. Unfortunately LoRa filenames seem to change regularly, and often without a new version being released. I try my best to keep up with these changes, but I guess I'll need to be more thorough with v1.5.
You can check the v1.4 notes in the description for a list of compatible filenames (the text before the link for each LoRa is the filename that the wildcards expect)
Sometimes the dynamic prompt will give an error:
Error running process:
pyparsing.exceptions.ParseException: Expected end of text, found '{' (at char 104), (line:1, col:105)
Seems like a curly bracket is in the wrong place somewhere in the Prompts?
I also get that error on occasion, though I can't seem to figure out why. The curly braces are supposedly balanced in the file (there is the same number of opening braces as closing braces). I've also gotten a similar error when using way simpler prompts with curly braces, where I could definitely tell that there weren't any misplaced braces.
Maybe it's an issue with the extension, or maybe I'm overlooking something. If you notice any concrete typos, issues in the wildcard prompts, I'd welcome the feedback.
Got it!
There was indeed an unnecessary '{' in line #13 of the wildcards file. Must've missed it last time I checked the number of opening/closing brackets. Will correct this for the next version.
@TxcTrtl {{{dystopian|dark} city,|} - here? The second bracket is not highlighted in line 13. However, there are delimiters inside. It seems to me that the bracket is not unnecessary, but on the contrary, it is missing a "}"? Anyway, thanks for your hard work!
@magenta The extra '{' was here (marked with bold font):
{Kremlin,|}}{<lora:SovietPunkAIv2:0.6>
The second bracket you mentioned was not highlighted, because the extra '{' "stole" it (the closing bracket was paired with the extra '{', instead of its intended pair).
Details
Available On (1 platform)
Same model published on other platforms. May have additional downloads or version variants.