All guides

How to roleplay so the story doesn't fall flat

If your chats keep going in circles or the character feels flat, it's almost never the model — it's usually how the messages are written. Here's what actually works, based on watching a lot of good and bad sessions.

Write actions with asterisks, speech in quotes

The simplest habit that instantly makes roleplay read better: wrap physical actions and narration in asterisks, and put spoken words in quotes. It's the convention every character on the site is tuned for, so the AI mirrors it back to you.

*She leans against the doorway, arms crossed.* "You're late again."

Compare that to typing everything as one flat line. When you separate the two, the character knows what's an action and what's dialogue, and it starts answering in the same rhythm — a bit of movement, then a line of speech. That back-and-forth is what makes a scene feel alive instead of like a text thread.

Give the AI something to react to

A reply is only as good as the message it's answering. One-word answers give the character nothing to work with, so it either stalls or makes something up. The fix isn't writing an essay — it's leaving a hook.

"ok"
*I sit down across from her, still not meeting her eyes.* "I didn't think you'd actually show up."

Notice the second one does three things at once: it sets an action, gives away a bit of emotion, and ends on a line that begs a response. You don't need all three every time, but end your message somewhere the character can grab onto — a question, a reaction, a small decision.

Write your own side, don't script theirs

This is the big one, and it's the mistake that quietly kills the most roleplays. It's tempting to write what your character does and then also write how the other character reacts — "*I hug her and she smiles and says she forgives me*." Don't.

When you put words and actions in the character's mouth, you take away the only thing the AI is there to do: surprise you. You've already decided the outcome, so the reply has nowhere to go but to agree with you. Do that a few times and every scene starts feeling like you're talking to yourself — because you are.

Control your character. Describe your actions, your words, your feelings. Then hand the moment over and let the other side answer for itself. If you want a specific direction, steer it through what your character does, not by writing their lines for them.

*I confess everything and she immediately forgives me and hugs me.*
*I finally look up, voice shaking.* "I should have told you months ago. I'm sorry."

Set the scene early

The first few messages set the tone for everything after. If you want a slow, moody story, open slow and moody. If you want banter, open with banter. The character reads your energy and formatting and matches it, so the pace you establish in message one tends to stick.

Many characters have more than one opening scene — you can swipe between them before you start to pick the setup you like best. Use that. A good starting point saves you a lot of steering later.

Keep yourself in character too

The character will hold its role as long as you hold yours. Stay in the story — speak and act as your character, not as a narrator talking to the AI. When you want a different direction or a change of mood, steer it from inside the scene: have your character do or say something that naturally pulls the story that way. The more you stay in character, the more the character stays in theirs.

The tools for when a reply misses

Sometimes a response goes somewhere you didn't want. You don't have to argue with the character in the story to fix it — the chat has a few controls built for exactly this, and using them beats wrestling a scene into shape from the inside:

The gentlest fix is usually the best one: regenerate or edit first, and only reach for undo or restart when a scene is truly off the rails.

That's really the whole craft: write your half well, leave room, let the character live, and lean on these tools when a reply misses. Do that and the stories get better on their own.

Next: every character field, explained →