TastyChat Guide
Key concepts

Lorebooks

The story background you choose for a conversation — what goes in it, how a character recommends one, what other readers can see, what happens when it is blocked, and why a saved unit is not a guarantee.

A lorebook is the background of a story: the people, places and things in it, the rules of its world, how it can start, and what can happen in it. A character can draw on it without any of that being restated in every message.

A world or setting is one kind of thing you can put in a lorebook. It is not what a lorebook is — plenty of useful lorebooks hold nothing but relationships and habits.

What goes in a lorebook

Every lorebook starts with a core description, which is always shown to readers and is part of every reply. Below it, the creator adds only the parts the story needs:

  • subjects — people, places and things;
  • world rules;
  • starting situations a conversation can begin from;
  • roles a reader can play;
  • possible events;
  • secrets, attached to a subject or to the world as a whole.

New parts are shown to readers from the start. Secrets are kept for readers to discover.

Who chooses the lorebook

You choose the lorebook for each conversation, and "no lorebook" is a choice too. You can pick one of your own lorebooks, someone else's public lorebook, or a link-shared lorebook someone sent you a link to. A choice applies only to that conversation.

A character's creator can recommend a lorebook. It is picked for you when you first talk to that character, but you do not have to keep it, and a recommendation does not give you access to anything you could not otherwise use. A character that other people can reach can only recommend a public lorebook. When you start a new conversation with the same character, your previous choice comes first.

An adult lorebook can be chosen only for an adult character, and only by a reader who meets the age and display conditions for adult content.

If you change the lorebook after a conversation has started, you decide how: start a new conversation with it, or continue this conversation with it.

What other people can see

A lorebook's owner sees everything in it. Every other reader sees the same limited view, whether the lorebook is public or link-shared:

  • the core description and the parts shown from the start;
  • details they have discovered themselves in their own conversations.

Anything not yet discovered stays out of view. When a known subject still has undiscovered details, the reader sees one unnamed line saying so — not how many details there are, what they are called, or how long they are. The settings that decide when something comes up are not shown either. A detail one reader discovers is shown to that reader only. Someone who is not signed in sees only the short description.

A lorebook that was published back when entries were never shown keeps them hidden until its creator confirms the disclosure. A creator is told before publishing that what is shown from the start is visible to every reader, and that discovered details are visible to the reader who discovered them.

Being able to read a lorebook does not make copying it allowed. Choosing someone else's public lorebook for your conversation, or recommending it from your character, is what public lorebooks are for; copying its content into a lorebook of your own without permission is not. Whether something was copied is decided by an operator who reviews the report and its evidence — a report on its own, or two lorebooks looking alike, does not decide it. Publishing a lorebook does not guarantee income, and no rule can fully stop copying.

Once other people have used it

When another account has chosen your lorebook and a reply was completed with it, the lorebook is protected for them. You can keep editing it, but you can no longer delete it or narrow who can reach it, and if it was used with a non-adult character you can no longer mark it as adult. Your own tests, a choice without a completed reply, and failed replies do not count.

When a lorebook or character is blocked

An operator can block a lorebook or a character. Nobody can use blocked content until an operator lifts the block, including its creator. The creator sees only its name and its blocked status in My AI.

When a lorebook is blocked, every character recommendation of it is removed and the characters' creators are told. A conversation that chose it stops before the next reply and nothing is charged. You are told only that the lorebook cannot be used right now, and you choose: continue without a lorebook, or pick another one. If an operator confirmed which lorebook was the original and you can use it, it is suggested, but nothing changes until you choose. If the block is lifted and you have not picked something else, the lorebook is used again from the next reply. The same pause happens when a lorebook stops being available to you for another reason, such as its owner withdrawing it before anyone else used it.

When a character is blocked, its past conversations stay readable, but no new message, regeneration or continuation can be made. A character whose lorebook alone was blocked is not blocked itself.

Separately from blocking content, an operator can give the creator a warning, or a 3, 7, 14 or 30 day account suspension. The two are kept apart: an account suspension ending does not lift a content block, and lifting a block does not change the account.

A sanction does not reach backwards into money: earnings recorded before a sanction are not taken back or moved to the original creator. The usual adjustments for refunds, fraud and chargebacks still apply.

An example subject

The example below is written for this guide. It is written text, not a model output.

Lorebook subject for a recurring location
The Moonveil Inn is the two-storey inn at the edge of the trade road where returning
parties stop before reporting to the guild. The common room is loud until midnight and
empty by one. The innkeeper keeps a ledger of who owes for a room and never forgets an
entry. Rooms upstairs are cheap, cold, and the only ones with a lock.

It is written as facts, not as instructions. That is what makes it reusable: a character can mention the ledger, or the cold rooms, or neither, depending on what the conversation actually needs.

Saved parts are candidates, not guarantees

The core description is part of every reply. The other parts share the room that is left, so a saved part is not guaranteed to be used in a particular reply. Write each part so a conversation still reads well when it is not pulled in.

Changes reach existing conversations

A lorebook is never frozen into a conversation. When its owner updates the lorebook — or, for someone else's public lorebook, once the update is approved — the new version is used from the next reply, without restarting the conversation. A character's recommendation changing does not move a conversation that is already open; only your own choice does.

Lorebook, memory, or persona?

  • A lorebook is a story's background. A creator writes it, and you choose it for a conversation.
  • Memory belongs to one conversation and is written by you.
  • A persona is about you, not about the story, and is never published.

On this page