Small fix to correct the behavior of the World Info NOT operator with a list of secondary keys to what was (hopefully) intended. Previously only the first secondary key was ever checked. Now each primary key should be checked against each secondary key with a single match invalidating the entry activation.
Add support for adding extension prompts into WI scanning. Doing this
required adding a method to get extension prompts by name. Now, AN
and depth prompts can be added to world info scanning.
However, since scanning just looks for keys in the chatlog, append
the extension prompts on the top of scanned text.
Signed-off-by: kingbri <bdashore3@proton.me>
* Kobold Presets fixed
* Help texts fixed
* Scale API for connectAPISlash
* Quick Reply checkboxes fixed
* New Instruct Mode Presets
* More date/time macros
* ChatML context template and instruct prompt format
* Mistral context template and instruct prompt format
* Removed use_default_badwordsids from kobold presets
* Renamed ChatML to Mistral-OpenOrca (ChatML)
* Renamed Mistral-OpenOrca (removed ChatML)
* Removed single_line from kobold presets
* Removed obsolete use_stop_sequence setting
* Ban EOS Token off by default
* Split AI Resp. Conf. in global and preset-specific settings
* Resolve conflicts
* Fix title
* Add translations for new help texts
* Fix i18n.json whitespace
* Make Mistral-OpenOrca system prompt more generic
* Renamed "Mistral-OpenOrca" to "ChatML" again
* More (UI) fixes and improvements
* Sendas hint fixed
---------
Co-authored-by: Cohee <18619528+Cohee1207@users.noreply.github.com>
Depth previously injected entries randomly. This is not ideal for
world info architectures that rely on insertion order to function
properly.
Redo depth injection to have its own parameter and redo how it's
handled in generate.
Signed-off-by: kingbri <bdashore3@proton.me>
* World Info: Add character locking for entries
With the addition of depth, world info has become more important than
ever. However, there is a conflict that can occur when using multiple
world info or lorebooks on a character. Add the ability to lock
entries to a specific character (or characters) if needed.
This allows for adequate separation especially when there are character
cards each with their separate lorebooks that build off of a core lorebook.
Signed-off-by: kingbri <bdashore3@proton.me>
* World Info: Add entry-specific character exclusions
This is the opposite of locking an entry to a specific character.
Exclusions allows the entry to get included for everyone except the
specified characters in the list.
Signed-off-by: kingbri <bdashore3@proton.me>
---------
Signed-off-by: kingbri <bdashore3@proton.me>