World Sandbox

1️⃣ Enter world_info in User Note and save. Simply input your story's world, genre, objectives, etc.
2️⃣ Set your own "Persona".
3️⃣ After saving world_info, say anything to begin your story (even just . works!)

✨️ You can write your own opening scenario too.
✨️ You can also start with requests like OOC: At the adventurer's guild reception or [Start from a pinch situation] to ask the AI for specific scenarios.
✨️ The representative image has been simplified for easy snapshot functionality. Enjoy generating story images as well!

• Recommended Models: Gemini 2.5 Pro, Claude Sonnet 4, Donald 2, DeepSeek V3
• Not Recommended: Huey, Kimi K2, Claude Sonnet 3.7

⚠️ If the status display (time, location, etc.) disappears, try switching models and regenerating, or change models to ensure it appears next time. The AI uses this information as reference for story creation.
⚠️ If display issues occur, there are workarounds available in the notes section (rare occurrence).

✨️ Use "suggest world_info" or "suggest settings" to get world_info setting examples
✨️ You can also request "suggest fantasy settings" and similar variations.
‼️ Always copy the content including world_info: and save it to User Note. Feel free to edit the settings as you like.

ℹ️ The suggestion feature works best with Gemini, Claude, DeepSeek.
ℹ️ Suggestions may consider your Persona settings.

⚠️ Please use words like "settings" and "suggest". Some languages may not respond properly, so include the term world_info if needed.
⚠️ If the AI starts the story on its own, delete the previous exchange
⚠️ Since AI loves dramatic scenes where users are sent to worlds, if it feels intrusive, delete the suggestion exchange before starting.

(Examples)

• world_info: near-future Tokyo, cyberpunk, dark tension, {{user}} is a hacker, caught up in corporate conspiracy
• world_info: modern café, romantic comedy, bright and warm daily life, {{user}} is a university student, thrilling daily life with barista
• world_info: near-future space station, space opera, {{user}} is rebel pilot, fighting against empire

✨️ world_info is your story's 'DNA' - everything written here becomes the foundation for all developments
✨️ Writing broad objectives, direction, and plot outline helps guide the AI's story generation.
✨️ Including atmosphere and tone along with genre creates a more consistent story experience
✨️ Setting start dates and time periods can help with the AI's time management

💡 Feel free to use User Note however you like.
💡 Using User Note lets you communicate things you want the AI to remember.

The information below is for those who want to know more detailed usage methods.

These can be used as small requests or instructions to the AI.
Use them when you want to liven up the story, change the atmosphere, give actions to NPCs, or switch scenes.
OOC and [ ] work the same way. Think of yourself as a film director or producer, suggesting to the AI "I want this kind of direction" - this makes it easy to understand.
One request at a time tends to be most effective.

(Examples)

[Make it the next morning]
OOC: John suddenly betrays, [Tell me the name and appearance of the person who appeared]
OOC: Change Takumi's first person to "Boku", [Give me a hint]
OOC: Trigger an event, [Reveal the truth]
*Read diary* [Explain all diary contents] 

✨️ You can guide the story.
💡 If the story feels stagnant, asking for hints or requesting "trigger an event" is effective. You can also ask for the story's finale.
💡 If the AI's story becomes too abstract and you can't find answers or clues, asking for "answers," "explanations," or "truth" through OOC is good. This makes the AI think in reverse. (The AI might not have thought it through yet either!)
💡 Techniques like *reading diary* [explain diary contents] are useful for making the AI generate content. Without requests, content often isn't explained. This prevents situations where content is omitted and becomes incomprehensible.
💡 This can also be used to modify character speech patterns and first-person pronouns. Since AI tends to imitate existing speech patterns, it's most effective to give instructions when new characters first appear.

1. Write in detail

• world_info: modern Japan, ghost train "Yomi-gō". Passengers are souls of the dead. {{user}} is a living person who wandered in. Soul judgment awaits at the terminal, but solving the train's mysteries might change fate.

• world_info: Aerial floating islands "Aerith", traveling by airship through islands floating on a sea of clouds. {{user}} is an apprentice navigator. Each island has different cultures and magic. Amid signs of a storm swallowing the island, seeking the legendary "Sky Compass".

💡 Recording important settings, unique rules, and objectives in detail prevents them from being forgotten or changed

2. Use parentheses for grouping

• world_info: magic school, fantasy, elf girl:(childhood friend, name:Alice, 19 years old, honor student)

💡 You can group sub-items with parentheses.

3. You can add settings to world_info during conversation as long as it doesn't confuse the AI.

💡 If settings get too long, consider making it a custom character.

4. Markdown-style formatting works well too.

# world_info
magic school, fantasy, user is a dropout
## objective
discover forbidden grimoire "Silent Grimoire" and aim for reversal
## Silent Grimoire
- grants dark magic to manipulate others' hearts
- curses user with nightmares each time it's used

# session memo (below is free form, section names recommended for AI comprehension)
## NPCs
- Alice: honor student
## promises
- promised to meet Alice on Sunday
...

✨️ Easy to write, so recommended!
✨️ Separating # world_info and # session memo sections helps AI understand whether it's story setting or event records
💡 Important recurring characters can be written in world_info too!
💡 Doesn't need to be strict markdown
💡 Any format works as long as AI can identify world_info sections (YAML, etc.)

✨️ If repetition starts occurring, try switching models or changing scenes.
ℹ️ Hidden logging functionality is built in to support AI story generation (visible when editing responses)
⚠️ The above hidden items may sometimes be displayed. In that case, use the edit function to delete (*) or (") from HTML comments. This is caused by caveduck's standard notation disabling invisibility.