Sillytavern not Initilazing

#3
by Skydea - opened

Hi There David, wanted to try your Script/Mod.
(Running latest Build 1.12.11 (Staging) of SillyTavern)

Changed the files in Public tried the Normal and the me-me Version.
Upon starting ST I had to notice following message:

'> node post-install.js

Synchronized missing files: ./public/ <----

up to date in 1s'

(Using both UpdateAndStart.bat and normal Start.bat)

When the Browser then Auto Opens the Script just does not run.
No Files actually will get changed by the message above, File Size and Date stay the same.

You can then just rename the Files again and use the Original ones and just Refresh via F5 / CTRL + SHIFT + R and it starts Normally.

I have no clue what is wrong here but I wanted to mention it.

Will try again.

Continue your enthusiastic work!

Okay a few issues may have occurred:

1 - There MUST be a file named "script.js" in the public folder.
2 - You must update (using Launcher) to the latest ST version BEFORE using the patch/core I build, otherwise other script(s) will be out of sync.
3 - If you get a blank screen, try using one of the other "cores" I build, rename to "script.js" -> and retry.

Caution:

If you edit/change settings in the script.js file(s), edit only in notepad. A single error, can cause the script.js to fail, and you will get a blank screen.

If in doubt - > Download the zip file from Silly Tavern -> Extract - > get the original "script.js" file -> Paste into "public folder" -> Ensure ST starts up correctly FIRST.
If this does not work, this means there is an issue in the ST install itself, not in the new "core(s)" from me - and this must be resolved first.
If this does work -> THEN proceed with replacing the "script.js" with one of the new "cores" from my repo.

  1. Yeah, i work in IT, I understood your guide. ;)
  2. Multiple Times a day on the bleeding edge, I did that.
  3. I will try the other builds tomorrow.

The Script Files where not Changed (Besides Renaming).
I made a copy of your script and opened this one In Notepad++, did not save and removed it, was curious, as I said, I read your Guide :).

When I tested it this morning I also got this issue, seems like it doesn't work with staging but with the latest release branch.

Then again, I don't know if it actually did something, sillytavern ran but I didn't notice any different nor in koboldcpp trying multiple settings.

This makes sense, as the script.js I used and patched is from "release" , and script.js (at ST) has a lot of modifications between releases.

works on ST release branch, not on staging. keep on eye on that.

Sign up or log in to comment