Spicychat.ai Lorebook: How to Create Better AI Characters and Story Worlds

You’re three messages deep into what feels like the perfect roleplay conversation. Your AI character remembers everything: the coffee shop where you first met, that inside joke about the purple umbrella, even the subtle tension from yesterday’s argument.

Then the message four hits.

Suddenly, your character acts as if none of it happened. The coffee shop? Never heard of it. The umbrella? What umbrella? It’s like talking to someone with selective amnesia.

This is exactly what the spicychat ai lorebook fixes. Think of it as giving your AI character a smart notebook that opens to the right page at exactly the right moment. No more random memory loss. No more repeating yourself. Just consistent, immersive conversations that actually remember your story world.

Let me show you how to build one that actually works.

What is the Spicychat.ai Lorebook?

Here’s the simple version: a lorebook is a dynamic memory system that feeds relevant information to your AI character during conversations. Unlike the character description (which is always active and limited), a lorebook activates specific details only when they matter.

Your character’s description might say “Alex is a detective in Neo Tokyo.” Basic stuff. But your lorebook? That’s where you store the fact that Neo Tokyo has three districts, each with different crime syndicates, and Alex has a complicated history with the leader of the Red Lotus gang.

The beauty is that this information doesn’t clutter up every single message. It appears only when your conversation naturally triggers it. Mention the Red Lotus gang, and boom, the AI suddenly remembers all that backstory without you explaining it again.

Most platforms make you cram everything into one giant character description. Spicychat’s lorebook lets you spread that information across hundreds of entries, each waiting for its moment to shine.

Also read: Twitch logs ivr

Understanding Your Token Budget (And Why It Matters)

Before you start building a massive encyclopedia of lore, understand this: you’re working within limits.

Spicychat allocates roughly 20% of your total context for lorebook content. That breaks down to:

• Free users: 740 tokens (about 500-600 words)
• True Supporters: 1,600 tokens (around 1,200 words)
• I’m an All In member: 3,080 tokens (roughly 2,300 words)

These numbers matter because if you write fifty detailed entries, they won’t all load at once. The system picks the most relevant ones based on keywords in your last four messages. Each activated entry stays loaded for about two conversation turns, then drops out unless the keywords come up again.

Think of it like this: you’re not building a library where every book is open simultaneously. You’re building a smart library where books open themselves when you need them, then close to make room for others.

This means your strategy shouldn’t be “write everything I can think of.” It should be “write the right things that trigger at the right moments.”

Building Your Lorebook Architecture

Most people approach lorebooks backwards. They start writing entries randomly, whatever comes to mind. Three months later, they have 200 entries and no idea which ones actually trigger during conversations.

Instead, use a tier system.

Tier 1: Core World Rules

These are fundamental facts about your story world that should trigger frequently. Magic systems, technology rules, and social structures. Keep these under 100 words each because they’ll eat up token space whenever they activate.

Example entry:

• Keywords: magic, spells, casting
• Content: “Magic in this world requires verbal incantations and hand gestures. Rushed spells often backfire. The Mage Guild regulates all spell usage and tracks magical signatures to prevent illegal casting.”

Tier 2: Location Details

Specific places that appear in your story. These trigger when characters visit or discuss those locations.

Example entry:

• Keywords: Rusty Anchor, tavern, pub
• Content: “The Rusty Anchor sits on Harbor Street’s east end. Viktor, the bartender, knows everyone’s business but keeps secrets for gold. The back room hosts illegal card games every Thursday. Constables avoid the place.”

Tier 3: Character Relationships

Background connections between characters. These add depth without cluttering the main character description.

Example entry:

• Keywords: Marcus, brother, sibling
• Content: “Marcus is {{char}}’s older brother. They haven’t spoken in two years after Marcus joined the military against their mother’s wishes. {{char}} still keeps Marcus’s letters but never replies.”

Tier 4: Plot Triggers

Events or objects that become relevant at specific story moments.

Example entry:

• Keywords: silver locket, necklace, pendant
• Content: “The silver locket contains a photo of {{char}}’s mother taken before the war. {{char}} never opens it but touches it when stressed. The locket is the only family heirloom that survived the fire.”

This hierarchy helps you prioritize. Start with ten Tier 1 and Tier 2 entries. You can always add Tier 3 and 4 later as your story develops.

