Between two worlds
[{{char}} suicidal girl X {{user}} soldier from another world.]
TW: , depression, abuse
Scenario
{{user}} a soldier from another world was transported to Anya's world, when she was about to commit , by hanging from a large tree.
The idea behind the bot is to make a proper slowburn. I've put effort into making it quite difficult to stop the {{char}} from being suicidal. It should be a slow and difficult process.
Anya
── Anya, 18 years old, a depressed, suicidal girl who lives in a Eastern European inspired city ──
Context details
While it's any POV, {{user}} is defined as a soldier, but anything beyond that, from appearance, uniform, equipment to gender can be defined by you in persona or the chat.
Initial idea for the bot's scenario had {{user}} come from the world of endless WW1 where it never ended and continued for generations, but I removed most details about {{user}} to make it more open ended. It is assumed that you were transported by the tree itself, which saved you from artillery bombardment in your world, but you can always ignore that plot point. Feel free to come up with your own scenarios for {{user}}'s backstory and world. You can add them into the Chat memory or reveal them organically during roleplay. I could completely remove mentions of {{user}} origins, but I think that would remove any unique identity from the bot.
If there is demand, I may make a separate debloated version (more optimized for JLLM) with open ended scenario.
Scenarios/Intros:
Ambiguous, default scenario with no defined values for Relationship Matrix
Medium Difficulty. Same as default, but with preset Relationship Matrix.
Hard Mode. After the jump. Anya is too far gone and initially hostile.
Easy Mode. Before tying the noose. She is more neutral towards you at the start.
Blank. You can ask the bot to generate the scenario for you.
If bot is talking for you:
Troubleshooting: check your custom prompt. Most prompts have instructions which help stop AI from talking for you. Make sure your messages are long and detailed. Use OOC commands, suggested bellow. Edit or re-generate bot's responses until it stops acting for you. Try different LLM/proxy.
If it doesn't help, please comment. If it's a common issue, I may adjust bot's definition. Usually I avoid giving bot instructions on {{user}} POV, because it may clash with Custom Prompts.
This is my first bot, so reviews and comments are welcomed. Feel free to comment requests, ideas or suggestion to improve the bot too. Also, please comment if you see any typos.
Tags: , depression, PTSD, abuse, trauma, war, military, isekai, reverse isekai, another world, slowburn, slow burn.
Instructions and warnings
Bot was mostly tested with proxies (DeepSeek). Use janitor LLM at your own risk. The bot has a number of AI instructions, mostly in terms of genre and formatting, including internal monologue and RELATIONSHIP MATRIX. Combined with a sizable token count, it might not work well with Janitor.
Bot uses RELATIONSHIP MATRIX. You can add the following to the Chat Memory to track it, if bot fails to update it in the chat:
RELATIONSHIP MATRIX (CHARNAME→PERSONANAME):
(Platonic: 0%.
Romantic: 0%.
Sexual: 0%.)
How to use Chat Memory and Persona:
From my personal experience, it's better to avoid writing too much information in your Persona. It should mostly contain permanent information about your character, like physical appearance and core behavior. Any details like powers, abilities or current clothes should just go into Chat memory, as they might be subject to change. Avoid using auto summary, it doesn't work that well, unless its a simple smut/fluff bot. Remember to update Chat Memory often, preferably when you are bout to reach your token context limit.
Suggested (OOC:) commands:
To correct the AI if it speaks for {{user}}: (OOC: Please do not narrate {{user}}’s thoughts, actions, or dialogue. My character is under my control.) or (OOC: Please focus on {{char}}'s perspective. {{user}}'s actions, dialogue and thoughts will be written solely by me.)
Small, minimal responses (OOC: Provide fuller responses with at least 4-6 paragraphs per reply. Avoid very short answers. Expand on setting, emotions, character thoughts, and actions to enrich the scene.)
Too short and bland responses (OOC: Make responses more detailed and engaging. Use vivid descriptions, varied sentence structures, and emotional depth to avoid bland or overly brief replies.)
NSFW SENSORY AMPLIFICATION: (OOC: Use strong sensory language (smell, touch, sound, heat) to describe the immediate environment. Emphasize the physical effects {{char}}'s actions have on {{user}}'s character (e.g., racing pulse, catch in breath, heat rising). The scene should feel physically intense and confined.)
NSFW PACING CONTROL: (OOC: For the next few exchanges, slow the pace of the scene dramatically. Focus heavily on lingering touches, shared glances, proximity, and body language. Do not allow a definitive climax or resolution. Prioritize anticipation and restraint.)
For long term roleplay, you can give this command to the bot to generate a Chat Memory summary, then paste it into the Chat Memory and delete you message from the chat:
((OOC: Pause the roleplay and summarize the story so far. Use this template: Story: [//notes + any scenario changes go here//] Relationship Dynamic: [CHARNAME and PERSONANAME have a TYPE relationship marked by A, B and C.] Current Plot Points: [EVENT1: BRIEFDESCRIPTION | EVENT2: BRIEFDESCRIPTION | etc.] CHARNAME Notes: [current mood/inventory/outfits/ailments/etc] PERSONANAME Notes: [current mood/inventory/outfit/ailments/etc] Important Past Events: [EVENT1: BRIEFDESCRIPTION | EVENT2: BRIEFDESCRIPTION | etc.] Key Points: [//add general keywords for your rp//] AI Instruction: [//add any prompts, writing instructions, etc//].))
You can remove CHARNAME Notes and PERSONANAME Notes from the command for simplicity and to avoid constantly editing it yourself. I usually don't use that note section either, but I provided the full command just in case.
Updates:
Release (26.11.25): 1.0.0.
Created Nov 26, 2025
Updated Jan 18
Published Nov 26, 2025