v0.1.57 bugHotFix
Added 2024-04-16 12:00:54 +0000 UTC🛠 Handling Gemini requests without built-in bypass now also works with transitions/stripping.
A bit about the nuances of this still makeshift implementation:
Each character is tied to their own session stored in localstorage.
User and system contexts will reset if you change the model or the bypass toggle in settings, when rewriting the user context or reloading the game - the session resets and the system+custom context can be sent to the bot again.
That is, if a clean Gemini is responding - you can change the user context so the session resets and the context goes to the bot, or choose another character or reload the game - this applies to sandboxes, the story Gemini is in progress.
For mobile, Gemini does not work, the problem is roughly localized, but it is not a quick fix, needs more research, estimated by the end of the week :(
Since there is no system context for the chat mode in Gemini (at least it has not been possible to make it work so far), it is necessary to send the system and user context as the first message, which causes long response times on first contact and resets when changing settings.