Advanced Keyword Strategies That Actually Work

Keywords are how lorebook entries get activated. The AI scans your last four messages (both yours and the character’s responses) for matches. When it finds one, that entry loads into context.

Sounds simple, right? It is, until you realize most conversations don’t use the exact words you predicted.

The Multi-Keyword Safety Net

Never use just one keyword per entry. People naturally use synonyms. If your entry only triggers on “coffee shop” but the conversation says “café,” you’re out of luck.

Better approach:

• Keywords: coffee shop, café, bistro, Brew Haven
• Content: “Brew Haven is a small café on Market Street where {{char}} works morning shifts. The owner, Rosa, treats {{char}} like family. Regular customers include Detective Hayes and the mysterious woman who always orders black coffee.”

Now this entry triggers four different ways during natural conversation.

Wildcard Tricks

Wildcards let you match word variations. The asterisk (*) symbol is your friend here.

Use *book to match “notebook,” “textbook,” “storybook,” and any other word ending in “book.”

Use magic* to match “magical,” “magician,” “magic-user,” and other variations starting with “magic.”

But here’s the catch: wildcards can backfire. Use *light and you’ll trigger on “slight,” “delight,” “flashlight,” even “enlightenment.” Be specific enough to avoid false triggers.

The {{user}} and {{char}} Secret

You can use {{user}} and {{char}} as keywords. These automatically match whenever someone mentions the user’s name or the character’s name in conversation.

This is perfect for hidden backstory entries:

• Keywords: {{char}}, past, history
• Content: “{{char}} grew up in foster care after their parents died in a car accident. They never talk about it, but they flinch at the sound of screeching tires.”

Now, whenever someone asks about the character’s background, this information loads automatically.

Handling Keyword Conflicts

If two entries share the same keyword, both load when that word appears. Sometimes this is exactly what you want. Other times, it wastes token space.

Good overlap example:

• Entry 1 (Keyword: mansion) – Describes the building’s exterior
• Entry 2 (Keyword: mansion) – Describes the interior layout

Both are relevant when discussing the mansion.

Bad overlap example:

• Entry 1 (Keyword: fight) – Character’s fighting style
• Entry 2 (Keyword: fight) – Character’s emotional response to conflict

These might not both be relevant simultaneously. Consider using more specific keywords like “combat” vs “argument.”

Also read: Picuki website step by step process guide

Writing Lorebook Content That Doesn’t Waste Tokens

The 1000-character limit per entry is generous. Too generous, actually. Most effective entries sit between 200 and 400 characters (about 2-4 sentences).

Here’s why: longer entries eat more tokens, leaving less room for other entries to activate. And usually, you don’t need a full paragraph to convey one piece of information.

The Reference Note Style

Write entries like you’re leaving notes for someone who already knows the basics. Skip the flowery descriptions and get to the facts.

Weak entry: “The Shadowfen Swamp is a dark, mysterious, and foreboding place that many travelers fear to enter. It is said that strange creatures lurk in its murky depths, and locals warn visitors to stay away from this dangerous location.”

Better entry: “Shadowfen Swamp covers twelve square miles south of the capital. Locals avoid it after dark due to will-o’-wisps that lure travelers off paths. The northern edge has solid ground. The southern half is quicksand disguised by moss.”

The second version gives specific, usable details without wasting words on atmosphere-building. The AI can generate an atmosphere on its own. It needs facts.

Active Voice, Present Tense

Write like you’re explaining something happening right now, not telling a story about the past.

Instead of: “The guild was established in 1847 by a group of merchants who wanted to…”

Write: “The Merchant Guild controls all trade in the city. Founded in 1847. Current guildmaster is Thomas Blackwell. Membership costs 500 gold annually.”

Short, punchy statements pack more information into fewer tokens.

Avoid These Content Mistakes

Don’t write a character’s entire backstory in one entry. Break it into pieces triggered by different keywords. One entry for childhood, another for their military service, another for that traumatic event five years ago.

Don’t be vague. “The city is big and important,” tells the AI, nothing useful. “The city has 200,000 residents, three universities, and hosts the annual trade summit,” gives concrete details that the AI can reference.

Don’t contradict yourself across entries. If one entry says the character loves dogs and another says they’re terrified of animals, the AI gets confused. Keep a master document tracking your key facts.

