📚Knowledge Base

The Knowledge Base (aka Lorebook) is a tool that helps define and reinforce the personality, background, and world-building elements of AI characters. It works by storing key details, such as character traits, relationships, and important events, which the AI can reference during conversations.

How It Works:

• Keyword Triggers: You can set specific words or phrases that, when mentioned in a conversation, prompt the AI to pull relevant information from the Knowledge Base

• Memory Reinforcement: Helps keep characters consistent across interactions.

• World-Building: Useful for RPGs, fanfiction, or any interactive storytelling where maintaining internal logic is crucial.

It’s similar to how “Memory” works in some AI chatbots, but more structured for character development and narrative continuity.

How does the Knowledge Base work?

The knowledge base retrieves information using trigger keywords

• Keywords: You manually assign these to an entry.

How should keywords be used effectively?

Choose keywords that are specific enough to match the entry while avoiding overly broad terms that could trigger irrelevant responses. For example, if referencing a specific 'Trip called The Hawaii' trip, use that as the keyword but avoid generic terms like trip, beach, or sea, which may cause the AI to pull the entry too frequently.

How many entries can we have?

Unlimited

Does {char} and {user} work in the knowledge base?

Yes. Check out this simple tutorial

How are keywords triggered?

Keywords activate whenever they appear in the chat, whether used by you or the AI. To avoid unintended triggers, choose keywords that are specific rather than too broad.

Can you use Knowledge Base in any new chat?

Yes, you can. Once you save your knowledge base entries, they can be used in any chat.

Do Knowledge Base count towards the token limit for memory?

No, the entire Knowledge Base does not count toward the token limit. Only the entries the AI retrieves—up to 4,096 characters (about 1,025 tokens) at a time—are considered. On Moescape AI, you can now pull only one entry at a time. However, in the “Edit Knowledge Base” section, you can adjust the scan depth, which determines how many chat history messages are analyzed for relevant keywords. Keep in mind that your AI memory context is not affected by the entire Knowledge Base.

Token vs Characters

Note: You can use this link to calculate your token— https://platform.openai.com/tokenizer

Entries

When you open the knowledge base window, you'll see the entry section, where you can add various trigger words to activate chatbot responses or memories.

Now, let’s jump into an example. Suppose you're chatting with a chatbot that plays the role of your coworker Justin, and you want to make him fall in love with you. You can set up specific entries to trigger certain types of conversations. (Remember: When creating keywords, be as specific as possible, as mentioned earlier.)

What type of keywords can you create to trigger specific types of conversations?

1. Character: Boss, colleagues, or office friends who influence the romance.

2. Event type/ Themes

   1. Workplace Tension & Flirting: Subtle (or obvious) chemistry through meetings, lunch breaks, or projects.

   2. Challenges & Conflict: Workplace policies, personal fears, misunderstandings, or external pressures.

   3. Turning Point: A critical moment that pushes them closer (e.g., late-night work session, company retreat, or crisis).

3. Location: Office, coffee shop, after-work hangout spots.

4. Others

   1. Inside Jokes & Shared Moments: Things only they understand (e.g., teasing about coffee orders, funny meeting mishaps).

   2. Memorable Quotes & Dialogues: Significant lines that reflect their relationship dynamic.

Character Example (Response below):

Response:

Event Type Example (Response below):

Response:

Final Notes

On Moescape AI, you can create as many entries as you want—there's no limit! For more tips on knowledge, feel free to join the Moescape Discord and chat with top chatbot creators in the Tavern channel.