Pakobbix/rpg-companion-sillytavern
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove redundant data commit call in sillytavern.js to prevent n-2 tracker data commits in fresh message generations

Browse Source
This commit is contained in:
Daryl
2026-02-26 17:09:33 -04:00
parent ce48ac0c34
commit c442314c10
1 changed files with 0 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/systems/integration/sillytavern.js
-8
View File
@@ -164,14 +164,6 @@ export function onMessageSent() {
// Note: FAB spinning is NOT shown for together mode since no extra API request is made // Note: FAB spinning is NOT shown for together mode since no extra API request is made
// The RPG data comes embedded in the main response // The RPG data comes embedded in the main response
// FAB spinning is handled by apiClient.js for separate/external modes when updateRPGData() is called // FAB spinning is handled by apiClient.js for separate/external modes when updateRPGData() is called
// For separate mode with auto-update disabled, commit from the prior assistant message's
// swipe store rather than lastGeneratedData to avoid ghost context from sibling swipes.
// At this point chat[chat.length - 1] is the user message, so search from before it.
if (extensionSettings.generationMode === 'separate' && !extensionSettings.autoUpdate) {
commitTrackerDataFromPriorMessage(chat.length - 1);
// console.log('[RPG Companion] 💾 SEPARATE MODE: Committed from prior assistant message (auto-update disabled)');
}
} }
/** /**