You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`KNOWLEDGE_SERVER_MEMORIES`| 4 | Server-level memories |`/memory server add`, `/memory server remove`|
78
78
|`KNOWLEDGE_SERVER_EMOJIS`| 5 | Available custom emojis |`/server initialize expressions`|
79
79
|`KNOWLEDGE_SERVER_STICKERS`| 6 | Available stickers |`/server initialize expressions`|
80
-
|`KNOWLEDGE_USERS_IN_CONVERSATION`| 7 | User list + personal memories + status + reminders + time/channel info |`/teach memory personal`, `/forget memory personal`|
80
+
|`KNOWLEDGE_USERS_IN_CONVERSATION`| 7 | User list + personal memories + status + reminders + time/channel info |`/memory personal add`, `/memory personal remove`|
81
81
|`KNOWLEDGE_SHORT_TERM_MEMORY`| 8 | Recent conversation summaries from other channels (STM) |`/personal cache`|
|`KNOWLEDGE_SERVER_CONDITIONING`| 10 | Reward/punish conditioning guidance for the active persona |`/conditioning reward`, `/conditioning punish`, `/conditioning manage`|
4. Server info = server name + description [KNOWLEDGE_SERVER_INFO]
97
-
5. Server memories (/teach memory server)* [KNOWLEDGE_SERVER_MEMORIES]
97
+
5. Server memories (/memory server add)* [KNOWLEDGE_SERVER_MEMORIES]
98
98
6. Server emojis* [KNOWLEDGE_SERVER_EMOJIS]
99
99
7. Server stickers* [KNOWLEDGE_SERVER_STICKERS]
100
100
8. Users in conversation = user list + personal [KNOWLEDGE_USERS_IN_CONVERSATION]
@@ -122,7 +122,7 @@ When a SillyTavern preset is active, the system uses a **Build-Then-Rearrange**
122
122
5. Merge depth-injected nodes into dialogue history items
123
123
6. Flush any remaining TomoriBot-only blocks at anchor points
124
124
125
-
This avoids refactoring the native builder while gaining full preset control over prompt ordering. The native blocks still contain the same content (system prompt from `/sysprompt`, personality from `/teach attribute`, etc.) — the preset only controls **where** each block appears and **what additional content** is injected around them.
125
+
This avoids refactoring the native builder while gaining full preset control over prompt ordering. The native blocks still contain the same content (system prompt from `/sysprompt`, personality from `/persona attribute add`, etc.) — the preset only controls **where** each block appears and **what additional content** is injected around them.
126
126
127
127
If the preset is deactivated or deleted, context assembly immediately reverts to the native fixed order above. No data is lost — `/sysprompt`, personality attributes, memories, and all other settings are stored independently from the preset.
Copy file name to clipboardExpand all lines: docs/integrations/matrix-bridge.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -340,7 +340,7 @@ Matrix users can be set as reminder targets. Since they have no row in the `user
340
340
341
341
1.**`reminderTool.ts`**: Skips BigInt fuzzy-matching (Matrix IDs are not numeric), skips `users` table lookup, and trusts the AI-provided nickname directly.
342
342
2.**`reminderTimer.ts`**: After delivering the reminder, calls `sendMatrixReminderMention()` instead of the Discord mention path. This sends a direct Matrix mention to the linked room if the AI response didn't already include the `@{localpart}` placeholder.
343
-
3.**`forget/reminder.ts`**: Displays Matrix reminders with `(Matrix)` suffix and `for {nickname}` instead of `created by {nickname}` so server managers can identify them.
343
+
3.**`personal/reminder/remove.ts`**: Displays Matrix reminders with `(Matrix)` suffix and `for {nickname}` instead of `created by {nickname}` so server managers can identify them.
344
344
345
345
Matrix user IDs are stored as-is in the `user_discord_id` TEXT column of the `reminders` table (which already accepts arbitrary strings). No schema changes were needed for reminder support.
|`/forget attribute`|`forget/attribute.ts`| Persona picker + single paginated select | Personality attributes are usually reviewed and pruned in batches | Needs index-safe array rewrite if duplicate attributes must be preserved |
422
-
|`/forget reminder`|`forget/reminder.ts`| Persona picker + single paginated select | Reminder cleanup is often batch-oriented, especially for stale schedules | Manager-only reminder views may need concise descriptions |
423
-
|`/forget document`|`forget/document.ts`| Persona picker + single paginated select | Document cleanup is an obvious multi-select management flow | Large lists should keep paginated fallback |
424
-
|`/forget history`|`forget/history.ts`| Persona picker + single paginated select | History entries are frequently pruned in groups | Large lists should keep paginated fallback |
425
-
|`/forget sampledialogue`|`forget/sampledialogue.ts`| Persona picker + single paginated select | Dialogue cleanup is often batch-oriented and already has index-safe removal | Good fit for index-valued checkbox groups |
421
+
|`/persona attribute remove`|`persona/attribute/remove.ts`| Persona picker + single paginated select | Personality attributes are usually reviewed and pruned in batches | Needs index-safe array rewrite if duplicate attributes must be preserved |
422
+
|`/personal reminder remove`|`personal/reminder/remove.ts`| Persona picker + single paginated select | Reminder cleanup is often batch-oriented, especially for stale schedules | Manager-only reminder views may need concise descriptions |
423
+
|`/memory document remove`|`memory/document/remove.ts`| Persona picker + single paginated select | Document cleanup is an obvious multi-select management flow | Large lists should keep paginated fallback |
424
+
|`/memory history remove`|`memory/history/remove.ts`| Persona picker + single paginated select | History entries are frequently pruned in groups | Large lists should keep paginated fallback |
425
+
|`/persona sample-dialogue remove`|`persona/sample-dialogue/remove.ts`| Persona picker + single paginated select | Dialogue cleanup is often batch-oriented and already has index-safe removal | Good fit for index-valued checkbox groups |
426
426
|`/persona remove`|`persona/remove.ts`| Single paginated select | Alter persona cleanup could be batch-managed | Should pair the bulk UI with stronger destructive-action messaging |
427
427
428
428
### Not Candidates — Keep String Select
@@ -439,14 +439,14 @@ These modals have dynamic or large option sets that exceed Radio Group/Checkbox
439
439
|`/config model fallback`|`config/model/fallback.ts`| Dynamic model list, uses pagination |
440
440
|`/config system-prompt preset`|`config/system-prompt/preset.ts`| Dynamic preset list from DB |
441
441
|`/config api-key set`|`config/api-key/set.ts`| Provider select + text input combo; list may grow |
442
-
|`/teach personaprompt`|`teach/personaprompt.ts`| Dynamic persona list + free-form prompt (up to 16000 chars, 4 fields) |
443
-
|`/teach attribute`|`teach/attribute.ts`| Dynamic persona list, uses pagination |
444
-
|`/teach sampledialogue`|`teach/sampledialogue.ts`| Dynamic persona list, uses pagination |
445
-
|`/teach memory personal`|`teach/memory/personal.ts`| Dynamic memory list |
446
-
|`/teach memory server`|`teach/memory/server.ts`| Dynamic memory list |
442
+
|`/persona prompt set`|`persona/prompt/set.ts`| Dynamic persona list + free-form prompt (up to 16000 chars, 4 fields) |
443
+
|`/persona attribute add`|`persona/attribute/add.ts`| Dynamic persona list, uses pagination |
444
+
|`/persona sample-dialogue add`|`persona/sample-dialogue/add.ts`| Dynamic persona list, uses pagination |
445
+
|`/memory personal add`|`memory/personal/add.ts`| Dynamic memory list |
446
+
|`/memory server add`|`memory/server/add.ts`| Dynamic memory list |
447
447
|`/novelai image-tags character`|`novelai/tags/character.ts`| Dynamic persona list |
0 commit comments