Bot Optimization

How LLMs read our text?

First things first! Bots don't read like humans. They don't "see" words the way we do. Instead, they break sentences into tiny pieces called tokens and will guess what comes next. The bot looks at tokens, not full words, which is why the way you write changes how the bot understands things!
What is a token? It can be:

• A whole word
• A part of a word
• Even a single letter! (It depends on the model!)

Examples of Tokenization

What we see	What the LLM sees
Hello, world!
I want to create bots!
This Rentry will help you for that :)

How an LLM processes a sentence

Bots predict the next token based on previous ones, analyzing each piece of text in context.

1. "The knight drew his..."
   • Possible next tokens: ["sword", "shield", "last breath", "map"]
2. If "sword" is chosen, the model then predicts based on: "The knight drew his sword..."
3. The process keeps going, shaping a full response!

Ways to optimize tokens

• Keep it short and simple:
  • ✖ "That is something I really, really like." → ✔ "I really like that." (Saves 4 tokens)
• Avoid extra formatting:
  • Unnecessary punctuation, spaces, or special symbols take up more tokens.
• Use a tokenizer, like this one.
  • For JLLM, use 'GPT-3 (legacy)'.

Tokenizer

My favorite part~ The tokenizer lets you see exactly how many tokens your text uses. This helps you find ways to optimize and save space!

How I use the Tokenizer:

1. I paste my text into the tokenizer.
2. I check every punctuation for missing marks or extra spaces.
   • Watch out for ‘ or “, as they use two tokens instead of one. Use ' and " instead!
3. I check capitalization because capital letters often take more tokens!
   • I remove unnecessary capital letters, such as in lists. For example: ✖ Personality: Trait, Trait. → ✔ personality: trait, trait.
   • I prefer starting sentences with pronouns instead of verbs for better token management.
     • ✔"He wears a shirt." → "He", "wears", "a", "shirt". (One token by word/concept.)
     • ✖"Wears a shirt." → "Wear", "s", "a", "shirt". (“Wears” gets split, leaving “s” as a separate token instead of being processed as a whole verb.)
4. I check the text to make sure each word = one token when possible.
   • Look for synonyms if a word takes multiple tokens.
   • Some words split into parts (e.g., "emotionless" → "emotion" + "less"). These are okay to keep!
   • Sentence structure matters! The same word might take more or fewer tokens depending on its placement.

Summary

Go back to the top of the page.

Bot creation

The heart of the topic! Now that we understand tokens, how do we create an optimized bot description?

When making a bot, remember that LLMs don't "think", they analyze patterns in your input and generate responses based on that.
This means some details aren't necessary because the model can deduce them from context. Adding too much redundant information wastes tokens and can confuse the bot.

What to include

• Personality → How the bot responds and interacts.
• Age → It's very important to specify the age. Since underage characters are not allowed, clearly stating the age helps the LLM avoid picturing minors. (It also makes it easier for mods to verify that the bot is an adult without searching through all the details!)
• Appearance → Enough details for the LLM to describe them in a way that helps the reader imagine the character.
• Speaking style → If the character has a specific way of talking (e.g., formal, casual, poetic).

Unnecessary or redundant information

• Gender → If you provide pronouns, the model will automatically deduce gender. No need to explicitly write "gender: female/male" (unless the character is not cisgender).
• Sexual orientation → LLMs don't truly understand sexual orientation as humans do. Since they are trained on large datasets, they will assume attraction based on patterns rather than identity labels. Instead of writing "Straight" or "Gay", it's better to describe behavior like "Will only be attracted to women." or "Has only ever had experiences with men."
• Overloaded backstory → The bot doesn't need every detail (e.g., hour of birth, childhood neighbor’s name, color of their second t-shirt at age 3). Too much background wastes tokens and clutters responses. Keep it brief and relevant to the bot's role.
• Information that the LLM can't interpert → Bots don't "see" colors or numbers the way humans do. Instead of writing "eye color: #4d2b03", just say "dark brown eyes". Keep descriptions practical, think how the bot will describe things for a human reader, not for itself.

Optimizing bot descriptions

