- The first macro evaluation occurs when the entry is activated.
- The second macro evaluation occurs after the regex replacement
* and only when the entry is before or after the char definition
this may cause confusion for users.
I'm not sure if this is the right thing to do, but it's one way I can think of to make all this make more sense.
- Tied and only visible to the "delay until recursion" toggle
- Will set it to a numerical value if used, otherwise keeps true/false state of the toggle
- When a WI entry has sticky, and inclusion group and "delay until recursion" set, another entry from the same group might prevent the sticky from activating. This is fixed here.
- Instead of processing entries by default sorting (based on order and books (char first, etc)), sticky will now be the first to process. This will make sure that stickied entries will reach the prompt, even in budget-limited scenarios.
* Include slider for Max Recursion Depth
* Implement Behavior for Max Recursion Depth
* Title message correction
* Disabling min activations when max recursion depth is disabled and vice versa
* Feature renamed to Max Recursion Steps
* Added warnings that min activations and max recursion steps disable each other
* Revert "Added warnings that min activations and max recursion steps disable each other"
This reverts commit 8c7efd09c5.
* Revert "Feature renamed to Max Recursion Steps"
This reverts commit f043fe6b60.
* Revert "Disabling min activations when max recursion depth is disabled and vice versa"
This reverts commit a3a28874bf.
* Renames the feature to Max Recursion Steps and disables it when Min Activations are enabled
* Combine info-warnings, log stop condition
---------
Co-authored-by: Your Name <you@example.com>
Co-authored-by: Cohee <18619528+Cohee1207@users.noreply.github.com>
* Update world-info.js
- make the rename button is also available in case of WIbook corruption.
- make the WI engine doesn't crash when certain entrys with `content === null`.
* Update zh-cn.json
* Part revert "Update world-info.js"
This part reverts commit 0693c9c400.
- WI entry updates utilize debounced save
- Trade-off between consistency of possible data loss and performance issues in STscript loops that update multiple things in a WI file are not worth it.
- Implement StructurecCloneMap, which is a map that provides structured clones on both get and set
- Don't delete WI cache on save, but update the cache
- Ensure that cache is updated immediately, so any future get will load the new saved data already
- Still be consistent with clones, so requested cache data that wasn't saved isn't taken into account
