What cards and lorebooks actually organize
A character card packages information about a fictional person: their description, behavior, scenario and example dialogue may be represented in structured fields. Exact fields depend on the format and software. A card is not a complete living simulation. Its content still has to reach a model in a usable form when a reply is generated.
A lorebook organizes information about the setting or cast. In systems that support activation rules, selected entries can be included when relevant keywords or conditions appear. That can reduce the need to repeat the whole encyclopedia. It can also miss an entry, include the wrong one or use too much context if configured poorly.
Chub’s official documentation covers these creator workflows. Its terms require users to be at least 18, and the service has adult-oriented options. This is a comparison for eligible creators, not a recommendation for children or a guide to bypassing restrictions. Consult the current official documentation rather than assuming all card formats and lore features behave alike.
Compare workflows, not promises of infinite lore
If you enjoy tuning structured entries, Chub’s documented card and lorebook approach may be relevant. If your project is an original character with a visual home, conversational testing and a short film, KOORI offers a different creative route. Neither choice removes the need to edit your writing and check the generated result.
KOORI does not establish a Chub-card importer or a keyword-triggered lorebook editor in this tutorial. Do not expect a downloaded card to populate compatible fields automatically. Translate your own permitted material into a concise character concept and keep the larger world bible separately.
Consider portability, visibility, costs and permissions before publishing. An exportable file may contain material you do not own. A private project may become visible if you submit it publicly. Permission to use AI output is not a blanket guarantee of exclusive copyright. Keep your original drafts and review the platform’s current terms.
Write a world bible the next scene can actually use
A world bible is your source of truth, not a document you must paste in full every turn. Divide it into stable rules and changing events. Stable rules include geography, magic limits and a character’s defining motive. Changing events include an opened gate, a new promise or a relationship that has become less certain.
For a cozy mapmaker story, start with a river town, a bridge that moves at sunset and a dragon who draws maps but dislikes leaving home. Add one relationship and one unanswered question. You already have enough material to make a decision: cross before dusk, ask the dragon to come with you, or investigate an erased path.
Write negative facts too. The dragon cannot teleport. The librarian has never visited the island. The sealed letter has not been read. These constraints stop a plausible-sounding invention from quietly rewriting your story. When a fact changes, replace its old version in your note rather than keeping both.
World bible: Riverglass is an original town where bridges move at sunset. Magic can illuminate a map but cannot transport a person. Orrel, an adult dragon cartographer, wants to finish a route he is afraid to walk. Sena, an adult librarian, owns a sealed letter from the island. Neither has read it. Keep this platonic, non-explicit and gently adventurous.
A practical character-world workshop in KOORI
Begin with one viewpoint character. A large supporting cast can exist in your notes, but a single chat is not a guaranteed synchronized simulation of independent characters. Make the lead’s behavior clear enough that they can carry a quiet scene without reciting the whole setting.
Turn the bible into a playable opening
- Step 1: Reduce the world to three active facts. Select the location, the relevant rule and the immediate problem. For the first scene: the bridge moves soon, the map is unfinished, and Orrel wants help without admitting fear.
- Step 2: Describe the original lead. Open character mode after sign-in and onboarding. Specify appearance, motive and an observable speech habit. Orrel measures distances precisely but changes the subject whenever travel becomes personal.
- Step 3: Choose artwork with repeatable anchors. Review an available image style and identify a few distinctive visual details, such as a blue satchel and a brass compass. Avoid relying on dozens of tiny costume details remaining exact in every future image.
- Step 4: Write the card and room opening. Place Orrel at the bridge holding a partly finished map. He asks you to check a line but has not decided to cross. Leave the user’s role and response open enough for meaningful choices.
- Step 5: Test a rule and a disagreement. In the character room, ask whether magic can skip the river, then suggest leaving before sunset. Check that the reply respects the world rule and the lead’s motive. Revise invented shortcuts rather than treating them as canon.
- Step 6: Save and maintain a scene summary. Finish creation and review any credit requirement. Keep the current facts in your own note as you chat. For a picture or Reel, supply only the visual moment and the rules that affect that moment.
Context and memory are different from world knowledge
Saved history preserves messages for the product; a context window limits what a model can use in a particular response. Explicit memories or retrieved lore are additional mechanisms, not proof that every earlier detail will appear. A system may know a character’s birthplace while losing track of the last promise made in the scene.
KOORI uses character information and available context, but this guide does not guarantee reliable cross-session persistent memory. Before a consequential scene, repeat the critical world rule and current state. After a contradiction, correct it specifically: the bridge has not moved yet; Orrel has not agreed to cross. Short factual corrections are more useful than demanding that the AI remember everything.
If you share a world with other creators, circulate a sanitized bible rather than private chats. Label which facts are fixed and which are invitations to improvise. A shared vocabulary helps build a fandom, but it does not give anyone automatic permission to reuse another person’s artwork or character commercially.
Character-card and worldbuilding FAQ
Does a lorebook guarantee perfect memory?
No. Activation, relevance, context limits and the model’s interpretation affect what appears in a reply. A lorebook is a way to organize and supply information, not unlimited recall.
Does KOORI import Chub cards?
A compatible card importer is not verified in this workflow. Use your own permitted notes to create a character and keep your world bible separately.
How much lore should my first scene contain?
Enough to explain a location, a rule and a decision. Introduce other facts when they change what the character can do, rather than pasting every historical detail immediately.
Can I make a video from my world?
KOORI’s Reel creator uses saved characters and a reviewed storyboard. Choose one clear action and check the credit requirement before filming. A video does not guarantee consistency with every line of your world bible.
Sources and further reading
KOORI publishes this Journal. Comparisons describe different creative workflows, not independent safety certification or a promise of flawless AI behavior. Features and eligibility can change; consult official documentation and terms.
More from KOORI Journal