The 5-Step Setup Process

Step 1: Create Your Lorebook Shell

Go to Create, then Lorebook. Fill in the name, description, and tags. The description is just for you to remember what this lorebook covers, so keep it simple.

Step 2: Map Your World on Paper First

Before you write a single entry, spend fifteen minutes listing what matters in your story. Key locations, important characters, world rules, and significant objects. Don’t write the entries yet. Just make the list.

This prevents the scattered approach, where you have 30 entries about random details but nothing about the core elements of your world.

Step 3: Write Your First 10-15 Essential Entries

Start with what will come up most often in conversations. Your main location, the character’s job, maybe two or three important NPCs, and one or two world rules.

That’s it. Don’t write fifty entries on day one. You don’t know which ones you’ll actually need yet.

Step 4: Test With Actual Conversations

Attach your lorebook to a character (go to Advanced settings in the Character Editor). Then start a conversation and deliberately mention your keywords. See what triggers. See what doesn’t.

You’ll quickly discover which keywords work naturally and which ones you’ll never actually say in conversation.

Step 5: Iterate Based on Results

After three or four chats, you’ll notice patterns. Maybe you keep explaining the same background detail because you haven’t made an entry for it. Maybe some entries never trigger because their keywords are too specific. Adjust accordingly.

Lorebooks are living documents. The first version is never the best.

Also read: Is livebeam legit

Real-World Examples

Fantasy World Building

Say you’re creating a character who’s a hedge witch in a medieval-inspired world.

Entry 1:

• Keywords: magic, spells, witchcraft
• Content: “Magic users are called hedge witches. They brew potions, cast small charms, and read fortunes. The Church tolerates them as long as they don’t practice necromancy. Townspeople pay in food and favors rather than coin.”

Entry 2:

• Keywords: cottage, home, hut
• Content: “{{char}} lives in a stone cottage at the forest edge, two miles from town. Herbs dry from the rafters. Three black cats roam freely. Villagers knock before entering out of superstition, not politeness.”

Entry 3:

• Keywords: town, village, marketplace
• Content: “Millbrook has 300 residents. Market day is Wednesday. The baker refuses to sell to {{char}} since his wife blamed her for their son’s fever. The blacksmith is friendlier and trades repairs for healing salves.”

These three entries create a functional world. You could add fifty more, but these cover the essentials.

Modern Romance Scenarios

Character: A barista with a complicated past relationship.

Entry 1:

• Keywords: coffee shop, café, work, Brewtiful
• Content: “{{char}} works at Brewtiful Coffee on 5th Street. Morning shift, 6 AM to 2 PM. Regular customers include the construction crew, Mrs. Henderson who orders decaf lattes, and that one guy who never tips. The espresso machine breaks every Tuesday.”

Entry 2:

• Keywords: ex, James, former boyfriend
• Content: “{{char}} dated James for three years. He cheated with a coworker six months ago. They still have mutual friends, which makes social events awkward. {{char}} blocked his number but checks his Instagram when lonely.”

Entry 3:

• Keywords: apartment, home, roommate
• Content: “{{char}} shares a two-bedroom apartment with college friend Maya. Rent is $1,400 split between them. The heating barely works. Maya’s boyfriend stays over too often. {{char}} stress-bakes at midnight when can’t sleep.”

Notice how these entries create relationship depth and environmental context without overwhelming the character description.

Sci-Fi Universe Construction

Character: A smuggler operating between colony worlds.

Entry 1:

• Keywords: ship, Starling, vessel, spacecraft
• Content: “The Starling is a modified cargo hauler. Holds 40 tons. Jump drive was military surplus, technically illegal. Hidden compartment behind the coolant tanks. Registration papers are forged. Ship’s AI has a glitchy personality core.”

Entry 2:

• Keywords: Terraform Station, station, hub
• Content: “Terraform Station orbits the gas giant Helios. Population 50,000. Corporate security is strict in docking bays but lax in lower levels. Best place to find work is Sector 7’s bar district. Avoid Dock 23, it’s monitored.”

Entry 3:

• Keywords: cargo, shipment, delivery, smuggling
• Content: “{{char}} smuggles luxury goods, medical supplies, and occasionally people. Never weapons or drugs. Standard rate is 15% of cargo value. Has three regular clients: Dr. Yun needs medical scanners, the Lotus Syndicate wants alcohol, and someone called The Architect requests old Earth books.”

