Tips

Handling Internal Game Information

In addition to information presented to the user, the AI maintains a scene summary and internal story information (Notes).

• For example, characters might have char:Taro, flags might have flag:in_room — Notes are kept per item.
• To save tokens, old body text is no longer referenced, but the body summary and Notes are sent to the AI with each scene generation from the beginning to the latest.
• Summary and Notes management is left to the AI, so an AI that slacks on management may forget parts of the story from a little while ago.
  • For example, body text indicating a mission was completed disappears from the reference range, and dragged along by a theme statement saying "the mission must be carried out," the mission ends up being repeated.

Debug Commands

Including the following instructions in the theme statement helps with situation management.

## Debug Commands

- When the player gives instructions with the words "debug" or "debug mode," change settings accordingly.
- Perform data disclosure, story situation transitions, setting changes, etc. It's fine if setting contradictions occur as a result of changes.

Rejection & Fumbles

The AI tries to fulfill user requests as much as possible. To prevent settings from being destroyed by player free-form input, it's good to set up the theme statement in advance to prioritize settings and have instructions that don't align with them result in rejection or fumbles. However, in that case, you need to carefully define the scope so as not to inhibit the player's free imagination.