SpicyChat Rulebooks: Track Changes and Guide Character Behavior

Choose one consequence to track first

Begin with the value most important to the premise. An overnight repair crew might need a spare-parts meter before it needs separate systems for money, fatigue and every relationship. A smaller setup makes it easier to see whether the rules do what you intended.

Decide what the meter's states mean in the story. Enough spare parts might let the crew continue; a shortage might force them to seek help. Make those consequences recognizable in the dialogue rather than treating the number as a decoration.

Give updates and influence different jobs

The meter holds a value. An update rule tells it how an event changes that value, and an influence rule tells the character how to respond to the resulting state. Keeping those responsibilities distinct makes the behavior easier to test.

Try an ordinary event before relying on the system in a long story. If a repair consumes a part, check that the count moves in the right direction and only once. Then test a low-supply state directly to see whether it affects the response as intended.

Attach and review the rules for each story

Use the supported attachment controls to connect a Rulebook to a character, persona or conversation. Inspect a cloned or imported book first. Rules written for another premise may be internally consistent but still give the wrong results in yours.

A Rulebook supports up to 15 meters, with 8 visible in the chat strip and one Story clock. Values are maintained separately for each conversation. You can use Rulebooks in mobile chats; editing takes place on the website.

Leave reusable background facts to a Lorebook and changing story state to a Rulebook. Neither replaces the character definition or ensures that a generated response will interpret every instruction precisely.