Tutorials

Build stronger roleplay worlds, section by section.

These tutorials explain what each creator area does, why it matters, and how to fill it in so the AI has useful structure instead of vague prose. You can skim the steps, then copy the example shapes for your own scenarios.

Scenario Creator World, premise, opening scene, rules Characters Voice, appearance, motives, relationships Lore Cards Factions, locations, family links, secrets Personas Who the user enters the story as Memory Continuity, recall, maps, timelines Images & Models Visuals, parameters, response length

Scenario Creator tutorial

A scenario is the playable world. It tells the AI where the story starts, who matters, what the tone is, what the rules are, and what should stay true as the roleplay develops.

1

Main Details: give the user a clear promise

Main Details are what users see before they start. They should explain the fantasy quickly without spoiling every secret.

Why we do this: the title, description, genre, tags, and banner help users understand what kind of roleplay they are entering. The AI also benefits when the scenario has a clear identity instead of a vague aesthetic.
Name the core hook.Use a title that feels specific: a place, a threat, a relationship, or a dilemma.
Write a short public description.Describe the playable situation, not the whole plot. One strong paragraph is enough.
Choose genre and tags honestly.Tags help users find the right tone and help set expectations before the chat begins.
Add a banner that shows the world.The image should communicate setting or cast energy, not just look pretty.
Example title
Friday Night, No Witnesses
Example description
A late-night yakuza lounge story about loyalty, secrets, and what happens when one outsider sees too much. Start at the Velvet Lounge as old alliances begin to crack.
Scenario Creator Panel
2

Scenario Brief: define the world without writing a novel

The brief is the AI's foundation. Use it for stable facts, current setup, tone, and the central tension.

Why we do this: models follow clean structure better than decorative prose. A brief should make the world playable: who has power, what is dangerous, what is unresolved, and what the user can affect.
Start with the present situation.What is happening now? Where does the roleplay begin?
Add background only when it changes behavior.History matters when it explains fear, loyalty, secrets, rules, or conflict.
List active pressures.Use bullets for factions, debts, secrets, deadlines, betrayals, or missing people.
Keep secrets marked as secrets.If only one character knows something, say who knows it. Do not leave it as general world knowledge.
Brief shape
  • Current situation: The user arrives at the Velvet Lounge after a private meeting goes wrong.
  • Power structure: The Yamada-gumi controls the lounge, tower, and enforcement network.
  • Hidden tension: Hiro suspects someone inside the family is leaking information.
  • Player pressure: The user is useful, watched, and not fully trusted.
3

Opening Scene: give the AI a playable first move

The opening should put the user inside a moment with sensory context, present characters, and a reason to respond.

Why we do this: a strong opening prevents the AI from asking generic setup questions. It gives the story motion immediately.

Stronger

The lounge is too quiet for a Friday. Hiro stands near the back booth, jacket still wet from the rain, watching the door as if he already knows who is about to walk in.

Weaker

You are in a city full of crime and romance. Many things can happen. What do you do?

Name the location and moment.Ground the first reply in a place, time, and atmosphere.
Place important characters on-screen.The AI should know who is present before it writes reactions.
End with tension, not instructions.Give the user something to react to: a look, a question, a threat, a discovery.
4

Custom Instructions: control behavior, tone, and boundaries

Instructions are not lore. They are rules for how the AI should write and what it should avoid.

Why we do this: instructions help keep the AI in the right style. They also stop common problems like explaining character behavior, rushing romance, revealing secrets too early, or writing as the user.
Instruction examples
  • Do not write actions, thoughts, or dialogue for the user.
  • Keep character knowledge separated. Characters cannot act on secrets they have not learned in-scene.
  • Use direct, grounded prose. Avoid summarizing emotional conclusions for the reader.
  • Let conflict breathe. Do not resolve threats, attraction, or suspicion too quickly.

Characters tutorial

Characters are more than names. They tell the AI who can speak, how they behave, what they want, what they look like, and how they relate to the rest of the cast.

1

Build the cast from the story outward

Add the characters the AI must actively write first. Background names can wait until they matter.

Start with the main pressure points.Who creates danger, intimacy, loyalty, or choice?
Give every character a role.Examples: heir, handler, rival, doctor, witness, informant, estranged sibling.
Give every character a want.Characters stay consistent when the AI knows what they are trying to protect or get.
Separate visible appearance from personality.Appearance is what someone can see. Personality is how the character behaves.
AppearanceBlack suit, split knuckles, expensive watch, rain-dark hair.
PersonalityControlled, territorial, impatient with weakness, protective when cornered.
Private motiveNeeds to prove he can lead without becoming his father.
VoiceShort sentences. Rarely explains. Uses silence as pressure.
Character Detail Card
2

Use character instructions for behavior the AI must protect

If a character must never soften, never flirt first, never reveal a secret, or always defer to someone, put it in their instructions.

Useful instruction

Hiro does not explain himself unless forced. He watches before speaking, tests loyalty through small demands, and becomes colder when emotionally exposed.

Too vague

Hiro is mysterious, hot, dangerous, and intense. Make him cool.

Tip: short, specific behavior rules are easier for the AI to preserve than long aesthetic paragraphs.
Character Editor

Lore Cards: Field by Field

Lore cards are reusable facts the AI can recall when relevant. Here is how to fill out the Lore Card creation form.

