Xotic chat settings: adjust reply length, style and pacing

By Daniel Kraus

When a Xotic conversation feels wrong, identify the problem before changing the model. A reply can be too long, move the scene too quickly, or use narration when you wanted dialogue. Those are different problems. This guide gives you a small, repeatable way to adjust one variable and judge whether it helped.

We checked Xotic’s official documentation on October 2, 2026. We have not run a paid-account experiment or measured one model against another. The exercise and evaluation sheet below are our own proposed workflow, using a fictional, non-explicit scene. Read the Xotic review for the broader product decision.

Locate the setting and check its scope

The current settings guide places controls in the companion’s profile panel, with an All Settings sheet. Settings are stored per conversation; a separate default-setting action applies the configuration across chats. Record the current values before changing anything globally.

A configuration that works for a short check-in may be awkward in a detective story. Label your notes with the conversation name and date, not simply “my Xotic settings.” If you cannot find a documented control, note your account tier and the screen you are using. Do not assume every conversational surface has the same controls.

Choose one problem you can actually observe

These tests are suggestions, not measured product outcomes. In particular, changing presentation does not prove a memory problem has been fixed. If the character calls the station a library, a beautifully written paragraph about the library still fails the factual check.

Separate style, length and pacing

Xotic documents three style choices, from casual conversation to immersive scene writing, and separate length and pacing controls. Length, pacing and explicitness adjustments require a subscription; free accounts can adjust style. Dialogue only and Hide emojis are listed in All Settings. For this exercise, keep the scene non-explicit and use the Off setting where available.

Define your objective without using a vague word such as “better.” For example: “One short reply that acknowledges the broken clock and asks which platform to inspect.” That lets you distinguish a concise answer that works from one that simply omits everything important.

Do not combine every change into a single attempt. If you shorten the reply, change its style and replace the model together, you will not know which change helped. Keep the settings you did not intend to test in the baseline column of your notes.

Run a small fictional example

Original exercise: You and a fictional adult colleague are checking a closed railway station before a morning inspection. The entrance clock has stopped at 8:10. A blue envelope is on the ticket counter. Nobody has opened it.

1. Write those three facts in your opening message and ask the colleague to suggest one next step without taking it.
2. Read the response once. Note whether it preserved the clock time, left the envelope closed and let you choose.
3. Pick only one presentation issue to work on: length, narration or scene speed.
4. Change the relevant available control, then continue with a clear instruction such as “Describe the counter, but wait for me before opening the envelope.”
5. Compare against your stated objective. Keep, revise or revert the change.

This is a usability exercise, not a controlled benchmark: later turns contain more context than earlier turns. A successful response does not establish a model’s overall accuracy or long-term memory. If you repeat the exercise, record that the conversation state changed instead of presenting the results as identical trials.

Know when a model switch or message action is relevant

The settings documentation lists Ivy for free use and subscription models for individual chats; group chat uses a fixed model instead. It says a model switch affects the next reply. Do not buy an upgrade solely because a formatting adjustment has not yet been tried.

The message-actions guide limits regeneration to the latest text response, excluding the greeting and media messages. It describes regeneration as replacing that response by sending the preceding user message again. Preserve a brief note first if you need to compare the old response with its replacement.

Regeneration can produce another answer to the same instruction; it does not explain why the first answer failed. If the instruction was ambiguous, clarify it instead of repeatedly drawing new replies and selecting only the most flattering result. Deleting a response from the visible conversation also should not be described as proof that all service records were erased.

Keep a short change log

The example observation is illustrative, not a result we obtained in Xotic. For your own log, write what actually happened, including failed attempts. A short record is enough; you do not need to retain a sensitive transcript or attach payment details.

Use the scene-pacing guide when the issue is the structure of your turns, and the memory guide when facts drift. The parent AI roleplay buying guide helps compare tools by the controls you need. Settings availability and subscription terms can change, so check the current account screen before paying.