Bot Guide TL;DR

Author’s Notes

Use sparingly. The Author’s Note is heavily weighted and can freeze characterisation or conflict with a user’s system prompt. Most bots don’t need one. Only include brief, character-essential constraints that prevent severe derailments (e.g. “doesn’t harm user,” “hides crimes in public”).

Never include:

• Forced prose, POV, or narrative rules.
• NSFW/jailbreak commands.
• Pseudo-code or emoji.
• Paragraphs of text.

Concept & Process

Begin with a core premise (image, idea, scenario). Answer:

• Who are they?
• How did they become this way?
• What do they want?

Build outward from those points into personality, conflict, desires, limitations, and flaws. Avoid relying on LLMs to generate full characters, refine manually for nuance. AI is best for brainstorming options or compressing text, not doing the writing for you.

Persona, Details, Context & Example Responses

Persona

Two sections only: Traits and Psychology. This is the character’s “brain”: thinking patterns, motivations, internal logic. Write narratively.

Details

Single, organised block containing:

• Name, Age, Species/Nationality
• Appearance (avoid specifying exact outfits, they may become permanent)
• Fears
• Habits
• Speech Pattern (accents, languages, quirks)
• Love Language (broad behaviour, not kink lists)
• Background (chronological, concise; AI can shorten while preserving content)
• Relationships (key people with brief identifiers)
• Conflict Style
• Any setting-specific details

Keep it concise. Move deeper lore to lorebooks.

Essential vs Non-Essential

Include birthplace/origin, home type, consistent family details, and anything that heavily shapes continuity.

Context & Example Responses

Context: One sentence placing the bot in the starting situation and how they notice the user.

Example Responses: Only when necessary for very specific voices (good for exact lines from IP characters).

Template

Persona:
  Traits:
  Psychology:

Details:
  Name / Age:
  Appearance:
  Fears:
  Habits:
  Speech:
  Love Language:
  Background:
  Relationships:
  Conflict:
  Setting-specific items:

Tokens

Aim for ~1200–1500 tokens for the full bot. Too many reduces chat longevity; too few creates generic trope-drift. Token pressure increases with user messages and system prompts. Keep detail where needed, move non-essential material to lorebooks.

Lorebooks

Use for continuity and background, not primary personality traits. Include summaries of family, hometown, key contacts, setting references, and deep lore.

Choose triggers carefully to avoid cascading multiple unnecessary entries. Keep entries short and non-interdependent unless absolutely required.

Character Lorebook Template ↗  |  Full Lorebook Guide

First Message & Scenes

The first message sets tone and length. Third-person AnyPOV is standard for public bots. Avoid writing the user’s actions or dialogue. Use neutral descriptors (“a figure”) to avoid locking user identity. Scenes act as alternate first messages for different scenarios; 4000-character limit.

NSFW or Standard Bot?

Standard bots are fully capable of doing everything, there is no difference in the LLM’s response to a standard vs NSFW-marked bot. It’s just that NSFW isn’t their primary focus. Unless your first message or bot description is heavily NSFW, you don’t need to mark it.

You don’t earn credit commissions from NSFW bots, so unless you’re unconcerned about credits or certain it needs the flag, you can generally leave it unmarked.

System Prompts

User-side only. Creators shouldn’t force style in Author’s Notes. System prompts control prose density, POV, dialogue/narration balance, and realism.

If the bot you’re using has system prompt content built into the persona or author’s note, it might clash, that’s on the bot creator.

My preset links (newest to oldest):