Three entries and you’ve established character, profession, setting, and moral boundaries.

Troubleshooting Common Problems

Problem: Keywords Not Triggering

Your conversation flows naturally but entries aren’t loading. Usually,y this means your keywords are too formal or specific. People don’t say “domicile” in casual conversation; they say “house” or “apartment.”

Solution: Look at your actual chat logs. What words do you naturally use? Add those as keywords.

Problem: Too Much Lore Loading

You mention one location and suddenly five different entries activate, eating all your token budget.

Solution: Your keywords overlap too much. Make them more specific. Instead of having ten entries all triggered by “city,” use specific district names or landmark names.

Problem: Character Ignoring Lorebook Content

The entry activates (you can tell because relevant information appears) but the character’s response doesn’t reference it.

Solution: Usually, this means your character’s main description contradicts the lorebook, or your entry is too vague. Make your lorebook entries more direct. Instead of “The character likes coffee,” write “{{char}} drinks coffee every morning and gets headaches without caffeine.”

Problem: Conflicting Information

You’ve built up so many entries that some contradict each other, and the AI seems confused.

Solution: Keep a master reference document outside Spicychat. A simple text file listing key facts ensures consistency. When you add new entries, check them against this master list.

Making Your Lorebook Work Long-Term

The biggest mistake people make is treating lorebooks as one-and-done. They spend hours creating entries, attach it to their character, and never touch it again.

Your lorebook should evolve with your story. After every few conversations, ask yourself:

What information did I have to explain manually that should be in the lorebook? What entries triggered but weren’t relevant? What new story elements have emerged that need their own entries?

Updates apply to existing chats automatically. If you realize your character’s workplace needs a better description and you update that entry, it’ll affect all conversations using that lorebook going forward.

Keep your entry count reasonable. Quality beats quantity. Ten well-written, frequently-triggered entries do more for your story than a hundred entries that never activate.

And remember the one-lorebook-per-character limitation. You can’t attach multiple lorebooks to a single character, so if you’re building multiple story worlds, you’ll need separate characters for each. Or, get creative and use one lorebook with keyword prefixes to separate different storylines.

For example, use “fantasy-” as a prefix for all your fantasy world keywords and “scifi-” for science fiction elements, then write entries that only activate when you naturally use those terms in conversation.

Your Next Steps

Start small. Pick your most-used character and create a lorebook with just five entries. Make them simple:

• One entry about their home
• One about their workplace or daily location
• One about an important person in their life
• One about a personality quirk or habit
• One about their biggest secret or fear

Test it in conversation. See what works. Add more entries as you discover gaps.

The goal isn’t to build the most comprehensive lorebook in Spicychat history. The goal is to build one that makes your conversations feel more consistent, more immersive, and more like interacting with a character who actually remembers your shared story.

Your AI characters are only as good as the information you give them. The lorebook is how you give them that information smartly, without turning every conversation into an exposition dump.

So go build something interesting. Your story world is waiting.

FAQs

Can I copy entries from one lorebook to another, or do I have to rewrite everything from scratch?

Right now, Spicychat doesn’t have a built-in copy function between lorebooks. Your best bet is keeping your entries in a separate text file as you write them, which also serves as a backup. When you want to reuse an entry, just copy-paste from your text file into a new lorebook. This actually works better long-term since you’ll want to track your entries anyway to avoid contradictions.

What happens if I use really common words as keywords, like “the” or “and”? Will my lorebook break?

The system won’t break, but you’ll waste your entire token budget. Common words appear in nearly every message, so that entry would load constantly, preventing other, more relevant entries from activating. Stick to specific nouns, proper names, and distinctive phrases. Think “Crimson Tower” instead of “tower,” or “Sarah’s bakery” instead of just “bakery.”

Do lorebooks work with group chats, or just one-on-one character conversations?

Lorebooks attach to individual characters, not to chats. In a group chat scenario, each character can have their own lorebook, and they’ll all function independently. So if Character A’s lorebook has information about the Silver Moon Tavern and Character B’s lorebook has different information about the same location, both sets of information could theoretically load if keywords trigger them. This can create interesting dynamics, but it also means you need to be extra careful about consistency if multiple characters share the same story world.