Shared-world authoring · 7 min read

Dreamle vs Character.AI: Give the Cast One Shared World Record

Use Character.AI’s current Lorebook controls and a small original example to distinguish shared lore from a live group conversation.

On this page
  1. Shared lore is different from simultaneous speakers
  2. Draft three entries with different jobs
  3. Keep core identity in the character
  4. Link and publish deliberately
  5. What Dreamle’s public route establishes

An ensemble can share a bridge, a deadline and a map without sharing every private motive. A useful world record preserves the common facts while leaving the people distinct.

Dreamle’s public group route is visible, while Fantasy World currently displays a subscription requirement. The guest pages do not establish how a shared fact is attached to individual characters. Character.AI provides more specific current documentation for that part of the job.

Shared lore is different from simultaneous speakers

Character.AI’s Lorebooks guide, updated September 17, 2026, describes a beta feature with early creation/editing access for c.ai+ subscribers. Entries activate through keywords, and one book can link to several characters.

That can support a common setting across different chats. It is not, by itself, a group-chat feature. A person speaking to the leader today and the archivist tomorrow can still use shared world facts without both characters appearing in one live conversation.

A group requires additional mechanics: which participants are present, who speaks next and what each has learned during the exchange. Neither a world label nor a linked book should be substituted for evidence of those mechanics.

Draft three entries with different jobs

This original plain-text example follows the structure in Character.AI’s import guide. It is a proposed draft, not a tested import.

Lorebook Name: The Dusk Observatory
Lorebook Description: An original fictional expedition of adult characters.

Entry Title: The bridge deadline
Keywords: bridge, crossing, dusk
Content: The east bridge closes at dusk. The expedition must choose a route before then. Do not solve a delay by moving the deadline without a story event.

Entry Title: Pax the archivist
Keywords: Pax, archivist, map symbol
Content: Pax is a 36-year-old archivist who can interpret the old map legend. Pax does not know the bridge's current condition until someone reports an inspection.

Entry Title: Remy the engineer
Keywords: Remy, engineer, load limit
Content: Remy is a 38-year-old engineer who understands equipment and load limits. Remy does not know the historical map symbol until Pax explains it.

The first entry is a world constraint. The other two describe people and knowledge limits. The distinct jobs give the model different instructions, but they are not an access-control system. A shared book may make an entry available in several chats; a sentence saying that Pax does not yet know a fact is a narrative constraint, not a guarantee that information is technically hidden from Pax. Do not use a shared entry to store an actual secret that must be inaccessible to other linked characters or readers.

Keep core identity in the character

Character.AI’s guide recommends keeping always-relevant identity and behavior in the character definition, while situational world information belongs in lore entries.

For Iona, the leader, the definition should establish decision style and motivation. The bridge rule should not become Iona’s entire personality. Conversely, a brief recurring identity should not depend on a rarely used keyword being mentioned.

The authoring guide warns about shared {{char}} references: that placeholder means whichever linked character is currently chatting. If a shared entry says that {{char}} owns the observatory, every linked character may receive that same fact. Name the owner directly when a fact belongs to one person.

The Lorebooks guide documents Create → Lorebook, adding entries, linking owned characters, and publishing. A draft is not yet used in chat. When a published book is edited, changes need the documented Update action to become live.

This matters for a corrected deadline. A note visible in the editor may still be a draft change while the published version supplies the old rule. Keep the correction in the record actually used by the conversation.

Visibility is another decision: public lorebook settings can allow other creators to link their characters, while private availability has its own subscription condition. Sharing a world and keeping it personal require different choices.

What Dreamle’s public route establishes

Dreamle’s Create a Group and Fantasy World destinations establish product routes, not a verified equivalent to the above entry system. This comparison does not claim Dreamle lacks shared records; it says their mechanics were not exposed in the reviewed public view.

For a creator whose immediate task is maintaining common lore, Character.AI has the clearer documented control path. For a live ensemble, the actual group mechanics still need separate evidence.

No account, lorebook, group or import was created. The practical deliverable is a small shared-world draft that can be reviewed before any paid setup, with each character’s knowledge kept explicit.

Sources and scope

This comparison separates documented capabilities from editorial interpretation. Source access and any limitations are described in the article; a suggested evaluation is not a claim of completed testing.

← More Dreamle articlesHow this was researched