Chronicle Memory Explained: How Memory Differs by Tier in Vampiro Life
Hey folks,
One of the most common questions we get is simple: "What does better memory actually mean in Vampiro Life?"
This post explains exactly how Chronicle memory works today, based on the mechanics we run in production.
The short version
Vampiro Life keeps campaign continuity in three layers:
recentmemory: short-horizon summaries of the latest eventsoldermemory: compressed medium-term historyancientmemory: long-horizon campaign history
Every plan gets memory. Higher tiers get deeper retrieval of older and ancient layers during play, so your storyteller can reference more of your Chronicle's distant past.
How memories are created
The memory pipeline runs in cycles:
- New chat messages are summarized into a
recentmemory block. recentblocks are periodically rolled up intoolderblocks.- Paid tiers can also roll
olderintoancient, and then consolidateancientas it grows.
In practice right now:
- Around 10 new messages can trigger a fresh
recentsummary. - Rollups typically happen in batches of 8 memory blocks.
This means the system keeps compressing the past instead of letting token usage grow forever.
What each tier sees during gameplay
When the storyteller assembles context for your next turn, it currently caps memory depth by plan:
- Free: up to 6
recent, 3older, 0ancient - Pro: up to 6
recent, 5older, 3ancient - Top: up to 6
recent, 8older, 10ancient
So tier differences are not cosmetic. They directly change how far back your campaign context can reach in each response.
"Stored" versus "used this turn"
There are two separate ideas that are easy to mix up:
- Archival memory management: how many memory blocks are retained before consolidation
- Turn-time retrieval depth: how many memory blocks are injected into the storyteller context for your live turn
Those two controls work together to keep performance stable while preserving continuity.
Why this matters for roleplay quality
Deeper memory improves:
- callback consistency (old debts, old promises, old grudges)
- relationship continuity (NPC trust and hostility remain coherent)
- long-arc pacing (plots can return after many sessions without feeling random)
If you want the mechanics behind the game loop itself, start with Features. If you are comparing tiers for campaign depth, see Pricing. If you want quick clarifications, check the FAQ.
What we are improving next
We are continuing to make memory behavior easier to inspect from the player side, so the difference between "what is remembered" and "what was used in this exact turn" is more transparent.
That is the direction: cleaner observability without sacrificing immersion.
Thanks for reading.
- Rodrigo