Use chat controls and slash commands
Review scope: Linked public documentation checked October 30, 2026. Examples are proposed checks, not recorded OD results; use your account's current controls.
November 1 source check: The chat-controls guide was re-read and still displays July 27, 2026 as its modification date. Its dated model table does not establish today's account inventory; follow the selector and settings actually offered in your account. No new model comparison was run.
You will adjust one chat setting, steer a single reply, and distinguish regeneration from a new story event.
A chat model is the system generating the written response. A slash command begins with / and requests a special chat action. Neither is the same as choosing an image style.
Before you begin
Open a practice conversation. Keep a copy of any important current state before changing the conversation history.
Adjust a setting
- Open the chat settings. Locate the model selector and response controls available in your account.
- Record the starting selection. Use the displayed model name and any per-message charge. Do not infer the underlying model from a nickname or another person's screenshot. Check the new selection's displayed cost before sending a paid test.
- Leave most controls alone. Choose one problem you want to address.
- Change one control. Use the table below to choose a relevant one.
- Send a short test. For example: “Mira, explain the two most useful places to search for the map.”
- Compare the response with your goal. If it does not help, return the setting to its previous value before trying another change.
| Control | What to observe |
|---|---|
| Response Length | Whether the reply is brief enough, complete, and leaves room for you |
| Creativity | Whether additional variation helps or disrupts the established scene |
| Lust Level | How readily the chat adopts sexual tone; choose a lower setting for this archive exercise |
| Chat model | Whether the same character and instructions are handled usefully |
The chat-controls guide describes these controls. Their names, ranges, and available models should be read from your own selector.
Public marketing pages and dated guide tables may list different model names. Use the actual selector for your account and route; do not turn either list into a universal ranking, infer backend identity, or invent controls that are absent. A saved test should identify the displayed model and date.
Compare wording separately from a model switch
Use this original two-stage practice plan. First save one short question and the complete relevant setup. Compare the baseline and one wording revision on the same selected model, restoring the scene and context for each trial. Then, if you want to compare models, keep the chosen wording unchanged and repeat through the actual selector. Check any new charge before sending.
Record the visible model label verbatim with the date. A guide's suggested use for a named model is not a measurement of your character or proof that the underlying provider stayed the same. A prose request such as use a smarter model is not a verified model-selection control. The chat-controls guide describes the actual selector and response settings; the OD prompt lab provides wording exercises.
Direct one reply
- Click the message box and type
/. - If a command menu appears, select /direct.
- Enter the direction below and send it once.
/direct Rowan arrives at the archive carrying a sealed parcel.
Leave Alex's response to the user.
- Read the next reply. Rowan's arrival should be the requested event; it should not become a repeated arrival in later replies.
- If the menu does not offer the command, use the controls your chat actually exposes. Do not invent a new slash command and assume the site will execute it.
Ask for an analysis
Use /analyze, when offered, for an out-of-character answer without continuing the roleplay, as described in the command reference. Ask about the available context:
/analyze What does Mira currently know about the missing map,
and which questions are still unresolved?
Treat the answer as an interpretation of the context. Compare it with what actually happened rather than treating it as a database query or prediction. The guide describes slash commands as hidden from the story; that is not a privacy guarantee or a reason to put passwords or other secrets in them.
Expand a draft
With /suggest, when offered, supply the idea you want help expressing. Review the proposed wording before sending the resulting story message. For example, expand “Ask to inspect the catalog” without adding a decision to leave the archive. The same command reference explains the three commands.
Regenerate edit and continue
- Regenerate asks for an alternative version of a reply. Review which version is retained; it should not automatically count as an additional completed game event.
- Edit your message when you supplied a wrong fact or unclear action. After changing earlier history, check any affected memory and state.
- Continue, if offered, requests further output. Inspect whether it continues the same moment or advances the fiction before using it in a game with counters.
These distinctions matter whenever RPG state depends on completed events.
Check your result
You should know which single setting changed and whether it helped. You should also be able to tell a temporary direction from a persistent instruction.
If something goes wrong
- The reply is cut off: reduce the target length or request a continuation, then inspect the resulting state.
- The story repeats itself: correct contradictory setup text before repeatedly regenerating.
- A model switch changes behavior: rerun the same simple check; do not assume settings transfer their effects identically.