diff --git a/Prompt-Tips.md b/Prompt-Tips.md index 236ea9a..42e4cce 100644 --- a/Prompt-Tips.md +++ b/Prompt-Tips.md @@ -1,5 +1,10 @@ # Prompt Tips +> [!NOTE] Different models have different prompting best practices. When in doubt, refer to model specific notes on CivitiAI website + +For example: standard **SD15/SDXL** models are prompted very differently vs **Pony**-derived models vs **SD35** or **Flux.1** derived models - it all comes down to which text enocder is used and how it was trained. +For more details, see [Prompting](Prompting.md) with different models wiki page. + ## Params TL;DR: Tweak **steps**, **cfg scale** and **sampler** as results will vary depending on combination of all three diff --git a/To-Do-(Wiki).md b/To-Do-(Wiki).md index 11c72b3..1c3894f 100644 --- a/To-Do-(Wiki).md +++ b/To-Do-(Wiki).md @@ -2,18 +2,13 @@ - Cross-reference `Scripts.md` with whats available in text/image tabs Add missing info as needed -- Create separate `FAQ.md` - Use following info as starting point - - - - -- Create separate `Styles-Wildcards.md` - It should cover functionality of styles AND wildcards +- Create separate `Styles.md` + It should cover functionality of styles - Create separate `Face.md` Current content in Scripts.md regarding Face should be moved here Should also cover PulID - Create separate `IPAdapter.md` Expand a bit -- Add screenshots where needed to any of the wiki documents ## Markdown diff --git a/Wildcards.md b/Wildcards.md new file mode 100644 index 0000000..cc7ba69 --- /dev/null +++ b/Wildcards.md @@ -0,0 +1,39 @@ +# Wildcards in Prompts + +Wildcards are placeholders in the prompt text that are replaced with a random value from a list of choices which allows for more variety in the prompts generated. + +- SD.Next supports standard file-based wildcards in prompts. +- Wildcard support is enabled by default, enabled by default, can be disabled in *settings -> extra networks* if you want to use 3rd party extension instead of SD.Next built-in support. +- Wildcards folder is set in *settings -> system paths*, default is `models\wildcards` + +## How does it work? + +*TL;DR*: string `"__abc__"` in prompt is matched to a file `abc.txt` inside wildcards folder + +The prompt syntax for wildcards is: + +> a woman wearing a ```__color__``` dress + +In the wildcards folder, create file `color.txt` and add multiple choices with one choice per line: + + red + green + blue + +## Tips + +- Wildcards can be used in both positive and negative prompts +- Prompt can have any number of wildcards + > a woman wearing a ```__color__``` dress and a ```__shape__``` hat +- Wildcards can be nested + Line inside wildcard file can also have a wildcard referrring to another wildcard, etc. +- Supports filename-only and path-based wildcards with full subfolder support + If wildcard is refered as `__color__` then it will look for file `color.txt` in wildcards folder and *any* subfoldrer + If wildcard is refered as `__nsp/color__` then it will look for `color.txt` *only* in `nsp` folder inside wildcards folder +- Wildcards files can be in one-choice per line or multiple choices per line separated by `|` format + +### Validation + +Wildcard matches and replacements will be logged in the standard log with debug level: + +> DEBUG Wildcards apply: wildcard="color" choice="Yellow" file="models/wildcards/my-variations/color.txt" choices=930