Edit #2: This is now a bug-report. I changed the “reply as” option back to the default user, exported the thread, and it imported correctly.
Because I’m paranoid, I export my data frequently, but when testing to see how easy it was to re-import data, I keep running into this error.
I’ve tried exporting the thread multiple times, but it will not import properly. The imported thread appears and is interactable, but if you click on it, it starts an infinite loading screen that locks up the tab.
Considering the amount of time I’ve spent on some of these stories, it makes me uneasy that the official method of saving them just…doesn’t work.
Windows 11, Chrome on desktop.
Anything I can do to save the thread aside from the soulless text export? (which I’m grateful for, don’t get me wrong!)
Edit I tried a couple other threads that work, so it’s only the current one I’m on that’s messed up somehow. The only differences I can think of between it and the other threads are that I had added some styling in the character sheet, like a background and opacity to the text boxes. I also set user responses to respond as an imported character, instead of the default “user”.
No worries, thanks for your help!
Please let me know if you run into any other issues, since I’ve just deployed a fairly big update which overhauls the summary system, and fixed a few other issues. There are already some bug reports due to those new changes that people have submitted via the feedback button, but there aren’t enough details yet for me to track down the issue. Might have something to do with memory handling.
Is there a changelog somewhere I can read? I’m interested in learning more about how the memory and summaries are used. Like whether pruning duplicate memories would speed up response time, or how to keep the a.i. from bringing up the same (already resolved) issue over and over, lol.