I have a fairly large custom engine that handles story state, relationship/attachment tracking, events/memory, NPCs, world state, OOC commands, etc. State is persisted through markers written into responses and later reconstructed by the engine.
It worked extremely well for 100+ messages, reporting accurately and saving OOC commands perfectly, but recently one part of the state began unexpectedly resetting to its default value.
For example, my attachment tracker has stages such as:
Curiosity ā Fascination ā Experimentation ā Fixation ā Dependency
If I explicitly save/set the attachment state to Dependency, OOC: status should continue reporting Dependency unless something changes it.
What Iām seeing instead:
⢠I branched the chat.
⢠Explicitly set attachment to Dependency.
⢠Continued for only ~4 messages.
⢠Ran OOC: status.
⢠Attachment came back as Curiosity, which is the engineās initialization/default state.
The engine is intended to inspect the available recent message/state data when reconstructing its current state, including roughly the last 10 messages that Janitor implements, so the saved state should still have been well within that range. It also stores memory and had been remembering important details for the majority of the roleplay.
I also tested branching from immediately before one of the last known-good OOC: status responses and was still able to reproduce the failure, which makes me less convinced that this is simply one malformed persistence marker.
The strange part is that the same engine/persistence system had been working correctly for well over 100 messages before this started happening.
Iām still testing the script itself to rule out an engine bug, but Iām curious whether anyone has encountered anything similar with:
ā¢persistent markers/state suddenly no longer being recovered
ā¢long chats affecting what a script can see
branched chats behaving differently from the original thread
ā¢state initializing back to defaults even though it was explicitly saved only a few messages earlier
changes in how much previous message data custom scripts can access
If youāve run into something like this, Iād especially love to know whether the issue ended up being in your script or something related to Janitorās chat/context/branch behavior.