Skip to main content
Test the character as one complete experience—not only as a collection of finished fields. A strong brief can still contain conflicting rules, a greeting with nowhere to go, or a progression trigger that fires too easily.

Review the complete character

Check these pieces together:
  1. Name and tags.
  2. Public Description.
  3. Greeting.
  4. Scenario.
  5. Additional Personality Details.
  6. Extra Details and any State Trackers.
  7. Permanent appearance fields.
  8. Display Media.
They should all describe the same premise. If the Public Description promises a mystery but the Scenario has no discoverable information, the experience will not match its hook.

Use three stress-test personas

The rusher

This user tries to skip the emotional or story progression. Test whether:
  • Hard locks and phase gates hold.
  • The character responds in character rather than simply agreeing.
  • A premature milestone has the consequence you designed.

The rule-breaker

This user presses locked topics, contradicts the world, or tries to force a hidden revelation. Test whether:
  • The character protects locked information.
  • World rules remain consistent.
  • Deflection or refusal sounds like the character rather than a system message.

The passive user

This user replies with a few words and rarely introduces new material. Test whether:
  • The character can advance the immediate scene without controlling the user.
  • The Scenario contains enough goals, routines, NPCs, or environmental events.
  • Replies offer a question, choice, discovery, or action to engage with.
Finding a loophole is useful. Strengthen the relevant rule, remove conflicting instructions, and run the same test again.

Test three different openings

Try at least:
  • A cooperative and curious reply.
  • A skeptical or confrontational reply.
  • A brief and noncommittal reply.
Then verify:
  • The character’s voice is recognizable in every route.
  • The character does not narrate the user’s private thoughts or choices.
  • The first phase remains active until its actual trigger.
  • State Trackers update for meaningful reasons.
  • The chat has somewhere to go beyond the opening scene.

Test visual stability

Generate several unrelated scenes:
  • A close portrait.
  • A full or three-quarter body pose.
  • A different outfit.
  • A different background and lighting setup.
If a core feature disappears or a permanent outfit keeps intruding, return to the appearance prompt and tune one trait at a time. See Image consistency and editing.

Ask someone else to try it

Keep the character Private during development or switch it to Unlisted for direct-link testing. Ask the tester to begin without explaining every hidden rule. Their first session should answer:
  • Did the Public Description make their role clear?
  • Did the Greeting provide an obvious response?
  • Did the character feel distinct after several messages?
  • Could they understand important mechanics without seeing the private fields?
  • Did any promise in the profile fail to appear in the chat?

Testing checkpoint

The character is ready to share when:
  • Its voice and boundaries survive all three stress tests.
  • Progression changes only for the intended reasons.
  • The cover, gallery, and written premise agree.
  • A new user can begin without extra instructions from the creator.
  • The character follows the current content rules.

Publish to the community

Review the separate public requirements and moderation checklist before submitting.
Last modified on July 27, 2026