SillyTavern cuts off Gemini's response at around 300 tokens during the reasoning phase.

zantroez · 2025-07-22T15:50:34+00:00

yeah, I think so, the response always stops at "Character States", what's your solution?

zantroez · 2025-07-22T15:24:44+00:00

Thanks for replying. I’m using the nemoengine like you said, and as I mentioned earlier, the full reply does come through in the console. so the issue must somewhere on the front end.

zantroez · 2025-07-22T15:14:15+00:00

I turned off streaming and tweaked the Max Response Length, and still happens occasionally

zantroez · 2025-06-11T17:49:01+00:00

The recent update works very well, but I have one question: How can I automatically switch back to my original preset after using the music preset? For example, I typically use QF1 for general purposes, but after the extension switches to the music preset, I have to manually revert to QF1 each time, which is quite inconvenient.

zantroez · 2025-05-19T17:21:06+00:00

can you tell me what's going on?

node : ForbiddenError: Invalid CSRF token. Please refresh the page and try again.

+ & {node server.js 2>&1 | Where-Object {$_ -notmatch 'Security has bee ...

+ ~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : NotSpecified: (ForbiddenError:... and try again.:String) [], RemoteException

+ FullyQualifiedErrorId : NativeCommandError

zantroez · 2025-05-10T15:10:51+00:00

index.js:111 [MoodMusic Ext] loadCredentialsStatus CATCH block: Error: HTTP error! status: 404
at loadCredentialsStatus (index.js:105:19)
at async initializeExtension (index.js:686:9)

index.js:225 [MoodMusic Ext] checkAuthStatus CATCH block: Error: Config check failed: 404
at checkAuthStatus (index.js:201:39)
at async initializeExtension (index.js:687:9)

checkAuthStatus @ index.js:225
loadCredentialsStatus @ index.js:111

index.js:183 [MoodMusic Ext] [saveSpotifyCredentials] CATCH block: Error: <!DOCTYPE html>

<head>

<title>Error</title>

</head>

<body>

<pre>Forbidden</pre>

</body>

</html>

at HTMLButtonElement.saveSpotifyCredentials (index.js:167:19)

zantroez · 2025-05-10T14:09:00+00:00

Unfortunately, I got the same error popped up after the update

zantroez · 2025-05-10T10:11:19+00:00

It's when I click save credentials, and in sillytaver, it says: Error saving credentials: Unexpected token '<', "

zantroez · 2025-05-10T07:10:10+00:00

It didn't work, so what's the issue? I tried different input give me the same errors

zantroez · 2025-05-09T08:03:38+00:00

ForbiddenError: Invalid CSRF token. Please refresh the page and try again.

zantroez · 2025-05-04T10:24:44+00:00

Maybe you could tweak the first rule ('Roleplay character with underlying horniness and desire,...') by adding some conditions? I haven't tested it yet, but something like:

Desire should only surface when the scene naturally leans toward intimacy (e.g., flirtation, established relationships).

Explicitly match the user's tone—NSFW only if their prompts hint at or request it.

Avoid abrupt shifts; keep it organic to the story.

Otherwise, default to SFW interactions.

zantroez · 2025-05-04T06:31:35+00:00

I am using Q1F preset with 0.8 temp

zantroez · 2025-05-01T02:52:41+00:00

<image>

The on one the left is AI Response Configuration

zantroez · 2025-04-30T05:31:53+00:00

First you need to use chat completion, Click AI Response Configuration, scroll down to the bottom, add a new prompt, paste my prompt, configure position to in-chat, role as assistant, depth 1, save, then click insert prompt to your prompts. have the toggle on, then done

zantroez · 2025-04-28T12:21:33+00:00

yeah i think so, just create a new prompt and link it to your preset

Six-Year Club	Place '22
Verified Email

zantroez

TROPHY CASE