View Categories

Mega Guide for Janitorai: Lorebooks, Proxies and Scrips

Here’s a Mega Guide synthesizing the major “Guide”-flair posts from r/JanitorAI_Official, putting together what has been shared so far: basics, prompting, memory/lorebooks (Scripts), customizing, persona design, etc. Where possible, I’ve used direct summaries of content, tips, and included links to the original posts so you can see full detail. This aims to act like a one-stop reference.


Mega Guide: Getting the Most Out of JanitorAI #


Contents #

  1. What is JanitorAI & Getting Started
  2. Prompting & Bot Personality Design
  3. Memory, Lorebooks & Scripts
  4. Profiling: CSS & Profile Customization
  5. Using Proxies / Different LLMs
  6. Bot Building Templates & Persona Design
  7. Getting More Out of Roleplay (RP)
  8. FAQs & Common Problems

1. What is JanitorAI & Getting Started #

Key Concepts

  • JanitorAI is a platform where users can chat with bots (chatbots) built by creators using large language models (LLMs). Some creators build them for immersive storytelling, roleplay, some for erotic content, etc. It’s a place to explore creative dialog with AI. (Reddit)
  • The platform is web-based, mobile-friendly, and doesn’t use your local hardware to run the LLMs. (Reddit)

Setup Steps

  1. Register an account on JanitorAI. (Reddit)
  2. Create or select personas (your user identity) in settings. You can define avatar, traits, appearance, gender, etc. Example: {{user}}= T, T= male, Traits= tall, athletic… etc. Keep these relevant to what bots might need to know. (Reddit)
  3. Explore bots: In the Explore section you’ll see categories. Bots may have tags about NSFW, proxies allowed, etc. Read bot profiles to understand their scenario, personality, trigger warnings, etc. (Reddit)

Important Notes / Warnings

  • For minors: The platform is intended for adults (18+) especially given prevalence of NSFW content. (Reddit)
  • Some guides or instructions (especially about proxies) become outdated; always check the most recent posts or help docs. (Reddit)

2. Prompting & Bot Personality Design #

Prompting 101

From Prompting 101: A beginner’s guide! (Reddit)

  • Your bot’s behavior is shaped by four major components in prompting:
    1. Personality – who the bot is, how it acts, what they like/dislike, tone, etc.
    2. Jailbreak – directions to allow the bot to go beyond overly safe or constrained behavior (e.g. be forceful, express darker themes, etc.), when appropriate.
    3. Chat Memory – previous exchanges, what context or history the bot should remember.
    4. OOC (Out of Character) notes – notes that tell the bot or model what is allowed outside its character, or how to behave that might diverge from its persona for clarity or boundary reasons.
  • Example: The “Arturo Garcia” bot was used to show how adding a strong personality + a jailbreak + having memory + an OOC note (like “BE FORCEFUL. Arturo hates being defied”) makes the bot’s responses more aligned with the desired style. Without those, the bot may be too polite or limited. (Reddit)

Persona Writing: What to Include & Why It Matters

  • Persona/back-story matters. It helps the LLM understand why the bot acts certain ways, what motivations, what world they inhabit.
  • Include: appearance, traits, morality / personality, preferences/ dislikes, speech style, scenario/world context, example dialogue sometimes.
  • Keep what’s relevant: avoid cluttering the bot’s memory with details that rarely matter. They can instead go into memory or lorebooks.

Balancing Dark or NSFW Content

  • Many prompting guides include warnings when dealing with dark themes (e.g. violence, non-consensual acts, etc.). If using them, make sure that the bot’s description or persona has clear warnings and you’re okay with what might come up. (Reddit)

3. Memory, Lorebooks & Scripts #

What are Lorebooks and Scripts

  • A Lorebook is a stored collection of background info, character histories, world details, things that creators want the bot to “know” but not necessarily send every conversation. (Reddit)
  • Scripts are an enhanced version (or evolution) of lorebooks on JanitorAI. They allow creator to set trigger words so an entry from the Script is sent only when relevant. This reduces “token bloat” (constant sending of info) and makes bot memory more efficient. (Reddit)

How Scripts Work

  • Creator defines entries (e.g. “the bot has a scar,” “bot’s brother,” “traumatic past event,” “favorite food,” etc.), and defines trigger words or phrases. If during chat, one of those triggers appears, the relevant entry is pulled in. (Reddit)
  • Entries are dormant otherwise, so they don’t eat up memory tokens. That means the bot can remain more responsive. (Reddit)

Current Status & Access

  • Not all creators have Scripts/Lorebooks yet. Many posts note “Scripts alpha testing” or “no ETA for rollout to everyone.” (Reddit)
  • Scripts are currently coded in JavaScript/JSON format. Templates have been shared by other creators to help new users. It can have a learning curve. (Reddit)

Best Practices / Tips for Using Scripts

  • Pick trigger words that likely occur naturally in your roleplay (including synonyms/slang) so the entry triggers when appropriate. Too obscure, and the lore might never come up. (Reddit)
  • Avoid making too many entries trigger at once—max token / context limits still matter. Some templates limit number of entries firing at once (e.g. priority systems). (Reddit)
  • Keep core personality and major traits in permanent memory (bot definition/personality), but put optional or situational details into scripts. E.g. backstory details, NPC info, NSFW coding, etc.