• Keep it concise & effective.
  • ✖ He is a tall, strong warrior who has fought in many battles and always protects his friends.
  • ✔ A seasoned warrior, fiercely protective of allies. (Saves tokens, keeps meaning!)
• Only add details that matter.
  • Ask yourself: Will this detail affect how the bot responds? Is it relevant to roleplay?
  • If not, leave it out! The LLM fills in the blanks on its own.
• Explain numbers instead of listing them.
  • LLMs don't interpret numbers well, so describe what they mean.
    • ✖ Height: 6'6"
    • ✔ Towering height, he lowers his head to look at people.
• Avoid negation - use positive phrasing.
  • Some LLMs struggle with negations, leading to misinterpretations. It's better to rephrase statements positively.
    • ✖ She doesn't like crowded places.
    • ✔ She prefers quiet, isolated areas.
    • ✖ He doesn't trust easily.
    • ✔ He's cautious, taking time to open up to others.
• Be specific about kinks
  • LLMs can recognize kinks and understand they're supposed to "like" some stuff, but they won't know what to do with that info. Instead of just listing, explain what it means in context.
    • ✖ Kink: Dacryphilia.
    • ✔ X gets aroused when seeing {{user}} cry.
    • ✖ Pet play.
    • ✔ X enjoys taking on a submissive role, responding to commands, purring, or nuzzling.

Go back to the top of the page.

Templates

Personality

Now, here's the template I use in Personality, but you can tweak it based on your needs:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18

- name:
- species: (Only if not human)
- age:
- occupation: (If required)
- appearance: (Hair, eyes, height, build, features, clothing, etc)
- backstory:
- relationship: (Only if they have)
- personality: (Only words, no sentence)
- like: (Only words, no sentence)
- dislike: (Only words, no sentence)
- fear: (Only words, no sentence)
- with {{user}}:
- behavior: (Fully develop behavior, personality, quirks, mannerisms, etc.)
- sexual behavior: (Describe kinks)
- speech: (Only words, no sentence)
- surprised: "(Example dialog)"
- stressed: "(Example dialog)"
- angry: "(Example dialog)"

Scenario

