Prepare a compact character definition, choose who can access it, save a recoverable copy, then check it with neutral prompts. On SpicyChat, the signed-out creation route stopped at an account gate in my latest check. Write the voice, fictional setting and boundaries in a local note before investing time in an editor you may not yet be able to use.
The current guest route stops before the editor
On October 23, 2026, I reopened SpicyChat’s character-creation route in desktop Chrome while signed out; the page identified its web version as 4.7.3. It showed public/private character descriptions and a “Create Free Account” button, with no editable character form. This repeats the access limitation in my September 24 guest check.
The verified finding is the account prerequisite. I did not create an account, save a character, upload an avatar or test generated personality consistency. The workflow below combines current official instructions with a clearly labeled test you can perform once you have legitimate editor access.
A compact character card beats a long backstory
I would draft four fields:
- Role: who the fictional adult character is and why they are talking to you.
- Voice: two or three traits shown through sample dialogue, not adjectives alone.
- Setting: where the conversation starts and what the character already knows.
- Boundaries: topics, behavior and consent rules that should remain stable.
SpicyChat’s creation guide recommends roughly 900–1,100 tokens across character setup to leave room for conversation. Its separate personality guide documents a 5,000-character field limit. Characters and tokens are different units: fitting inside the field does not establish how much conversation context remains. These are the provider’s current instructions, not measured limits from my guest session.
Chub’s prompting guide explains that character definitions, inserted lore and recent history share the input context. A compact starting card gives you fewer contradictions to diagnose; it does not guarantee identical behavior across models.
A small test card is easier to debug
For a first pass, I would write something like: “Mara is an adult night-shift museum curator in a fictional coastal town. She answers in short, dry sentences, asks one question at a time, and remembers that the gallery closes at midnight.” Then I would add two sample replies in that voice and open a private chat. The goal is not literary polish; it is to give the model a few stable constraints I can actually test.
The following is a proposed consistency check, not a completed model test. Keep the same character, model and settings while asking:
| Check | Neutral prompt | What to record |
|---|---|---|
| Recall | “When does your gallery close?” | Whether the reply preserves midnight without the question supplying it |
| Contradiction | “How was your shift at the harbor?” | Whether the reply corrects the job or adopts a different one |
| Voice | “Describe the room we are in.” | Whether the reply follows the short, dry style and established setting |
Record the actual replies and session length. A short successful exchange demonstrates behavior in that conversation; it does not establish long-term memory or isolate which input caused the answer. If a detail drifts, clarify one ambiguous field and repeat the same prompts before changing the model too.
Keep a portable master copy
Write the character card in a local note before pasting it into any platform. Keep the opening message and two sample replies with it. If the platform loses a draft or changes its editor, you can recreate the character without rewriting the premise from memory. Version the card when you change a boundary or backstory fact; otherwise a later good response may be impossible to reproduce.
When a character drifts, change one field at a time. First fix a contradiction in the role or setting, then retest with the same neutral prompt. Rewriting the entire card and switching models simultaneously makes it hard to tell which change helped.
Check avatar and lorebook prerequisites
The avatar step can stop publication
SpicyChat’s avatar instructions require an uploaded or generated avatar to finish creation. The guide currently specifies a square upload of at most 10 MB, with JPG and PNG among the supported formats. Prepare a fictional image before filling a long form, then check the actual editor’s requirements. I did not test an upload or generated avatar.
For longer stories, consider keeping optional world facts in a lorebook. Chub’s guide explains scan depth and token budgets for keyword-triggered entries. A keyword outside the scanned messages, or an exhausted budget, can explain a missing fact. Check the entry’s activation settings before calling it a model-memory failure.
A private lorebook and a private character are separate settings. SpicyChat’s current support page, checked October 23, says its lorebooks are private but can attach to your own public or private bots. Public lorebook sharing is a different feature; the page still describes it as coming later. I have not independently tested attachment in a logged-in account. Keep personal secrets out of lore, particularly when a public character may use those facts in replies.
Visibility is a separate decision
Before saving, check both character visibility and definition visibility. SpicyChat’s guide says public characters appear in listings; unlisted ones remain accessible to people with their link; private ones restrict public access. Definition visibility separately controls whether other users can inspect the personality, examples and scenario. The same guide says moderators can still see hidden characters. Neither setting establishes that the provider cannot process the content.
Save a work-in-progress character as Private, not Draft
SpicyChat’s draft-recovery help says character drafts live only in the current browser or app. Clearing site data, switching devices or using private browsing can erase unfinished work; lost drafts cannot be recovered. Save the unfinished character as Private if you want it attached to your account and available across devices. Private controls public access; it is not a promise that the service stores no copy.
Next step
Write a 100-word fictional character card, add two sample replies and run the contradiction test. Only add more lore after you can identify a specific missing fact. For tools that support roleplay, start at the AI chat category.