A story can contain several names while still being a one-character conversation. The identity the user adopts is one role; the AI character is another. A third named person in the background is not automatically a separately controlled speaker.
Dreamle links Create Character, Create a Group and Fantasy World. SpicyChat’s persona documentation addresses a narrower question: who the user is in the exchange.
Put each piece in its own record
Suppose you play an adult expedition photographer, meeting a fictional adult engineer before a crossing.
| Piece | Example | Purpose |
|---|---|---|
| User persona | Photographer, 35, careful about unverified claims | Defines how the AI addresses your role |
| AI character | Engineer, 38, practical and concise | Defines the other speaker |
| Shared scene | A bridge inspection before dusk | Defines what is happening now |
| Supporting person | An archivist waiting for a message | Background until actively introduced |
A persona containing “I am a photographer, an archivist and an engineer” does not create three independent AI participants. It gives the model a confusing user identity.
SpicyChat documents My Personas → Create New, with name, avatar and concise highlights. Its current support page describes the persona as context the AI reads about the user. Keep it focused on the role needed for this exchange.
A different role may need a different conversation
SpicyChat’s chat guide documents changing a persona in the conversation menu. It also warns that this does not rewrite prior names in messages or memories.
If you want to replay the bridge scene as the archivist, use the documented Start New Conversation route, then choose that persona. The old conversation remains available; Change Persona inside it does not rename its already accepted history. A separate conversation avoids pretending that the photographer’s established history never happened. If the role change is an intentional plot event, state it clearly instead of expecting a settings change to rewrite the story.
Dreamle’s group route names a different kind of structure, but its guest view does not verify cast limits or speaker-selection behavior. Do not use a group label as proof that it can manage every proposed role.
For a practical check, ask the next reply to address your chosen role and its task: the photographer records the inspection, while the archivist interprets the ledger. If the reply still attributes the old profession or memories to you, review whether you changed persona inside an existing history instead of starting the intended fresh version. This is a diagnostic example, not a claim that a new conversation isolates every account-level memory.
For a one-to-one scene, a focused persona and a clear AI character may be sufficient. For an ensemble, write each participant’s goal and knowledge boundary first. That plan remains useful even before the actual group mechanics are known.
No persona or group was created for this comparison. SpicyChat supplies the documented user-role controls here; Dreamle supplies publicly separate routes for character and group tasks, with internal mechanics still unverified.