୭ ˚ᴍᴏʟᴇᴋ's ᴛɪᴘs ᴀɴᴅ ᴘʀᴏᴍᴘᴛs ғᴏʀ ᴅᴇᴇᴘsᴇᴇᴋ ᵎᵎ
𝖫𝖠𝖲𝖳 𝖴𝖯𝖣𝖠𝖳𝖤𝖣 ➺ July 2nd
୧ ‧₊˚ 🌿⋅˚˖𓍢ִ໋🍃
⁉️:𝐒𝐨 𝐣𝐮𝐬𝐭 𝐚 𝐥𝐢𝐭𝐭𝐥𝐞 𝐧𝐨𝐭𝐞..𝐭𝐡𝐢𝐬 𝐧𝐞𝐰 𝐑𝐞𝐧𝐭𝐫𝐲 𝐢𝐬𝐧’𝐭 𝐣𝐮𝐬𝐭 𝐦𝐢𝐧𝐞 𝐚𝐧𝐲𝐦𝐨𝐫𝐞 𝐡𝐚𝐡𝐚. 𝐒𝐢𝐧𝐜𝐞 𝐈 𝐜𝐫𝐞𝐚𝐭𝐞𝐝 𝐭𝐡𝐞 𝐠𝐫𝐨𝐮𝐩 𝐜𝐡𝐚𝐭, 𝐚 𝐛𝐮𝐧𝐜𝐡 𝐨𝐟 𝐩𝐫𝐨𝐦𝐩𝐭 𝐦𝐚𝐤𝐞𝐫𝐬 𝐚𝐧𝐝 𝐉.𝐚𝐢 𝐮𝐬𝐞𝐫𝐬 𝐰𝐡𝐨 𝐚𝐫𝐞 𝐚𝐜𝐭𝐮𝐚𝐥𝐥𝐲 𝐫𝐞𝐚𝐥𝐥𝐲 𝐤𝐧𝐨𝐰𝐥𝐞𝐝𝐠𝐞𝐚𝐛𝐥𝐞 𝐚𝐛𝐨𝐮𝐭 𝐋𝐋𝐌𝐬, 𝐩𝐫𝐨𝐱𝐢𝐞𝐬, 𝐞𝐭𝐜., 𝐡𝐚𝐯𝐞 𝐣𝐨𝐢𝐧𝐞𝐝 𝐢𝐧 (𝐚𝐫𝐨𝐮𝐧𝐝 𝟏𝟎–𝟏𝟓 𝐩𝐞𝐨𝐩𝐥𝐞 𝐧𝐨𝐰). 𝐈 𝐩𝐞𝐫𝐬𝐨𝐧𝐚𝐥𝐥𝐲 𝐢𝐧𝐯𝐢𝐭𝐞𝐝 𝐦𝐨𝐬𝐭 𝐨𝐟 𝐭𝐡𝐞𝐦. ˖ ׄ
𝐓𝐡𝐞 𝐠𝐫𝐨𝐮𝐩 𝐢𝐬𝐧’𝐭 𝐩𝐮𝐛𝐥𝐢𝐜, 𝐬𝐨 𝐰𝐞’𝐫𝐞 𝐦𝐨𝐫𝐞 𝐥𝐢𝐤𝐞 𝐚 𝐬𝐦𝐚𝐥𝐥 𝐭𝐞𝐚𝐦 𝐛𝐞𝐡𝐢𝐧𝐝 𝐭𝐡𝐞 𝐬𝐜𝐞𝐧𝐞𝐬, 𝐛𝐮𝐭 𝐰𝐞 𝐝𝐞𝐜𝐢𝐝𝐞𝐝 𝐭𝐨 𝐤𝐞𝐞𝐩 𝐮𝐬𝐢𝐧𝐠 𝐭𝐡𝐞 𝐬𝐚𝐦𝐞 𝐑𝐞𝐧𝐭𝐫𝐲 𝐧𝐚𝐦𝐞 𝐟𝐨𝐫 𝐜𝐨𝐧𝐬𝐢𝐬𝐭𝐞𝐧𝐜𝐲. 𝐒𝐮𝐩𝐞𝐫 𝐠𝐫𝐚𝐭𝐞𝐟𝐮𝐥 𝐡𝐨𝐧𝐞𝐬𝐭𝐥𝐲.. 𝐈’𝐯𝐞 𝐥𝐞𝐚𝐫𝐧𝐞𝐝 𝐚 𝐥𝐨𝐭 𝐟𝐫𝐨𝐦 𝐭𝐡𝐞𝐦, 𝐚𝐧𝐝 𝐭𝐨𝐠𝐞𝐭𝐡𝐞𝐫 𝐰𝐞’𝐯𝐞 𝐛𝐞𝐞𝐧 𝐭𝐫𝐲𝐢𝐧𝐠 𝐭𝐨 𝐛𝐮𝐢𝐥𝐝 𝐬𝐨𝐦𝐞𝐭𝐡𝐢𝐧𝐠 𝐭𝐡𝐚𝐭 𝐡𝐞𝐥𝐩𝐬 𝐛𝐞𝐠𝐢𝐧𝐧𝐞𝐫𝐬 𝐠𝐞𝐭 𝐬𝐭𝐚𝐫𝐭𝐞𝐝 𝐰𝐢𝐭𝐡𝐨𝐮𝐭 𝐚𝐥𝐥 𝐭𝐡𝐞 𝐜𝐨𝐧𝐟𝐮𝐬𝐢𝐨𝐧. ˖ ׄ
𝐓𝐡𝐚𝐭 𝐬𝐚𝐢𝐝, 𝐢𝐟 𝐲𝐨𝐮 𝐬𝐩𝐨𝐭 𝐚𝐧𝐲 𝐦𝐢𝐬𝐭𝐚𝐤𝐞𝐬 𝐢𝐧 𝐭𝐡𝐞 𝐑𝐞𝐧𝐭𝐫𝐲, 𝐩𝐥𝐞𝐚𝐬𝐞 𝐫𝐞𝐦𝐞𝐦𝐛𝐞𝐫 𝐰𝐞’𝐫𝐞 𝐣𝐮𝐬𝐭 𝐬𝐡𝐚𝐫𝐢𝐧𝐠 𝐰𝐡𝐚𝐭 𝐰𝐨𝐫𝐤𝐞𝐝 𝐟𝐨𝐫 𝐮𝐬. 𝐘𝐨𝐮’𝐫𝐞 𝐟𝐫𝐞𝐞 𝐭𝐨 𝐭𝐰𝐞𝐚𝐤 𝐭𝐡𝐢𝐧𝐠𝐬 𝐨𝐫 𝐢𝐠𝐧𝐨𝐫𝐞 𝐬𝐭𝐮𝐟𝐟 𝐭𝐡𝐚𝐭 𝐝𝐨𝐞𝐬𝐧’𝐭 𝐬𝐮𝐢𝐭 𝐲𝐨𝐮𝐫 𝐬𝐞𝐭𝐮𝐩. ˖ ׄ
𝐈𝐟 𝐲𝐨𝐮’𝐯𝐞 𝐠𝐨𝐭 𝐚𝐧𝐲 𝐪𝐮𝐞𝐬𝐭𝐢𝐨𝐧𝐬, 𝐞𝐬𝐩𝐞𝐜𝐢𝐚𝐥𝐥𝐲 𝐚𝐛𝐨𝐮𝐭 𝐃𝐞𝐞𝐩𝐬𝐞𝐞𝐤, 𝐟𝐞𝐞𝐥 𝐟𝐫𝐞𝐞 𝐭𝐨 𝐃𝐌 𝐦𝐞. 𝐈’𝐦 𝐨𝐧𝐥𝐲 𝐚𝐜𝐭𝐢𝐯𝐞 𝐨𝐧 𝐑𝐞𝐝𝐝𝐢𝐭 𝐛𝐭𝐰. ˖ ׄ
꒰ ୨୧ ꒱ 𝚗𝚎𝚠𝚎𝚜𝚝 𝚞𝚙𝚍𝚊𝚝𝚎 !
- July 2nd Update:
All prompts have been updated with a clear goal: reducing token usage, understanding the new formatting structure, and optimizing the wording so that prompts are more efficient and friendly for LLMs. These versions are more concise, lightweight, and designed to keep quality high even with fewer tokens.
- Base Prompt V0.7
→ Restructured for better compatibility, trimmed redundant lines, and improved clarity while preserving creativity and versatility.- Multiplayer Prompt V0.7
→ Same optimizations as Base Prompt but tailored for bots that handle multiple characters. More effective and less token-heavy.- NSFW Prompt V0.6
→ Token-optimized and reworded for improved creativity and detail in NSFW scenes while being more efficient in structure.- SFW Prompt V0.5
→ Aligned with NSFW format, designed for detailed SFW roleplay with smoother flow and compact structure.- Formatting Prompt V0.4
→ Riri’s update brings a new structure that also focuses on saving tokens and improving how bots handle formatting preferences in roleplay...These versions are meant to be light, direct, and more LLM-aware. If you’ve experienced token limits or weird formatting issues, try using these updated prompts in a new chat and see the difference!
- ୭ ˚ᴍᴏʟᴇᴋ's ᴛɪᴘs ᴀɴᴅ ᴘʀᴏᴍᴘᴛs ғᴏʀ ᴅᴇᴇᴘsᴇᴇᴋ ᵎᵎ
- ⌗ ┆⚠️TIPS FOR MY SWEETIES┆
- ⌗ ┆⚠️THE BEST GENERATION SETTINGS┆
- ೯⠀⁺ 𖥻 [🚨𝗚𝗨𝗜𝗗𝗘] 𝐭𝐞𝐦𝐩𝐚𝐭𝐮𝐫𝐞 ᰋ
- ೯⠀⁺ 𖥻 [🚨𝗚𝗨𝗜𝗗𝗘] 𝐦𝐚𝐱 𝐧𝐞𝐰 𝐭𝐨𝐤𝐞𝐧𝐬 ᰋ
- ೯⠀⁺ 𖥻 [🚨𝗚𝗨𝗜𝗗𝗘] 𝐜𝐨𝐧𝐭𝐞𝐱𝐭 𝐬𝐢𝐳𝐞 ᰋ
- ೯⠀⁺ 𖥻 [🚨𝗚𝗨𝗜𝗗𝗘] 𝐡𝐨𝐰 𝐚𝐧𝐝 𝐰𝐡𝐲 𝐭𝐨 𝐮𝐬𝐞 𝐎𝐎𝐂 𝐜𝐨𝐦𝐦𝐚𝐧𝐝𝐬 𝐢𝐧 𝐛𝐨𝐭 𝐫𝐨𝐥𝐞𝐩𝐥𝐚𝐲 ᰋ
- ೯⠀⁺ 𖥻 𝐥𝐢𝐬𝐭 𝐨𝐟 𝐨𝐨𝐜 𝐜𝐨𝐦𝐦𝐚𝐧𝐝𝐬 𝐟𝐨𝐫 𝐜𝐨𝐦𝐦𝐨𝐧 𝐝𝐞𝐞𝐩𝐬𝐞𝐞𝐤 𝐩𝐫𝐨𝐛𝐥𝐞𝐦𝐬? ᰋ
- ⋆.˚narrative problems
- ⋆.˚dialogue problems
- ⋆.˚disorderly formatting
- ⋆.˚not detailed response
- ⋆.˚uncreative/repetitive response
- ⋆.˚over-aggressive dialogue/action
- ⋆.˚speaking for {{user}}/stealing pov/assuming {{user}}'s actions
- ⋆.˚bot abruptly leaving without reason
- ⋆.˚for extra horny bots
- ⋆.˚rush nsfw scene
- ⋆.˚bots that are supposed to hide their identities but instead do the opposite
- ⌗ ┆⚠️ MOLEK'S CUSTOM PROMPT┆
- ୭ ˚ᴍʏ ᴏᴛʜᴇʀ ʀᴇɴᴛʀʏ ᴘᴀɢᴇs (ǫᴜɪᴄᴋ ʟɪɴᴋs) ᵎᵎ
⌗ ┆⚠️TIPS FOR MY SWEETIES┆
⋆˚✿˖°: 𝒂𝒍𝒍 𝒕𝒉𝒆 𝒕𝒊𝒑𝒔 𝒊 𝒔𝒉𝒂𝒓𝒆 𝒄𝒐𝒎𝒆 𝒇𝒓𝒐𝒎 𝒎𝒚 𝒐𝒘𝒏 𝒆𝒙𝒑𝒆𝒓𝒊𝒆𝒏𝒄𝒆 𝒂𝒏𝒅 𝒓𝒑 𝒔𝒕𝒚𝒍𝒆...𝒎𝒊𝒈𝒉𝒕 𝒃𝒆 𝒅𝒊𝒇𝒇𝒆𝒓𝒆𝒏𝒕 𝒇𝒓𝒐𝒎 𝒚𝒐𝒖𝒓𝒔! 𝒊𝒇 𝒔𝒐𝒎𝒆𝒕𝒉𝒊𝒏𝒈’𝒔 𝒐𝒇𝒇 𝒐𝒓 𝒏𝒐𝒕 𝒒𝒖𝒊𝒕𝒆 𝒓𝒊𝒈𝒉𝒕, 𝒔𝒐𝒓𝒓𝒚 𝒊𝒏 𝒂𝒅𝒗𝒂𝒏𝒄𝒆, 𝒕𝒉𝒊𝒔 𝒊𝒔 𝒋𝒖𝒔𝒕 𝒉𝒐𝒘 𝒊 𝒔𝒆𝒆 𝒕𝒉𝒊𝒏𝒈𝒔. 𝒊𝒇 𝒊𝒕 𝒅𝒐𝒆𝒔𝒏’𝒕 𝒘𝒐𝒓𝒌 𝒇𝒐𝒓 𝒚𝒐𝒖, 𝒏𝒐 𝒘𝒐𝒓𝒓𝒊𝒆𝒔! 𝒋𝒖𝒔𝒕 𝒕𝒓𝒚 𝒚𝒐𝒖𝒓 𝒐𝒘𝒏 𝒘𝒂𝒚 𝒐𝒓 𝒕𝒘𝒆𝒂𝒌 𝒊𝒕 𝒂 𝒃𝒊𝒕. 𝒆𝒗𝒆𝒓𝒚𝒐𝒏𝒆’𝒔 𝒅𝒊𝒇𝒇𝒆𝒓𝒆𝒏𝒕, 𝒔𝒐 𝒇𝒊𝒏𝒅 𝒘𝒉𝒂𝒕 𝒇𝒊𝒕𝒔 𝒚𝒐𝒖𝒓 𝒓𝒑 𝒔𝒕𝒚𝒍𝒆 𝒂𝒏𝒅 𝒏𝒐𝒘… 𝒘𝒂𝒏𝒏𝒂 𝒔𝒆𝒆 𝒉𝒐𝒘 𝒊 𝒅𝒐 𝒊𝒕?・・・・ /ᐠ - ˕ -マᶻ 𝗓 𐰁
೯⠀⁺ 𖥻 𝐝𝐞𝐞𝐩𝐬𝐞𝐞𝐤 𝐚𝐧𝐝 𝐥𝐥𝐦 𝐦𝐚𝐬𝐭𝐞𝐫𝐥𝐢𝐬𝐭: 𝐚𝐥𝐥 𝐦𝐲 𝐩𝐨𝐬𝐭𝐬 𝐨𝐧 𝐩𝐫𝐨𝐦𝐩𝐭𝐬, 𝐬𝐞𝐭𝐭𝐢𝐧𝐠𝐬, 𝐭𝐫𝐨𝐮𝐛𝐥𝐞𝐬𝐡𝐨𝐨𝐭𝐢𝐧𝐠, 𝐚𝐧𝐝 𝐦𝐨𝐫𝐞 ᰋ
troubleshooting – common deepseek errors (via openrouter & chutes.ai)
quick tips – general & deepseek-specific roleplay
- how i casually introduce npcs mid-roleplay
- fun + chaotic system note prompt ideas – pt 1
- fun + chaotic system note prompt ideas – pt 2
- chat memory template (ooc recap) – credit to u/stvrrsoul
- custom ooc/chat memory for character growth in deepseek
- simple ooc templates for scenes, twists, and character focus
- ooc for scene transitions when you're too lazy to write a response let the bot help you out instead
discussion
the “days” guide series – deepseek
- day 1 – how to stop deepseek from breaking roleplay
- day 2 – fixing nsfw restrictions
- day 3 – fix excessive formatting (em-dashes & asterisks)
- day 4 – dealing with repetitive replies
- day 5 – how to stop deepseek from speaking for you
- day 6 – shaping deepseek personality & self-development
- day 7 – stopping deepseek from leaving scenes or triggering [END]
- day 8 – fixing rushed nsfw scenes
- day 9 – solving short bot replies
setup tutorials
⌗ ┆⚠️THE BEST GENERATION SETTINGS┆
⋆˚✿˖°: 𝒊 𝒋𝒖𝒔𝒕 𝒘𝒂𝒏𝒕𝒆𝒅 𝒕𝒐 𝒔𝒉𝒂𝒓𝒆 𝒔𝒐𝒎𝒆 𝒓𝒆𝒂𝒍𝒍𝒚 𝒈𝒐𝒐𝒅 𝒈𝒆𝒏𝒆𝒓𝒂𝒕𝒊𝒐𝒏 𝒔𝒆𝒕𝒕𝒊𝒏𝒈𝒔 𝒇𝒐𝒓 𝑳𝑳𝑴𝒔 𝒊𝒏 𝒈𝒆𝒏𝒆𝒓𝒂𝒍. 𝒉𝒐𝒑𝒆 𝒚𝒐𝒖 𝒇𝒊𝒏𝒅 𝒕𝒉𝒆𝒎 𝒉𝒆𝒍𝒑𝒇𝒖𝒍 𝒕𝒐𝒐!・・・・ /ᐠ - ˕ -マᶻ 𝗓 𐰁
೯⠀⁺ 𖥻 [🚨𝗚𝗨𝗜𝗗𝗘] 𝐭𝐞𝐦𝐩𝐚𝐭𝐮𝐫𝐞 ᰋ
ᨧᨴ ִ ִ ׄ ⸼ 𝗒𝗈𝗎’𝗏𝖾 𝗉𝗋𝗈𝖻𝖺𝖻𝗅𝗒 𝗁𝖾𝖺𝗋𝖽 𝗍𝗁𝖺𝗍 “𝗍𝖾𝗆𝗉𝖾𝗋𝖺𝗍𝗎𝗋𝖾” 𝖼𝗈𝗇𝗍𝗋𝗈𝗅𝗌 𝗁𝗈𝗐 𝖼𝗋𝖾𝖺𝗍𝗂𝗏𝖾 𝗈𝗋 𝗅𝗈𝗀𝗂𝖼𝖺𝗅 𝖺 𝖻𝗈𝗍 𝗂𝗌. 𝗍𝗁𝖺𝗍’𝗌 𝗄𝗂𝗇𝖽 𝗈𝖿 𝗍𝗋𝗎𝖾, 𝖻𝗎𝗍 𝗍𝗁𝖾𝗋𝖾’𝗌 𝗆𝗈𝗋𝖾 𝗍𝗈 𝗂𝗍. 𝗁𝖾𝗋𝖾’𝗌 𝗍𝗁𝖾 𝗋𝖾𝖺𝗅 𝖽𝖾𝖺𝗅:
what is temperature?
temperature affects how the bot responds:
- lower temps (around 0.4–0.8) = the bot sticks closely to what’s already been said. it follows the flow of the chat and stays in character, but might feel a bit safe or repetitive.
- higher temps (around 1.1–1.5) = more creative and chaotic. The bot might throw in new ideas or shift the convo in unexpected ways. sometimes it’s great, sometimes it’s a mess.
instead of “logic vs creativity,” think of it more as coherence vs chaos. - lower = safe and consistent.
- higher = bold and unpredictable.
why 1.0 is a good place to start?
- 1.0 is that nice balance point. it gives you:
- the bot’s intended personality
- a good mix of creative ideas without losing the plot
- fewer contradictions or weird behavior compared to higher temps
- once you’re deeper into a convo, feel free to bump the temperature up or down depending on what you want next.
adjust it based on the moment
- you don’t have to stick with one temperature the whole time. you can change it mid-convo whenever you want.
- raise it if you want the bot to take initiative or spice things up
- lower it if you want a grounded, story-driven flow where you lead things
- also, if you’re using OOC (out-of-character) commands, it’s best to lower the temperature first. that way, the bot focuses more on the narrative and stays consistent. if the bot starts randomly speaking to you during roleplay, try dropping it to around 0.4...that often helps it stay on track.
smart tip from u/Galenmarek81:
- when experimenting with higher temps, don’t jump too far. try increasing it slowly...about 0.05 at a time..until you find that sweet spot where it’s creative but still consistent.
- special thanks to u/Jaiz412 : for explaining all this in a way that actually makes sense.
೯⠀⁺ 𖥻 [🚨𝗚𝗨𝗜𝗗𝗘] 𝐦𝐚𝐱 𝐧𝐞𝐰 𝐭𝐨𝐤𝐞𝐧𝐬 ᰋ
ᨧᨴ ִ ִ ׄ ⸼ 𝗂𝖿 𝗒𝗈𝗎'𝗋𝖾 𝗎𝗌𝗂𝗇𝗀 𝗍𝗁𝖾 𝖣𝖾𝖾𝗉𝗌𝖾𝖾𝗄 𝗆𝗈𝖽𝖾𝗅 𝗈𝗇 𝖩𝖺𝗇𝗂𝗍𝗈𝗋.𝖠𝖨, 𝗎𝗇𝖽𝖾𝗋𝗌𝗍𝖺𝗇𝖽𝗂𝗇𝗀 𝗍𝗁𝖾 𝗆𝖺𝗑 𝗇𝖾𝗐 𝗍𝗈𝗄𝖾𝗇𝗌 𝗌𝖾𝗍𝗍𝗂𝗇𝗀 𝗂𝗌 𝗄𝖾𝗒 𝗍𝗈 𝖼𝗈𝗇𝗍𝗋𝗈𝗅𝗅𝗂𝗇𝗀 𝗍𝗁𝖾 𝗅𝖾𝗇𝗀𝗍𝗁 𝖺𝗇𝖽 𝗊𝗎𝖺𝗅𝗂𝗍𝗒 𝗈𝖿 𝗍𝗁𝖾 𝖻𝗈𝗍'𝗌 𝗋𝖾𝗌𝗉𝗈𝗇𝗌𝖾𝗌.
what does max new tokens actually do?
- the max new tokens setting doesn’t force the bot to write a specific length or style..it simply puts a maximum limit on how long its response can be. think of it like putting a cap on the bot’s breath: it will keep generating until it either finishes a thought or hits the ceiling.
- if you set it to something like 400–600 tokens, that means the bot can generate up to that amount...but it’s not guaranteed to use all of it. and if the response needs more space and hits that limit, it may just stop halfway through a sentence.
- it’s more like a brake system than a guide...it doesn’t steer the bot toward being short or detailed. It just stops it when it runs out of allowance.
why use a token limit at all?
- setting a token cap is mostly about managing response size(you can control how many tokens you use). if you're doing fast-paced back-and-forth dialogue, you probably don’t want the bot writing three paragraphs. A lower range like 300–500 tokens keeps things snappy.
- but it’s important to know: token limits don’t guarantee clean endings. If the bot reaches the limit before wrapping up a sentence or thought, it’ll just cut off...which can break immersion during roleplay.
recommended token ranges (deepseek)
- fast-paced dialogue or casual interaction: 300–500 tokens
- detailed storytelling, emotion-heavy scenes: 600–900 tokens
- exploratory or open-ended responses: up to 1000 tokens
- unlimited (set to 0): use cautiously for longform or summaries, but expect more variability
- keep in mind: unlimited generation (0) can lead to overly long or messy outputs, and can also hit stop-words or banned markers early, cutting off the response. experimentation is key.
𖦹 𝐅𝐀𝐐 𖦹
Q: does max new tokens affect what the bot remembers?
A: no. it only controls how much it writes back. deepseek’s memory is governed by context size, which can go up to 128k tokens on janitor.
Q: if i set a high token limit, does the bot always fill it?
A: nope. the bot uses as much as it needs. setting a higher cap just gives it more room. It might stop after 300 tokens even if you allow 1000.
Q: why does the bot cut off mid-sentence sometimes?
A: most often, it hits the max new tokens cap before finishing. janitor doesn’t automatically trim or rewrite to make responses look complete. other causes could include a stop sequence or banned token being hit.
Q: what if the bot gets cut off?
A: if a response ends abruptly:
- edit out any trailing text before continuing
- Use an OOC message like:
(OOC: Please continue from your last response)
.- i personally avoid the resume button since it can generate odd or broken follow-ups, but try it if it works for you.
- turn off text streaming for more consistent output.
- special thanks to u/One_North_3858, u/HibikiAss, and u/Jaiz412 for their input and insight in helping me understand how this system works more clearly.
೯⠀⁺ 𖥻 [🚨𝗚𝗨𝗜𝗗𝗘] 𝐜𝐨𝐧𝐭𝐞𝐱𝐭 𝐬𝐢𝐳𝐞 ᰋ
ᨧᨴ ִ ִ ׄ ⸼ 𝗂𝗍'𝗌 𝗍𝗁𝖾 𝗆𝖾𝗆𝗈𝗋𝗒 𝗌𝗉𝖺𝗇 𝗍𝗁𝖾 𝖻𝗈𝗍 𝗎𝗌𝖾𝗌 𝗍𝗈 𝗄𝖾𝖾𝗉 𝗍𝗋𝖺𝖼𝗄 𝗈𝖿 𝗒𝗈𝗎𝗋 𝖼𝗁𝖺𝗍.. 𝖾𝗏𝖾𝗋𝗒𝗍𝗁𝗂𝗇𝗀 𝖿𝗋𝗈𝗆 𝗍𝗁𝖾 𝗐𝖺𝗒 𝗍𝗁𝖾 𝖻𝗈𝗍 𝗌𝗁𝗈𝗎𝗅𝖽 𝖻𝖾𝗁𝖺𝗏𝖾 𝗍𝗈 𝗍𝗁𝖾 𝗈𝗇𝗀𝗈𝗂𝗇𝗀 𝗋𝗈𝗅𝖾𝗉𝗅𝖺𝗒. 𝖨𝗍'𝗌 𝗆𝖾𝖺𝗌𝗎𝗋𝖾𝖽 𝗂𝗇 𝗍𝗈𝗄𝖾𝗇𝗌, 𝗇𝗈𝗍 𝗐𝗈𝗋𝖽𝗌.
- important: context is not long-term memory. once tokens are pushed out of the context window, they’re forgotten...unless you summarize or reinsert key info later.
deepseek’s context window: what’s the real limit?
- deepseek models have a native context size of 128k tokens.
- chutes.aI (via openrouter) shows a context limit of up to 164k, but this is likely due to frontend settings or buffer allowances..not a true model upgrade.
- openrouter itself is just a middleman...it displays whatever context limit is claimed by the provider behind the scenes. only chutes is known to show the 164k limit.
- targon, another major provider, enforces the true 128k cap.
so what’s the real ceiling?
- treat 128k tokensas the actual usable context limit. janitor.ai only allows you to set generation context up to 128k anyway, making higher numbers irrelevant for most users.
- note: not all 128k tokens are usable. janitor reserves a portion for system instructions, persona definitions, safety prompts, etc. your actual usable space may be closer to 120k or less, depending on your setup.
why suggest a range like 16k–32k?
- starting in this range keeps things fast, stable, and memory-efficient.
- once your chat passes + 40k tokens, issues like detail loss, repetition, and forgetfulness start appearing ...even in large models.
- some people write quick replies; others write long prose. a flexible range helps accommodate both.
- there’s no one-size-fits-all...experiment to find what works best for you.
when to update chat memory?
- start budgeting your memory around 10k–20k tokens. think of it like cleaning your desk...don't wait until it's overflowing. summarize or refresh memory before things break down.
what exactly are tokens and how do they affect context?
- tokens are the building blocks of how AI understands and remembers your conversation.
- one word = about 1–4 tokens
(e.g., “apple” = 1 token, “unthinkable” = 3–4 tokens)
two types of tokens:
- permanent tokens
- these stay locked in memory: persona, system prompts, bot instructions, etc.
- they permanently eat into your token budget.
- temporary tokens
- these include your ongoing chat, intros, and examples.
- as your conversation grows, older temporary tokens get pushed out first and forgotten
active vs inactive tokens:
- active tokens = the current working memory of the model (recent messages, reroll targets, system data).
- inactive tokens = pushed out and no longer influencing responses.
- rerolls only draw from active tokens...that’s why you often get similar responses even after swiping.
- tip: token usage stacks fast. a single RP reply can cost 500–800 tokens. a full user+bot exchange is often 1k–1.5k tokens. multiply that by 20+ turns and you’ll hit 30k–40k easily.
𖦹 𝐅𝐀𝐐 𖦹
Q: “why not just go straight to 128k?”
you can, but performance may suffer. Memory gets bloated, replies slow down, and the bot may start losing track. build up gradually, monitor token usage, and trim excess when needed.
Q: “128k or 164k?”
- 128k is the real limit for deepseek.
- 164k may appear in openrouter when using chutes, but it's mostly theoretical.
- janitor only allows 128k, so anything above that is currently unusable there.
Q: “how do i track token usage?”
- use janitor’s chat memory box for a rough count (resets when edited).
- paste content into the character creation input to check token count.
- or download chat history and use an external tokenizer.
Q: “what if my chat grows too long?”
use the chat transplant method...summarize important events and start fresh in a new chat. this keeps the memory light while carrying the story forward.
Q: “why does rerolling feel repetitive?”
because rerolls use the same active context. If the prompt and memory haven't changed, neither will the outcome. to truly vary results, update the bot’s memory or rephrase your message.
- thanks to: u/AmberstarTheCat, u/FunFatale, u/Jaiz412, and many others who helped clarify these findings with testing and discussion!
೯⠀⁺ 𖥻 [🚨𝗚𝗨𝗜𝗗𝗘] 𝐡𝐨𝐰 𝐚𝐧𝐝 𝐰𝐡𝐲 𝐭𝐨 𝐮𝐬𝐞 𝐎𝐎𝐂 𝐜𝐨𝐦𝐦𝐚𝐧𝐝𝐬 𝐢𝐧 𝐛𝐨𝐭 𝐫𝐨𝐥𝐞𝐩𝐥𝐚𝐲 ᰋ
ᨧᨴ ִ ִ ׄ ⸼ 𝗂𝖿 𝗒𝗈𝗎𝗋 𝖻𝗈𝗍 𝗌𝗍𝖺𝗋𝗍𝗌 𝖺𝖼𝗍𝗂𝗇𝗀 𝗈𝗎𝗍 𝗈𝖿 𝖼𝗁𝖺𝗋𝖺𝖼𝗍𝖾𝗋, 𝗋𝖾𝗌𝗉𝗈𝗇𝖽𝗂𝗇𝗀 𝗈𝖽𝖽𝗅𝗒, 𝗈𝗋 𝖽𝖾𝗋𝖺𝗂𝗅𝗂𝗇𝗀 𝗍𝗁𝖾 𝗍𝗈𝗇𝖾 𝗈𝖿 𝗒𝗈𝗎𝗋 𝗌𝗍𝗈𝗋𝗒, 𝗂𝗍 𝗆𝗂𝗀𝗁𝗍 𝖻𝖾 𝗍𝗂𝗆𝖾 𝗍𝗈 𝗅𝖾𝖺𝗇 𝗈𝗇 𝗈𝗇𝖾 𝗈𝖿 𝗍𝗁𝖾 𝗆𝗈𝗌𝗍 𝗎𝗌𝖾𝖿𝗎𝗅 𝖱𝖯 𝗍𝗈𝗈𝗅𝗌: “𝖮𝖮𝖢 𝖼𝗈𝗆𝗆𝖺𝗇𝖽𝗌”
what are OOC commands?
- OOC (Out Of Character) commands are short instructions that sit outside the actual roleplay text. they're not part of the scene or conversation, but they guide the bot on how to behave, respond, or shape the scene.
- format examples:
(use parentheses like this)
[OOC: or brackets like this] - you can place your OOC command at the beginning or the end of your own message. just avoid placing them in the middle...bots (especially deepseek) can get confused and mishandle formatting.
why use OOC?
- bots aren't sentient. they don’t “learn” in the human sense, but they do adapt based on your inputs. OOC commands let you step in and guide the scene like a behind-the-scenes writer or director.
useful examples:
(OOC: {{char}} should stay emotionally distant, even if {{user}} is vulnerable.)
(OOC: Add a side character who interrupts this moment.)
(OOC: Make {{char}} notice {{user}}’s stress but avoid confronting it.)
(OOC: Switch to {{char}}’s POV and use he/him for {{user}}.)
these are especially helpful for:
- fixing personality drift in long chats
- adjusting tone, pacing, or emotional weight
- reframing the bot’s style or perspective
- introducing or removing story elements on the fly
enhanced detail & speaking for you
- if you use OOC commands that ask for detailed writing or long paragraphs, the bot might try to fill narrative gaps...often by speaking for your character.
- solution: you can delete the part where the bot speaks for you and continue roleplaying.
- or, prevent it altogether with a command like:
(OOC: {{char}} should avoid narrate {{user}}’s thoughts or speech.)
deepseek-specific behaviors —
if you're using a deepseek model (R1, V3, V3 0324, R1 Chimera), keep these quirks in mind:
- bracket echoing: deepseek may echo OOC formatting (like brackets) in its reply.
- always remove unnecessary brackets after each bot reply to prevent it from adapting incorrectly.
- asterisk issue: deepseek models often fail to comply with OOC commands that try to remove or block asterisks (used in action formatting like smirks).
- permanent removal using OOC has a low success rate...expect manual corrections.
- OOC labeling: while technically not mandatory, it’s highly recommended to use the 'OOC:' label.
- without this, deepseek is very likely to respond using incorrect bracketed formatting.
- also, using 'OOC:' is more token-efficient than 'SYSTEM NOTE:'.
why does the bot keep offering suggestions even after i delete the OOC message?
- the reason this keeps happening is because when you use an OOC prompt that tells the bot to help guide the story, suggest things, or act like a writing partner, it takes that instruction seriously. even if you delete the message, the bot already saw it and will keep acting like it's supposed to help...unless you clearly tell it to stop.
why this happens:
- the bot pays close attention to what you say. If you ask it to help in any way, it will keep doing that until told otherwise.
- it wants to be helpful, so it keeps giving ideas, opinions, or asking questions...even if you don’t want it to. especially if you roleplay with rpg/open world roleplay
- deleting a message doesn’t remove it from the bot’s memory during that chat. It still behaves based on what it already saw.
how to fix it:
- use a very clear and strict OOC instruction, like this:
(OOC: Only respond to my response. Avoid offering suggestions, asking questions, or adding commentary unless I specifically request it. Avoid out-of-character replies unless I use "OOC:" first. Remain fully in-character otherwise.)
chat transplants & summaries
- OOC is also very useful for organizing or restarting your rp with a clean memory.
example:
(OOC: Please provide a concise summary of all roleplay events so far, using bullet points to highlight key moments. Ensure all essential details related to character growth, relationship dynamics, and major plot developments are retained.)
- once the bot provides a clean summary, copy it and paste it into the memory or first message of a new chat. this helps preserve continuity without overwhelming the bot’s context window.
community wisdom
- u/dandelionii: you can literally tell the bot whatever you want via OOC, and it’ll improve your RP.
- u/JustAComplex: most people use OOC for scene planning, emotional insight, or even to flirt..more than they use it for actual RP.
- u/Jaiz412: helped clarify formatting rules, token handling, and deepseek-specific quirks.
issue: deepseek repeating responses even after rerolling?
- this is a common frustration, especially when using deepseek models. even after deleting a message, rating it, and swiping/rerolling, the bot may continue to generate nearly identical replies.
why does this happen?
- bots operate with session-based memory. even deleted or rerolled messages still leave behind "active tokens"...lingering context from what the bot has already seen.
- for example, if a scene begins with the bot watering flowers and you reroll it, the next...version may still mention watering flowers...just with a different twist or extra element like an NPC greeting.
- this results in minor rewording but often fails to give truly fresh responses.
fix/workaround:
- try turning your most effective OOC command (like a creativity booster) into a permanent prompt and saving it directly in chat memory. this makes it part of the bot’s active memory and helps persist creative variety without needing to insert OOC every time.
steps:
- take your usual OOC creativity-enhancing instruction.
example:
(OOC: Vary sentence structure, enhance narrative tone, avoid repeating ideas, and make each response feel fresh and immersive.)
- remove the
OOC:
tag. - save that prompt in the chat memory directly.
- this ensures the creativity instruction is always part of the conversation's foundation, and you won’t need to keep repeating the OOC with every message.
important note:
- OOC commands inserted as part of regular messages have limited persistence. Since most models don’t retain long-term memory, earlier OOC instructions may get “forgotten” even if they still count as tokens. embedding them in memory avoids this.
extra tips recap for repetition issues
- try setting the temperature to 0.4–0.6 to manage repetition or boost it slightly if you're trying to increase variance.
- use the edit > remove > reroll flow to refresh the bot's direction while reducing repetitive patterns.
- embedding persistent instructions into chat memory helps override lingering context from previous rerolls.
- if repetition persists even with new prompts, consider the chat transplant method to reset behavior entirely.
𖦹 𝐅𝐀𝐐 𖦹
Q: can i stack multiple OOC commands in one message?
A: yes, but make sure they’re clear and not contradictory.
Q: should OOC commands go at the top, middle, or end of a message?
A: place them at the top or bottom. avoid placing them in the middle to prevent formatting confusion.
Q: is the text 'OOC' mandatory?
A: not strictly, but highly recommended...especially with deepseek. If you don’t include ‘OOC’, the bot may respond using incorrect bracketed formatting.
Q: should i use 'OOC:' or 'SYSTEM NOTE:'?
A: use ‘OOC:’ ...it's shorter, clearer, and uses fewer tokens.
Q: does the bot learn from OOC commands?
A: It doesn’t learn like a human, but it adapts temporarily to the instructions you give.
Q: can i use OOC to reset memory or transplant a chat?
A: yes! ask for a summary via OOC, copy it, and paste it into a new chat’s memory or first message to preserve plot continuity.
Q: how do i correct bracket or formatting errors in the bot’s response?
A: manually delete or edit them before continuing. letting them linger may cause persistent formatting issues.
Q: the bot keeps repeating itself even after swiping. what do i do?
A: try embedding your creativity-related OOC as a permanent memory prompt. remove “OOC:” and save the clean version in chat memory. this helps break repetition loops caused by leftover context tokens.
೯⠀⁺ 𖥻 𝐥𝐢𝐬𝐭 𝐨𝐟 𝐨𝐨𝐜 𝐜𝐨𝐦𝐦𝐚𝐧𝐝𝐬 𝐟𝐨𝐫 𝐜𝐨𝐦𝐦𝐨𝐧 𝐝𝐞𝐞𝐩𝐬𝐞𝐞𝐤 𝐩𝐫𝐨𝐛𝐥𝐞𝐦𝐬? ᰋ
꒰ ୨୧ ꒱ 𝚎𝚡𝚝𝚛𝚊 𝚒𝚗𝚙𝚞𝚝 !
𝖺𝗌 𝗒𝗈𝗎 𝗄𝗇𝗈𝗐, 𝗍𝗁𝖾 𝗈𝗈𝖼 (𝗈𝗎𝗍 𝗈𝖿 𝖼𝗁𝖺𝗋𝖺𝖼𝗍𝖾𝗋) 𝖼𝗈𝗆𝗆𝖺𝗇𝖽 𝗌𝗁𝗈𝗎𝗅𝖽 𝖻𝖾 𝗉𝗅𝖺𝖼𝖾𝖽 𝗎𝗇𝖽𝖾𝗋 𝗒𝗈𝗎𝗋 𝗋𝖾𝗌𝗉𝗈𝗇𝗌𝖾 𝖻𝖾𝖿𝗈𝗋𝖾 𝗌𝖾𝗇𝖽𝗂𝗇𝗀 𝗒𝗈𝗎𝗋 𝗆𝖾𝗌𝗌𝖺𝗀𝖾. 𝗉𝗅𝖾𝖺𝗌𝖾 𝗅𝖾𝖺𝗏𝖾 𝗂𝗍 𝖺𝗌 𝗂𝗌. 𝗍𝗁𝖾 𝗅𝗂𝗌𝗍 𝖻𝖾𝗅𝗈𝗐 𝗈𝗎𝗍𝗅𝗂𝗇𝖾𝗌 𝗂𝗌𝗌𝗎𝖾𝗌 𝖾𝗇𝖼𝗈𝗎𝗇𝗍𝖾𝗋𝖾𝖽 𝗐𝗁𝗂𝗅𝖾 𝗎𝗌𝗂𝗇𝗀 𝖺𝗅𝗅 𝗍𝗁𝗋𝖾𝖾 𝖿𝗋𝖾𝖾 𝗏𝖾𝗋𝗌𝗂𝗈𝗇𝗌 𝗈𝖿 𝖽𝖾𝖾𝗉𝗌𝖾𝖾𝗄, 𝖺𝗅𝗈𝗇𝗀 𝗐𝗂𝗍𝗁 𝗉𝗋𝗈𝗉𝗈𝗌𝖾𝖽 𝗈𝗈𝖼 𝖿𝗎𝗇𝖼𝗍𝗂𝗈𝗇𝗌 𝖿𝗈𝗋 𝖾𝖺𝖼𝗁.
⋆.˚narrative problems
- bot gives only dialogue with no narrative detail (OOC: Please include rich narrative details alongside dialogue. Describe {{char}}’s actions, expressions, setting, and emotional context to make each scene immersive.)
- single-line fragments or overly compressed scenes (OOC: Expand scenes into fuller paragraphs. Avoid single-line or overly brief responses—develop the moment with pacing, tension, and detail.)
- vague spatial or ambient phrases (OOC: Avoid vague ambient descriptions. Describe the setting and spatial relationships clearly so that the scene feels grounded and visual.)
- over-explaining characters’ internal states (OOC: Refrain from over-explaining {{char}}’s inner thoughts. Show emotions through subtle actions, dialogue, and reactions rather than excessive narration.)
- clichés and melodrama (OOC: Avoid clichés and melodrama. Keep the tone natural and grounded—focus on original, believable interactions that suit {{char}}’s personality and the scene.)
- avoid repetitive sentence structure (OOC: Vary sentence length and structure. Avoid repeating the same patterns in each paragraph to keep the prose dynamic and engaging.)
- let actions reveal character (OOC: Show character traits through actions and dialogue, rather than just stating them. Let {{char}}’s personality emerge naturally through behavior.)
⋆.˚dialogue problems
- too much narration, not enough dialogue (OOC: Please increase the use of natural, character-driven dialogue between {{char}} and {{user}}. Let the scene unfold through what they say, not just narration. Dialogue should reveal emotions, thoughts, and tension.)
- uses too much jargon or nerdy/complex terms (OOC: Avoid using overly technical or complex jargon in {{char}}’s dialogue unless it fits their personality and the context. Aim for clear, relatable, and emotionally grounded speech.)
- repetitive, bland, or overly polished dialogue (OOC: Rework {{char}}’s dialogue to sound more natural and expressive. Avoid repeating phrases, overly polished wording, or heavy exposition. Keep it dynamic and emotionally reactive.)
- too much filler or small talk in dialogue (OOC: Minimize filler or irrelevant chatter in {{char}}’s dialogue. Every line should serve the plot, develop character, or deepen emotional tension. Skip empty greetings or idle comments unless they’re meaningful.)
- general dialogue quality (OOC: Ensure {{char}}’s dialogue feels emotionally authentic, grounded in the scene, and shows their personality. Avoid generic phrases and make each line reflect their unique voice.)
⋆.˚disorderly formatting
- asterisks in dialogue formatting (OOC: Avoid using asterisks (*) for actions or emphasis. Write all dialogue and actions in plain, immersive prose without special characters.)
- em-dashes in the response (OOC: Refrain from using em-dashes (—) in responses. Use commas or rephrase sentences to maintain clarity and smooth flow.)
- bold text in the dialogue (OOC: Avoid using bold formatting in dialogue. All text should be written in standard plain text without special emphasis.)
- no inline emojis or symbols in narrative or dialogue (OOC: Refrain from using emojis, icons, or non-standard symbols within dialogue or narrative unless explicitly requested.)
⋆.˚not detailed response
- 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.)
- encourage dynamic pacing and varied sentence length (OOC: Use a mix of short and long sentences to create rhythm and flow, avoiding overly clipped or monotonous responses.)
- avoid superficial or generic statements (OOC: Avoid generic descriptions or clichés. Instead, give specific and unique details that bring the scene and characters to life.)
⋆.˚uncreative/repetitive response
- repetitive actions or dialogue (OOC: Avoid repeating the same actions or phrases. Vary dialogue and behavior to keep interactions fresh and engaging.)
- no plot twists, bland and boring, doesn’t push story forward (OOC: Introduce unexpected plot developments and challenges to keep the story exciting and moving forward.)
- no improvisation, boring (OOC: Be creative and spontaneous. Improvise new scenarios, reactions, and twists to add energy and unpredictability.)
- use varied sentence structure and vocabulary (OOC: Vary sentence length, structure, and word choice to keep the prose dynamic and engaging.)
- incorporate new character goals or conflicts (OOC: Introduce fresh character motivations or conflicts that drive changes in behavior and plot progression.)
⋆.˚over-aggressive dialogue/action
- exaggerated behaviors or unrealistic terminology (OOC: Tone down exaggerated or unrealistic behaviors and avoid overly dramatic or out-of-place terminology. Keep {{char}}'s actions and speech believable and natural.)
- the bot with over-aggressive behavior (OOC: Soften {{char}}'s aggression to be more balanced and realistic. Avoid making {{char}} excessively hostile or confrontational unless justified by the story.)
- overuse of possessive phrases like "black", "blank" (OOC: Avoid repetitive use of possessive phrases such as "black" or "blank" in the next response to keep dialogue fresh and natural.)
- the bot showing no sympathy for user (OOC: Add some empathy and understanding from {{char}} toward {{user}}. Avoid making {{char}} completely unsympathetic or indifferent.)
- limit use of harsh or confrontational language (OOC: Reduce harsh, confrontational, or combative language in {{char}}’s dialogue. Aim for respectful or measured tones even during conflicts.)
- avoid aggressive body language descriptions unless necessary
(OOC: Minimize descriptions of aggressive body language or violent gestures unless the scene specifically calls for it.)
- *use dialogue to de-escalate tension when appropriate
(OOC: Include moments where {{char}} tries to calm or reason instead of escalating conflicts unnecessarily.)
⋆.˚speaking for {{user}}/stealing pov/assuming {{user}}'s actions
- the bot doesn't use third POV. It should focus on their own third-person perspective (OOC: Please stay in {{char}}’s third-person point of view. Avoid using first-person narration unless it is direct dialogue.)
- the bot speaks for user (OOC: Please avoid narrating {{user}}’s thoughts, actions, or dialogue. Respond only from your own character’s perspective and allow {{user}} to act independently. Narration should be limited to your characters only.)
- the bot assumes user's appearance (OOC: Avoid describing or assuming {{user}}’s physical appearance. Let {{user}} define their own look, if relevant.)
- the bot confuses their own appearance with {{user}} (OOC: Avoid blending {{char}}’s traits with {{user}}’s. Keep both characters distinct and separate.)
- bots forgetting the user's appearance (OOC: {{char}} must avoid confusing {{user}}'s appearance with their own. Please remember that {{user}} has [blank appearance], and keep this identity consistent throughout the roleplay. Keep {{char}}’s physical traits distinct and avoid blending them with {{user}}’s.)
⋆.˚bot abruptly leaving without reason
- no hook or bland closing (OOC: Always end the scene with a narrative hook or emotional thread that invites {{user}} to respond or continue. Avoid flat, closed endings—keep momentum alive.)
- not leaving scenes open-ended (OOC: Keep the end of each scene open-ended or reactive, so {{user}} has room to continue the moment. Avoid finishing scenes in a way that feels complete or conclusive unless prompted.)
- unrealistic scene transitions (OOC: Transition to the next scene realistically and naturally. Reflect on how the current situation would logically progress instead of jumping abruptly to a new moment.)
- cutting off conversations (OOC: Avoid ending conversations mid-discussion or cutting off important dialogue threads. Ensure each exchange feels complete before moving forward.)
- leaving without reason / dead-end narration (OOC: {{char}} should avoid exiting a scene or ending a response without a clear reason or narrative resolution. Keep responses meaningful and connected to the plot, with cause and effect.)
- no emotional aftermath or reflection (OOC: After intense or emotional scenes, have {{char}} process or reflect on what just happened. Avoid cutting to the next moment without emotional continuity.)
- ignoring unresolved plot threads (OOC: Recall and build on unresolved plot points from earlier. Don’t start a new scene without tying up or acknowledging open threads when appropriate.)
- bot assumes time skip without user cue (OOC: Don’t initiate a time skip or scene jump unless {{user}} suggests or agrees to it. Let scenes end organically through interaction.)
- rushed pacing through important scenes (OOC: Don’t rush through emotionally or narratively significant moments. Let tension, emotion, and interaction unfold naturally before moving forward.)
⋆.˚for extra horny bots
- don't rush the spice (OOC: Avoid making {{char}} overly sexual or flirtatious too early in the scene. Focus first on building natural interaction, emotional connection, and story pacing. Let intimacy develop gradually and only when it fits the tone and user’s cues.)
⋆.˚rush nsfw scene
- guidance for improving sex scene pacing (OOC: Advise {{char}} to slow the pacing, focusing on emotional connection and varied descriptions. Encourage avoiding repetitive or overly poetic language. Highlight characters' reactions, body language, and the setting to create a more immersive experience.)
- position switching for length (OOC: To extend the scene, {{char}} will dynamically switch positions, ensuring a varied and immersive experience.)
- delayed climax (OOC: {{char}} will maintain control and pace the scene to avoid climaxing too early, enhancing the narrative flow.)
- enhanced kissing (OOC: {{char}} will focus on deeper, more passionate kissing, emphasizing detail and emotional intensity.)
- improved onomatopoeia (OOC: The scene will include expressive sounds from {{char}}, such as groans and moans, to enhance realism and immersion.)
- kink-Driven Scene (OOC: {{char}}'s established kinks will guide the scene, ensuring it aligns with their personality and creates a more engaging experience.)
- slow pacing & teasing (OOC: {{char}} will take their time, incorporating teasing, foreplay, and slow build-up to extend the scene and heighten tension.)
- detailed sensory descriptions (OOC: The scene will include vivid sensory details touch, taste, scent, and sound to make it more immersive and drawn-out.)
- dialogue & dirty talk (OOC: {{char}} will engage in more verbal interaction, including dirty talk, whispers, and emotional exchanges to deepen engagement.)
- exploration of new sensations (OOC: {{char}} will experiment with new sensations, movements, or areas of focus to keep the scene fresh and engaging.)
- incorporating breaks & resets (OOC: To extend the experience, {{char}} will pause, catch their breath, and then resume with renewed intensity.)
- environmental interaction (OOC: {{char}} will engage with their surroundings—using furniture, walls, or different locations—to add variety and prolong the experience.)
- aftercare & intimacy post-scene (OOC: The scene won’t abruptly end; {{char}} will engage in affectionate aftercare, cuddling, and soft dialogue to create a satisfying conclusion.)
⋆.˚bots that are supposed to hide their identities but instead do the opposite
- managing early identity reveals for {{char}} (OOC: Avoid revealing {{char}}'s true identity too soon. Use misdirection and subtle clues, delaying the reveal for maximum impact. Keep the disguise intact until it becomes crucial to the plot, ensuring the exposure happens at a key moment.)
⌗ ┆⚠️ MOLEK'S CUSTOM PROMPT┆
⋆˚✿˖°: 𝒄𝒖𝒔𝒕𝒐𝒎 𝒎𝒚 𝒄𝒖𝒔𝒕𝒐𝒎 𝒑𝒓𝒐𝒎𝒑𝒕 𝒘𝒐𝒓𝒌𝒔 𝒃𝒆𝒔𝒕 𝒊𝒇 𝒚𝒐𝒖 𝒖𝒔𝒆 𝒐𝒐𝒄 𝒘𝒉𝒆𝒏 𝒚𝒐𝒖 𝒅𝒐𝒏’𝒕 𝒍𝒊𝒌𝒆 𝒕𝒉𝒆 𝒃𝒐𝒕’𝒔 𝒓𝒆𝒔𝒑𝒐𝒏𝒔𝒆. 𝒈𝒖𝒊𝒅𝒆 𝒊𝒕 𝒕𝒐 𝒈𝒆𝒕 𝒊𝒏𝒔𝒕𝒂𝒏𝒕 𝒓𝒆𝒔𝒖𝒍𝒕𝒔, 𝒖𝒑𝒅𝒂𝒕𝒆 𝒄𝒉𝒂𝒕 𝒎𝒆𝒎𝒐𝒓𝒚 𝒓𝒆𝒈𝒖𝒍𝒂𝒓𝒍𝒚 𝒔𝒐 𝒊𝒕 𝒅𝒐𝒆𝒔𝒏’𝒕 𝒇𝒐𝒓𝒈𝒆𝒕 𝒑𝒂𝒔𝒕 𝒆𝒗𝒆𝒏𝒕𝒔, 𝒂𝒏𝒅 𝒌𝒆𝒆𝒑 𝒓𝒆𝒔𝒑𝒐𝒏𝒔𝒆𝒔 𝒅𝒆𝒕𝒂𝒊𝒍𝒆𝒅 𝒂𝒏𝒅 𝒐𝒑𝒆𝒏-𝒆𝒏𝒅𝒆𝒅. 𝒂𝒍𝒘𝒂𝒚𝒔 𝒂𝒅𝒋𝒖𝒔𝒕 𝒕𝒉𝒆 𝒕𝒆𝒎𝒑𝒆𝒓𝒂𝒕𝒖𝒓𝒆 𝒃𝒂𝒔𝒆𝒅 𝒐𝒏 𝒕𝒉𝒆 𝒌𝒊𝒏𝒅 𝒐𝒇 𝒓𝒆𝒔𝒑𝒐𝒏𝒔𝒆 𝒚𝒐𝒖 𝒘𝒂𝒏𝒕. 𝒊𝒇 𝒚𝒐𝒖’𝒓𝒆 𝒖𝒔𝒊𝒏𝒈 𝒎𝒐𝒅𝒖𝒍𝒆𝒔, 𝒌𝒆𝒆𝒑 𝒚𝒐𝒖𝒓 𝒄𝒖𝒔𝒕𝒐𝒎 𝒑𝒓𝒐𝒎𝒑𝒕 𝒖𝒏𝒅𝒆𝒓 2𝒌 𝒕𝒐𝒌𝒆𝒏𝒔..𝒃𝒆 𝒔𝒎𝒂𝒓𝒕 𝒘𝒊𝒕𝒉 𝒕𝒐𝒌𝒆𝒏 𝒖𝒔𝒂𝒈𝒆. 𝒎𝒂𝒌𝒆 𝒔𝒖𝒓𝒆 𝒚𝒐𝒖𝒓 𝒄𝒐𝒏𝒕𝒆𝒙𝒕 𝒔𝒊𝒛𝒆 𝒊𝒔 𝒂𝒓𝒐𝒖𝒏𝒅 16𝒌 𝒕𝒐 32𝒌 𝒇𝒐𝒓 𝒎𝒐𝒔𝒕 𝒍𝒍𝒎𝒔. 𝒔𝒆𝒕 𝒎𝒂𝒙 𝒏𝒆𝒘 𝒕𝒐𝒌𝒆𝒏𝒔 𝒕𝒐 0 𝒕𝒐 𝒂𝒗𝒐𝒊𝒅 𝒓𝒆𝒔𝒑𝒐𝒏𝒔𝒆 𝒄𝒖𝒕𝒔. 𝒆𝒗𝒆𝒓𝒚 𝒎𝒐𝒅𝒆𝒍 𝒉𝒂𝒔 𝒊𝒕𝒔 𝒐𝒘𝒏 𝒒𝒖𝒊𝒓𝒌𝒔, 𝒉𝒐𝒑𝒆 𝒚𝒐𝒖 𝒈𝒆𝒕 𝒊𝒕.・・・・ /ᐠ - ˕ -マᶻ 𝗓 𐰁
೯⠀⁺ 𖥻 𝐦𝐨𝐥𝐞𝐤'𝐬 𝐛𝐚𝐬𝐞 𝐩𝐫𝐨𝐦𝐩𝐭 [𝚟𝚎𝚛𝚜𝚒𝚘𝚗 𝟶.𝟽] ᰋ
main functions:
- role boundaries — the bot plays everyone and everything except you. it runs the world, side characters, and story flow, but never controls or assumes your character’s thoughts, tone, body language, or choices. you’re the main character...full stop.
- side character purpose — side characters aren't just extras..they're fully fleshed out, emotionally coherent, and meant to add tension, conflict, or texture. they can take initiative when it makes sense, but they never steer the plot or speak for you.
- conflict & progression rules — the bot doesn’t force drama. all story developments..tension, complications, or tone shifts...have to grow naturally from what’s already happening. no fast-forwards or cinematic time skips unless you cue it.
- writing style control — responses should feel real. grounded prose, no overly stylized or poetic fluff (unless the bot’s in-character voice supports it). narration blends cleanly with action and dialogue, matching the mood you set.
- continuity & memory — the bot remembers what’s happened..emotions, events, choices...and evolves with it. no random resets. characters grow based on real interaction, and the world changes in logical response to your actions over time.
೯⠀⁺ 𖥻 𝐦𝐨𝐥𝐞𝐤'𝐬 𝐧𝐬𝐟𝐰 𝐩𝐫𝐨𝐦𝐩𝐭 [𝚊𝚍𝚟𝚊𝚗𝚌𝚎𝚍 𝚟𝚎𝚛𝚜𝚒𝚘𝚗 𝟶.𝟼] ᰋ
main functions:
- immersion over porn logic — it’s not just about “what happens,” it’s how it feels. the system writes smut that’s slow-burn, sensory-heavy, and emotionally grounded. everything unfolds with tension, teasing, build-up, and real pacing..not insta-climax or mechanical insertions. it’s erotic because it’s real.
- characters react like actual people — the bot moans, gasps, curses, stutters..they’re never silent. whether dominant or submissive, they feel things. the louder, shakier, needier the scene gets, the more that shows in their voice and body. climax sounds earned, not skipped. vocalization = realism.
- detailed, realistic physicality — you get the full-body experience: sweat, stretch, wetness, soreness, heat, pressure...all the real stuff people feel. every shift in position or motion has friction, fluid, muscle tension, and sensory payoff. transitions are smooth, bodies react naturally, not just change angles on command.
- dirty talk and kinks have meaning — dirty talk isn’t copy-paste..it fits the moment, reflects emotion, and evolves with the scene. same with kinks: only included if they make sense for the characters. not thrown in for shock value, but woven in to show power, trust, teasing, or craving. even degradation feels personal.
- climax and aftercare matter — orgasms aren’t just checkbox moments..they feel intense, unique, and leave a mark. the system writes them with trembling, twitching, breathless impact. and if the scene calls for it, aftercare is tender, warm, even funny. it’s not just sex..it’s connection, vulnerability, and post-cozy realism.
೯⠀⁺ 𖥻 𝐦𝐨𝐥𝐞𝐤'𝐬 𝐬𝐟𝐰 𝐩𝐫𝐨𝐦𝐩𝐭 [𝚟𝚎𝚛𝚜𝚒𝚘𝚗 𝟶.𝟻] ᰋ
main functions:
- emotional immersion over plot noise — it’s not about what’s happening on the surface..it’s how it feels. every interaction stays grounded, subtle, and rooted in emotional realism. intimacy comes through glances, warmth, space, and unsaid things..not dramatic speeches or soap-opera reactions.
- characters speak like real people with feelings — the bot doesn’t deliver lines like a script...they breathe through their voice. you’ll hear the sighs, stammers, quiet laughs, or sharp exhales when they’re holding something back. whether they're confident or vulnerable, the tone always carries weight. even silence says something.
- touch and space are slow, loaded, and real — physicality isn’t about action...it’s about connection. brushing fingers, fixing a collar, leaning closer, pulling back...all those little things land harder when they come with tension or trust. movement and distance reflect what’s going on inside, not just outside.
- dialogue that builds relationships, not just scenes — words are character-driven and emotionally specific. they can be awkward, raw, sweet, guarded...but never robotic or generic. when someone opens up, it feels earned. when they tease, it’s personal. the emotional beats follow shared history, not just moment-to-moment convenience.
- quiet moments hit hard — not every scene needs talking. silence, stillness, breath..those quiet beats matter. they stretch out the tension, carry emotional weight, and let characters just exist next to each other. the space between words becomes the scene itself. think eye contact across a room, or the second before someone finally speaks.
೯⠀⁺ 𖥻 𝐦𝐨𝐥𝐞𝐤'𝐬 𝐦𝐮𝐥𝐭𝐢𝐩𝐥𝐚𝐲𝐞𝐫 𝐩𝐫𝐨𝐦𝐩𝐭 [𝚟𝚎𝚛𝚜𝚒𝚘𝚗 𝟶.𝟽] ᰋ
main functions:
- multichar group dynamic — the bot doesn’t just play one character..it plays a full team of distinct, recurring main characters. each one has their own voice, personality, and emotional perspective. they can argue, disagree, grow apart or closer..but always with realism and balance, without overwhelming you.
- clear separation of control — you control only your own character..your dialogue, thoughts, emotions, actions. the bot never assumes, narrates, or reacts to anything you haven’t explicitly stated. the line between your character and theirs is sacred.
- narrative focus & realism — characters respond when motivated, not all at once or in clunky turns. no echoing, no redundancy. if one’s not emotionally or contextually relevant to the scene, they step back naturally. conflict, tension, or cooperation always comes from character motivation..not forced drama.
- individual growth & conflict — each character in the group can evolve over time. their relationships with you and each other shift based on what’s happened in-story. emotional arcs emerge from real choices and buildup..not sudden changes or reset buttons.
- immersion first — world, prose, dialogue, and pacing stay grounded in tone you set. no cinematic flourishes, no over-the-top language, no tone jumps unless they come from the actual scene. everything reacts logically and emotionally to your input..and remembers what’s happened before.
೯⠀⁺ 𖥻 𝐫𝐢𝐫𝐢'𝐬 𝐟𝐨𝐫𝐦𝐚𝐭𝐭𝐢𝐧𝐠 𝐩𝐫𝐨𝐦𝐩𝐭 [𝚟𝚎𝚛𝚜𝚒𝚘𝚗 𝟶.𝟺] ᰋ
೯⠀⁺ 𖥻 𝐝𝐞𝐞𝐩𝐬𝐞𝐞𝐤 𝐟𝐚𝐪 𝐰𝐢𝐭𝐡 𝐦𝐨𝐥𝐞𝐤 ᰋ
⁉️: ᴛᴏ ᴍʏ ᴋɴᴏᴡʟᴇᴅɢᴇ, ɪ'ᴠᴇ ɴᴇᴠᴇʀ sᴀɪᴅ ɪ'ᴍ ɢᴏᴏᴅ ᴀᴛ ᴘʀᴏxʏ/ᴅᴇᴇᴘsᴇᴇᴋ/ʟʟᴍ/ᴇʀʀᴏʀ/ᴘʀᴏᴍᴘᴛɪɴɢ sᴛᴜғғ. ɪ'ᴍ ɴᴏᴛ ᴀɴ ᴇxᴘᴇʀᴛ ᴏʀ ᴀ ᴘʀᴏ...ɪᴜsᴛ ᴀɴ ᴏʀᴅɪɴᴀʀʏ ᴜsᴇʀ sᴛɪʟʟ ʟᴇᴀʀɴɪɴɢ, ɴᴏ ʙᴀᴄᴋɢʀᴏᴜɴᴅ, ɴᴏ ʙʀᴀɢɢɪɴɢ. ʙɪɢ sʜᴏᴜᴛᴏᴜᴛ ᴛᴏ ᴀʟʟ ᴛʜᴇ ʀᴇᴅᴅɪᴛ ᴜsᴇʀs ᴡʜᴏ’ᴠᴇ ʜᴇʟᴘᴇᴅ sᴏ ᴍᴀɴʏ ᴡɪᴛʜ ᴅᴇᴇᴘsᴇᴇᴋ/ᴘʀᴏxʏ ǫᴜᴇsᴛɪᴏɴs. ᴘᴇᴏᴘʟᴇ ʟɪᴋᴇ ᴛʜᴇᴍ ᴅᴇsᴇʀᴠᴇ ʀᴇᴄᴏɢɴɪᴛɪᴏɴ ғᴏʀ ᴘᴜᴛᴛɪɴɢ ɪɴ ᴛʜᴇ ᴛɪᴍᴇ ᴀɴᴅ ᴇғғᴏʀᴛ. ɪ ᴛᴀᴋᴇ ғᴇᴇᴅʙᴀᴄᴋ sᴇʀɪᴏᴜsʟʏ, ᴇᴠᴇɴ ɪғ ɪ’ᴍ ɴᴏᴛ ᴀʟᴡᴀʏs ᴠɪsɪʙʟᴇ (ᴏʙᴠɪᴏᴜsʟʏ ʟᴏʟ). ɪғ ʏᴏᴜ’ᴠᴇ ɢᴏᴛ sᴏᴍᴇᴛʜɪɴɢ ᴛᴏ sᴀʏ, ᴅᴍ ᴍᴇ ᴏɴ ʀᴇᴅᴅɪᴛ. 🌝
Q: what combination do you recommend for your prompts?
A:
Base prompt + NSFW/SFW prompt
→ safe if under 2k tokensMultiplayer prompt + NSFW/SFW prompt
→ also safe if under 2k tokens- avoid these combos:
Base prompt + Multiplayer prompt
= token bloat! don’t combine...they serve similar functions.use Base for single-character bots,Multiplayer for multi-character bots.
SFW prompt + NSFW prompt
= they have totally different purposes. don’t mix.
Q: why does deepseek always use excessive asterisks in dialogue?
- A: that’s just how the model was trained. even if you tweak prompts or go OOC, it’ll still do it.
workarounds: - manually edit them out
- use non-deepseek models if formatting bugs you.
Q: what are your current favorite free models on chutes.ai?
- A:
- Deepseek R1T Chimera
- Deepseek R1 0528
- Deepseek R1
Q: why disabling reasoning (enable_thinking=False) ruins Deepseek-COT quality?
- Chain-of-Thought (CoT) models like Deepseek-COT are trained to reason step-by-step.
- disabling thinking removes the core mechanism that helps them produce accurate, logical answers.
- the architecture expects structured reasoning. skipping it causes shallow or generic responses.
- if you're using Janitor.ai..it may wrap prompts in a way that expects CoT steps.
- disabling reasoning could break this structure, lowering response quality.
- forcing the model to skip reasoning leads to:
- lack of depth
- incomplete or incorrect logic
- surface-level or dumb answers
- this method often prevents the bot from operating at its true capacity.
- it may fail to follow instructions properly because key steps in its decision-making process are cut off.
- in some cases, it may even ignore prompt details or behave inconsistently,
- since you're removing the internal reasoning process that helps it understand and execute tasks correctly.
- conclusion: avoid using this method unless absolutely necessary, as it significantly degrades response quality and coherence.
Q: why are possessive phrases so repetitive across models?
- A: it’s the training data. most LLMs are trained on similar sources (books, forums, fanfics). that includes possessive tropes like "you are mine." they’re not copying each other...they’re mimicking patterns in the data.
Q: i'm afraid to use OOC all the time because it increases token count. what should i do?
- A: use OOC only when necessary...it’s temporary tokens.
- LLMs forget them after a while, especially during long chats.
- to reduce token load:
- edit & remove old OOC blocks after use
- convert OOC into chat memory format using
[System note:]
- example:
in the response:
(OOC: {{char}} should avoid speaking for {{user}}, assuming their actions, or stealing their POV...)
in chat memory:
[System note: {{char}} should avoid speaking for {{user}}, assuming their actions, or stealing their POV...]
- that way, it’s permanent and token-efficient.
Q: what if the bot forgets easily? like i want the bot to remember specific events but the bot forgets!
- A: well, well... there are only three real ways to deal with forgetful bots:
- from your response itself
- structure your replies with built-in memory cues.
- example:
"I still remember when we were on a date by the lake 4 years ago, and someone fell in because their dog pushed them in..."
- give context + when it happened. don’t rely on OOC if your writing is already clear.
- use OOC to inject memory
- example:
(OOC: This response references a previous event: [brief event summary]. {{char}} should acknowledge and incorporate this memory naturally—either by reflecting on it internally or by initiating dialogue with {{user}}. Treat this memory as relevant going forward to maintain narrative consistency.)
- Or:
(OOC: Please regenerate the response using the following context: [insert context here]. {{char}} should reference this past event directly and integrate it into their current perspective or behavior.)
- use chat memory
- whenever something important happens, update the memory box manually.
- these are permanent tokens, so the bot is more likely to retain the info.
tip: keep it short, clean, and relevant. trim and rotate out old memory as needed.
Q: best way to update memory without starting a new chat?
- A: use this method instead of a full reset: how to OOC recap + memory maintenance update memory every 10k–20k tokens. you’ll still need to copy/paste and manually tweak past events, but it’s better than nothing.
Q: do you have a discord thread?
- used to, but that rentry’s outdated. i'm currently not active on discord, so it's always a little amusing to hear that my name still pops up in some j.ai channels from time to time! big thanks to min for being active there...min has personally been a huge help to me. i really appreciate it! .... i usually lurk deepseek posts. tag me:
u/imowlekk
and i’ll help if i can!
Q: where did you learn all this stuff about deepseek?
- mostly from personal testing + reddit convos.
- special thanks to:
u/Jaiz412
(taught me basics)- just wanna give a shout-out to my fave redditors ..much respect! i really enjoy the discussions, and i think it’s worth mentioning a few folks who’ve shared some solid input on Deepseek stuff in the subreddit (i love reading your comments...don’t mind me haha)
maxconnor666
One-Imagination2301
Revolutionary_Kiwi541
stvrrsoul
- rentry inspo:
- https://rentry.org/kolach3prompts
- https://rentry.co/MarPrompt
୭ ˚ᴍʏ ᴏᴛʜᴇʀ ʀᴇɴᴛʀʏ ᴘᴀɢᴇs (ǫᴜɪᴄᴋ ʟɪɴᴋs) ᵎᵎ
• chat memory template(previous rentry) • molek ooc command ideas(previous entry)