How Chronicle Memory Works in Vampiro Life

Chronicle continuity is one of the core design goals in Vampiro Life. This page explains how memory is handled in production today: what is stored, what is summarized, and what gets injected into each new turn.

The Three Memory Layers

Campaign history is managed in three layers. Each layer has a different job and compression level:

• recent: short-horizon summaries of the latest arc and immediate consequences.
• older: medium-horizon digests that compress several recent summaries.
• ancient: long-horizon summaries for deep Chronicle continuity over many sessions.

How Summarization Happens

New messages are periodically summarized into recent memory. As memory volume grows, the system rolls up batches into deeper layers so context quality stays high without unbounded token growth.

In practical terms, this means your Chronicle keeps evolving history, but in increasingly compact forms. The goal is not to remember every sentence verbatim forever, but to preserve the narrative signal that matters for future decisions.

What Changes by Plan

Every plan uses the same memory architecture, but the live retrieval depth changes by tier. During each turn, the storyteller always receives recent memory and then a capped amount of older/ancient memory depending on your plan.

• Free: shallower deep-history retrieval.
• Pro: deeper retrieval with access to ancient context.
• Top: deepest retrieval window for long-running chronicles.

This is why paid tiers can keep stronger continuity on very long arcs: they see more deep historical context during generation, not just more tokens in a generic sense.

Why This Matters in Play

Better memory continuity improves:

• NPC consistency and relationship follow-through
• Long-payoff plot threads and callbacks
• Stable character voice across many nights
• Reduced narrative drift in complex campaigns

Best Practices for Long Chronicles

• Make intent explicit when stakes shift (alliances, debts, oaths, betrayals).
• Name recurring NPCs and places consistently so memory summaries keep strong anchors.
• Use decisive actions instead of vague meta-instructions when you want concrete continuity.

For a broader product overview, visit Features. To compare plans directly, see Pricing. For quick mechanics clarifications, use the FAQ. For implementation updates, read the Blog.