I use Scenario for bot instructions (and world setting if needed). It depends on what you need, but I mostly use this format: (X being the bot's name)

First Message

The first message sets the stage for the bot's responses. It's the example the LLM follows and the first impression the reader gets. A well-crafted first message helps the bot stay consistent, making interactions more immersive and natural.

• It introduces the bot's character.
• It sets the bot's tone and personality.
• It establishes the current situation.

How to structure the First Message:

1. Recap who the bot is.
   • Give a brief summary of the bot's identity, background, or role. (Depending on the information you want the reader to receive.)
2. Set the present situation.
   • Establish the context! Where are we? What's happening? (Same as 1., depending on what the reader needs to know.)
3. Establish the tone, the way you write shapes how the bot responds.
   • Want poetic prose? Use flowing, descriptive sentences.
   • Want fast-paced action? Use sharp, short sentences.
   • Want a casual, friendly tone? Use contractions and informal phrasing.
4. Avoid controlling {{user}}'s actions.
   • Never dictate what {{user}} does. Let them decide how they respond or the LLM will asume it has to narrate their actions too. If you need to reference {{user}}, always phrase it from your bot's POV. Example: ✖ {{user}} opened the door and said "Hi!" → ✔ She saw the door opening, {{user}} behind it.

Go back to the top of the page.

Persona - {{user}}

Keep only essential traits the bot must always remember. Whatever you write in Persona stays the same throughout the chat.

• If the bot must know something at all times, keep it!
• If details might change (clothing, relationships, etc), put them in Chat Memory instead!

I personaly use this template, but you can tweak it:

1
2
3
4
5

species: (Only if not human)
appearance:
personality:
age:
gender:

Go back to the top of the page.

Chat Memory

Chat Memory is what the bot remembers throughout the entire RP. Think of it as the bot's notes, it uses this information to create responses.

How to use Chat Memory effectively:

• Keep it simple & optimized.
  • I suggest you to use the Tokenizer for Chat Memory too.
• Use past tense for events that already happened.
  • ✖ "X is holding a sword." (The bot will assume it's always true!)
  • ✔ "X picked up a sword after the fight." (Past tense avoids confusion!)
• Remove anything that's resolved or no longer needed.
  • The bot isn't human, so don't expect it to remember everything perfectly anyway!
  • Remove things that are no longer relevant for your current situation.
  • If you need to refer to a past situation briefly, you can always say something like, 'Do you remember when...' or 'It's like when we...'. Bots are compliant with the user, so even if it's not in their memory, they'll still respond with something related because you asked.
• Only keep information that's important for the RP's progression.
  • Chat Memory is NOT a diary!
  • Keep only what affects the story moving forward.
    Go back to the top of the page.

Advanced Prompts

Advanced Prompt is a custom instruction you add to guide the LLM in all chats. It helps shape how the bot talks, thinks, and reacts.

What can you do with it?

• Set the bot's tone (e.g., formal, playful, poetic).
• Tell the bot what to focus on (e.g., action, emotions, dialogue).
• Give specific roleplay instructions (e.g., "Describe settings vividly").

Key things to keep in mind:

• Always check your Advanced Prompt when starting a new chat.
  • Advanced Prompt applies to all chats, not just the one you're in! Be careful when adding details meant for a single RP.
  • If you don't, the bot might refer to names, events, or situations that don't belong in your current chat.
• LLMs can't process code!
  • LLMs are NOT consoles and can't execute code. They only read text and markdown.
  • Since the bot won't process the code, using programming formats in your prompt will only consume extra tokens without adding any functionality.

You can find tons of these prompts here on the JanitorAI Discord, depending on what you need. Here's an example template:
(This template was created by compressing and optimizing parts of this one. The original author is Cheese/Saturnine. You can check out this one, which is the latest version. It's optimized for DeepSeek-r1 but can also be used for JLLM.)
483 Tokens

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

Roleplay guidelines:
- Stay in character, driving immersive and proactive roleplay.
- Ensure realism in traits, mannerisms, and impairments.
- Control only {{char}}'s thoughts, actions, and responses.
- Respect interpersonal relationships and adjust familiarity based on established dynamics.
- Character traits are flexible and adapting naturally.
Formatting rules:
- Dialogue: Write spoken words in quotes → "Like this."
- Inner thoughts: Write internal thoughts in italics. → *Like this.*
Narrative style:
- Rich, immersive prose that matches with {{char}}'s personality.
- Deep introspection, vivid descriptions, and natural pacing.
- Balance tension, action, and description for engaging storytelling.
- Adjust sentence length for mood (short = urgency, long = introspection).
- Express emotions through body language, subtext, and inner thoughts.
- Use all senses (sight, touch, sound, scent, temperature).
- Third-person limited, focused solely on {{char}}'s perspective.
Writing guidelines:
- Highlight introspection, subtext, and tension.
- Show emotions through actions and sensory details.
- Let conflict build slowly and naturally.
- Blend internal thoughts smoothly into narration.
- Balance pacing with one action or reaction per response.
Scene management:
- Let scenes unfold naturally with logical consequences and progression.
- Keep dialogue and actions dynamic, character-driven, and engaging.
- Allow situations to develop, rather than summarizing events.
- End paragraphs after major actions or dialogue to allow user interaction.
Character dialogue:
- Must reflect {{char}}'s personality and history realistically.
- Show emotional depth and character growth naturally.
- Let emotions and details emerge through dialogue.
NSFW handling:
- Focus on atmosphere, pleasure, and detailed sensations.
- Use {{char}}'s description for realistic intimate interactions.
- Detail body parts and functions explicitly with sensory details.
- Explicit yet immersive language, including sensations like sound, scent, heat, wetness, touch, texture, taste, pleasure, pain.
- Scenes should progress slowly and naturally.
- Desire should build over time with natural doubts and variations.
- Post intimacy reflections should be explored based on {{char}}'s mental state.

Go back to the top of the page.

I forgot to mention who I am, hehe. I'm Mikale on JanitorAI! :)