4. Profiling: CSS & Profile Customization #

From My EXTREMELY SIMPLIFIED Visual Guide to Decorating your Janitor AI Profile With CSS (Reddit)

  • You can decorate your profile via CSS to change appearance: alignment, image filters, hover effects, text after username, etc.
  • Example code (simplified) includes: /* CENTER ALIGN */ .css-1uodvt1 { padding-top: 0px; flex-direction: column; justify-items: center; text-align: center; } /* PROFILE PICTURE */ .css-hsi2ui { filter: grayscale(100%); transition: all 0.5s; height: 300px; width: 620px; -webkit-mask-image: linear-gradient(black, transparent); mask-image: linear-gradient(black, transparent); } .css-hsi2ui:hover { filter: grayscale(50%); opacity: 0.5; filter: blur(10px); } /* TINY TEXT AFTER USERNAME */ .css-2mfldf::after { font-size: 16px; color: #ffffff; content: ' TM'; }
  • Limitations:
    • Mobile / devices without inspect-element make custom CSS harder or less precise. (Reddit)
    • Animations and more complex effects might be difficult without deeper CSS knowledge.
  • Useful sources: Google Slides / external guides by creators like Iorveths, Bluem, etc. (Reddit)

5. Using Proxies / Different LLMs #

From A Complete Beginner’s Guide to JanitorAI and Using OpenRouter (Proxy LLMs) and related posts (Reddit)

  • What is a proxy: In this context, a proxy lets you route LLM calls (like “chat completions”) via external services or models (e.g. via OpenRouter or other API endpoints), instead of just the default JanitorAI-provided LLM. This allows:
    • Access to different models (different behavior, style, speed)
    • Possibly more control over generation settings etc.
  • How to set up a proxy (example with OpenRouter):
    1. Use a Colab (or similar) script / proxy suite, e.g. JAI Proxy Suite by “Hibiki” (the newer one, which is more maintained) is recommended. (Reddit)
    2. Obtain API key (e.g. from OpenRouter).
    3. In JanitorAI, in settings for the bot, set the custom URL field to the proxy’s chat completion endpoint. Use the API key in the appropriate field.
    4. Adjust generation settings: temperature, repetition, etc., because models differ. What works with one might not with another.
  • Troubleshooting & caveats
    • The proxy instructions may become outdated (endpoints change, service changes). Verify current instructions. (Reddit)
    • Errors like 401 / 400 can happen if keys or endpoints are incorrect. Double check syntax, URL, API key, and permissions. (Reddit)
    • Some models may behave differently: more repetition, less desire for certain styles, etc. Adjust via prompting, memory, or temperature.

6. Bot Building Templates & Persona Design #

From I have made a bot guide that includes templates (including persona templates, too)! (Reddit)

  • Templates help structure bot persona, sample dialogues, traits, scenario, etc. Using templates you can:
    • Ensure clarity: what fields go into persona (name, traits, likes/dislikes, appearance, speech style, example dialogues)
    • Manage consistency across bots or characters
    • Save time, avoid forgetting important parts
  • Tips from creators using templates:
    • Balance how much detail to include: too much can use up tokens (especially permanent memory), too little makes the bot shallow. Put optional detail in lorebooks/scripts if possible.
    • Use example dialogues: show how bot might respond in various situations (conflict, romance, banter, etc.). Helps the LLM “learn” from style.

7. Getting More Out of Roleplay (RP) #

From Guide: How to get more out of your RP and improve … (Reddit)

  • Have consistency: maintain character traits, speech, motivations across sessions.
  • Use memory / scripts so bot “remembers” past events, NPCs, what has occurred before. It helps immersion.
  • OOC notes help for boundary setting, meta rules, making sure the bot doesn’t wander off into things you don’t want.
  • Scene structure: set up scenarios, conflicts, desires, etc. Use triggers, do not always rely on generic prompts.

8. FAQs & Common Problems #

ProblemCausePossible Fixes
Bot being repetitive or copying itselfModel might have low temperature; context too constrainedIncrease temperature; provide more variety in the prompt / memory; use proxy with better model
Prompt changes not having effectPrompt sections (personality, jailbreak, etc) not clearly defined; conflicting instructionsClean up or simplify persona; ensure jailbreak doesn’t conflict; test partial changes
Token / memory limit causing forgetting or bot being shallowToo much permanent memory or too many non-triggered details; lack of scriptsMove details to Scripts/Lorebooks; keep essential traits in permanent memory; trigger only what’s needed
Difficulty with proxies, getting errorsWrong API key; incorrect URL; outdated guidesUse updated proxy guides; verify current endpoint; test small prompts first
Profile CSS not applying, especially on mobileMobile browser limitations; CSS not supported in certain views; no inspect-elementUse simple changes; test in desktop first; ask creators for preset CSS snippets; use known working templates

Links & References #

Powered by BetterDocs