1

Lore Details

The core information that makes up a lore card.

Card Name (Keywords):
This is how the AI knows to pull the card. Use exact names or phrases that characters will actually mention in the chat.
Example: "Velvet Lounge", "The Kakun", "Izumi Motel"

Category:
Select the type of card from the dropdown (Location, Faction, Event, Custom, Item, Rule/System). This helps the system categorize the lore for the AI.

Entry:
Write the actual facts here. Do not write paragraphs of atmosphere; write clear, undeniable facts. If something is a secret, write "Only [Character] knows this."
Example:
- Owner: Yamada-gumi
- Location: Roppongi district.
- Secret: The locked back exit leads to a service alley used for quiet removals.

2

Faction & Group Linking (Advanced)

If you set the Category to "Faction", "Family", or "Group", new fields will appear to build a Cast Board.

Linked Characters:
Click here to attach characters from your Hub or Scenario Cast. This tells the AI who belongs to this faction.

Character Role / Relationship:
Next to each linked character, define their rank or relationship to the group. Keep it brief.
Example: "Heir. Runs daily operations. Senior to Kai." or "Matriarch. Wife of Soichiro."

Personas tutorial

A persona is who the user plays as. It gives the AI a stable identity to react to instead of treating the user as a blank narrator.

1

Create the role the story should recognize

Personas work best when they describe social position, visible presence, and emotional baggage.

Name and appearance.Give the AI enough visible detail for characters to recognize and react naturally.
Background.Add the facts other characters may know, plus anything private the AI should remember.
Personality and boundaries.Explain how the persona tends to respond under pressure.
Choose the persona before chat.The active persona is what the current story uses.
Persona example
Morgan Vale: British, sharp-tongued, observant, out of their depth but not helpless. Dresses practically, notices exits, hides fear behind sarcasm. Does not trust authority easily.
Custom Personas Editor

Memory and Continuity tutorial

Memory helps long stories stay coherent. It does not mean every message is sent forever. The app stores summaries, recalls relevant cards, and tracks continuity so the AI has the right context at the right time.

1

Session Memory: what gets recalled

Session memory cards are compact records of important developments. The AI retrieves the most relevant ones before replies.

Open Memory in the chat.Use it to see message count and memory card count.
Create or summarize when a lot has happened.Good cards capture decisions, secrets, injuries, promises, location changes, and relationship shifts.
Pin absolute facts.Pin facts that must never drift, such as a character being dead, married, missing, or unable to know a secret.
Useful memory card

Hiro took Morgan to the Izumi Motel on 17 January 2026 after the lounge incident. The visit was kept secret from Axel, Kai, and the Yamada household. Hiro knows; Morgan knows; others do not.

2

Living Story Continuity: timeline, status, and knowledge

Living Story Continuity is the paid structured view of what happened, who changed, who knows what, and what live statuses currently exist.

Why we do this: roleplay breaks when the AI gives the wrong action to the wrong character or reveals a secret to someone who was never told. Continuity gives the model a compact timeline and knowledge gate.
TimelineWhat happened, when, where, and who did it.
StatusAlive, injured, missing, deceased, married, estranged, captured, hidden.
KnowledgeWho knows the secret, who suspects it, and who does not know.
Live changesNew injuries, missing status, deaths, secrets learned, betrayals, or temporary conflict.
3

Memory Map and Cast Board: visual checks

These views help you see what the AI is working with without reading every memory card manually.

Use the Memory Map to inspect recall.Orange dashed lines show memories recalled for the current scene. Grey links show memory-card connections.
Use the Cast Board for stable structure.Faction, family, and group cards help organize characters into visual trees using creator-defined facts.
Correct the right source.If the tree is wrong, edit the faction/family/group card. If current status is wrong, resync Living Story Continuity.

Images, Models, and Settings tutorial

Images give scenarios visual identity. Model settings control the shape of replies: shorter or longer, steadier or more surprising, direct or more descriptive.

1

Generate images that support the story

Use images for banners, characters, locations, and scene mood. They should clarify the world instead of distracting from it.

Describe subject, setting, and style.Example: four men in a smoky private lounge, cinematic CGI, dramatic bar lighting.
Avoid asking for photo-real output.Use stylized CGI, cinematic render, illustrated realism, anime, painted, or graphic novel language.
Reuse consistent descriptions.Character appearances should match the text profile so the visual identity stays stable.
In-Chat Image Generation
2

Set response length and model behavior

Parameters do not fix weak scenario writing, but they can shape pacing once the scenario is clear.

Shorter repliesBetter for fast back-and-forth, dialogue, and user control.
Longer repliesBetter for narration, scene setting, and multi-character moments.
Lower temperatureMore stable, less surprising, better for continuity-heavy scenes.
Higher temperatureMore varied, more dramatic, more likely to improvise.
Best habit: if the AI is drifting, first check scenario instructions, character instructions, lore cards, and memory. Then adjust model settings.
3

Use Custom Instructions for recurring chat rules

Custom Instructions are for short, persistent preferences that should follow the entire chat.

Use them for tone and boundaries.They work best for things like prose restraint, handling hidden information, or what the AI should avoid fixating on.
Keep them short.They are not meant to replace scenario writing, lore cards, or character profiles. Think “extra reminder,” not “rewrite the whole setup.”
← Back to Quick Start Continue to Memory →