> For the complete documentation index, see [llms.txt](https://noshame.gitbook.io/noshame-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://noshame.gitbook.io/noshame-wiki/chat/roleplay-guide.md).

# Roleplay guide

You can do more than type dialogue. Use actions, out-of-character notes, and rewind tools to steer the scene.

NoShame is for adults 18+.

## Actions with asterisks

Text between asterisks is treated as an action, a description, or a change of scene — not as spoken dialogue. You can mix an action and a spoken line in the same message.

Examples:

* `*I put the keys on the table and sit down.* How was your day?`
* `*We're in the kitchen now.* I could use a glass of water.`
* `*A knock comes from the hallway.* Did you invite someone?`

You can also write other people or a sudden event into the scene the same way. The character will react in the story. This is a way to add someone to a scene, not a separate group-chat feature.

## Out of character (OOC)

To nudge the scene without the character treating the line as in-story speech, you can try an out-of-character note:

`(OOC: slow this down)`

or

`(OOC: stay shy for the next few replies)`

OOC is a common roleplay convention. It often works, but it is not a guaranteed, built-in control. If the character ignores it, go back to asterisks or a plain instruction, such as `*I ask you to slow down.*`

## Rewind, edit, and regenerate

If a scene went the wrong way:

1. Edit a message you already sent and generate a new reply, or regenerate the character's last reply. See [Chatting](https://noshame.gitbook.io/noshame-wiki/chat/chatting.md).
2. To fork the story from an earlier point, delete every message from that point forward, including the one you want to redo, then send a different line.

Deleted messages cannot be brought back. Only delete forward from the point you want to change.

## Tips

{% hint style="info" %}
Short, clear actions work better than a long list of instructions in one message. Set the place, the action, and the tone, then let the character answer.
{% endhint %}

## Quick answers

| Question                  | Answer                                                                                                     |
| ------------------------- | ---------------------------------------------------------------------------------------------------------- |
| How do I write an action? | Put it between asterisks, like `*I open the window.*`                                                      |
| What is OOC?              | An out-of-character note, often written as `(OOC: …)`, to steer the scene. It often works, but not always. |
| Can I take a scene back?  | Yes. Edit, regenerate, or delete forward from the message you want to change.                              |

Related: [Chatting](https://noshame.gitbook.io/noshame-wiki/chat/chatting.md), [Chat modes](https://noshame.gitbook.io/noshame-wiki/chat/chat-modes.md), [You in the story](https://noshame.gitbook.io/noshame-wiki/chat/you-in-the-story.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://noshame.gitbook.io/noshame-wiki/chat/roleplay-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
