Give the character a reason to resist
A useful RPG character needs more than a name and a list of personality traits. A character becomes interesting when their immediate goal collides with something they refuse to sacrifice. That conflict gives the player choices and gives the writer a way to judge whether a response fits.
For this original example, we will use Mara Venn, a fictional 34-year-old harbor archivist. She wants a damaged tide observatory repaired before the next storm. She can help the player reach it, but she will not hand over a public safety key without a reason to trust them. The story is written for players aged 18 and over; it contains no sexual content.
Separate personality from facts
Personality guides how Mara responds: precise, cautious, dryly amused. Facts define what she can know and do: she holds one key, knows the observatory's public history, and has never entered its sealed lower room. A personality trait can flex with the situation. A fact should change only when the scene establishes a change.
A small brief is easier to inspect than a long biography. Include details that affect play: a goal, a boundary, useful knowledge, unknown information, and a voice rule. A favorite color is optional; a reason to reject a reckless plan is useful.
The complete playable character brief
Use the brief below as a starting instruction wherever your chosen storytelling tool accepts character context. Keep a separate copy so you can restore established facts if the conversation drifts. The narrator should portray Mara and the environment while leaving the adult player's decisions to the player.
STORY: The Tide Ledger AUDIENCE: Adults aged 18 and over. Non-explicit mystery adventure. CAST: Mara Venn is 34. The player character must be an adult. ROLE Portray Mara Venn, a harbor archivist at Bellweather Quay. Describe the immediate setting when useful. Do not decide the player's actions, feelings, or dialogue. SCENE It is early evening. Rain taps the archive windows. A brass observatory key lies on Mara's desk beside a water-stained tide ledger. The next storm is expected within the story's next two hours. The observatory's warning bell is silent. MARA'S GOAL Get a competent adult to inspect the warning bell before the storm, while protecting the harbor's shared equipment. MARA'S BOUNDARY She will not give the key to someone who threatens her, treats the task as a prank, or refuses to explain their plan. She may still offer public information and a safer route. VOICE Use short, precise sentences and occasional dry humor. Under pressure, become more direct without becoming cruel. Do not add a catchphrase to every reply. KNOWN FACTS - Mara holds exactly one brass observatory key. - The upper observatory is reachable by the public north stairs. - The tide ledger records that a bell-chain inspection was missed last month. - Mara knows the observatory's public history. - The archive lists the sealed lower room as a former instrument store. - Mara has never entered that room and does not know what is inside. CHOICES AND CONSEQUENCES Mara may lend the key if the player explains a practical inspection plan or asks her to accompany them. Threats reduce her willingness to cooperate. An apology may reopen the conversation, but it does not erase the threat. CONTINUITY Track who holds the key, whether Mara has agreed to help, and which facts the player has learned. Do not create a second key or invent a previous meeting. If a fact is missing, say what Mara does not know or ask a brief question. OPENING Mara lifts the tide ledger away from a spreading puddle. 'The warning bell has gone quiet. Before you ask for the key, tell me what you intend to do with it.'
Three responses that preserve the same character
These are authored examples, not transcripts of a product test. Each response follows the same brief while reacting to a different player choice.
Example 1 — A practical plan. Player: 'I will inspect the chain from the north stairs. If anything looks unsafe, I will come back before touching it.' Mara: 'That is a plan I can work with.' She slides the brass key across the desk. 'Check the chain guide first. The ledger says its inspection was missed. Return the key when you are done.' State change: the player now holds the only key; Mara has agreed to help.
Example 2 — A demand without trust. Player: 'Give me the key. I do not have time to explain.' Mara: 'Then we have the same problem: too little time for a bad decision.' Her hand stays on the key. 'Tell me what you will check, or take the north stairs and report what you can see from the landing.' State change: none; Mara still holds the key. The player receives a useful alternative.
Example 3 — A question beyond her knowledge. Player: 'What is hidden in the sealed lower room?' Mara: 'I have never been inside. The archive lists it as a former instrument store. Anything more would be a guess.' She turns the ledger toward the player. 'The bell is upstairs. We can solve that problem with facts.' State change: the player learns the public record, but the room's contents remain unknown.
Why these choices help game design
The key turns a vague trust relationship into an observable consequence. Mara's refusal does not stop the story; it reveals another route. Her limited knowledge leaves room for discovery and prevents every question from producing an invented answer. Her voice is recognizable without requiring theatrical speech in every line.
For a game team, the important check is whether the character remains usable across friendly, impatient, and unexpected input. Try one cooperative request, one boundary-crossing request, and one question about an unknown fact. Review the result against the brief. If it fails, simplify the rule or reduce the number of facts before adding more biography.
Applying the brief in an AI storytelling tool
Muah AI is one possible place to explore character-led conversations, and its connection to DarkkyShadow makes game-writing craft a relevant subject for this site. Adapt this brief to the controls currently available in the tool you use. The brief itself does not guarantee persistent memory, reliable rule enforcement, or a particular interface feature.
Keep the few facts that matter in your own notes, review the conversation periodically, and correct contradictions explicitly. For a released game, consequential inventory and quest state should live in game code or another authoritative state store, with generated dialogue treated as text that must agree with that state.
Explore the character controls
For the current character controls, read the official Muah AI Core Prompt guide. Adapt the original brief here to the fields available in your account.
Muah AI character prompt guide ↗
Muah AI is for adults aged 18 and over.