Even detailed session notes may not tell you what is true now

You may remember exactly what happened during the last session.

The players infiltrated the castle.

One of them stole a key.

Another convinced a guard to change sides.

The party found a letter in the basement but did not open it.

Finally, they escaped through the waterways with a prisoner.

That is a clear session record.

It preserves the course of events and gives the players enough information to remember the story before the next session begins.

But when the next session actually starts, the GM may need answers to a different set of questions:

Who has the key now?

Who is carrying the letter?

Is the guard who changed sides still inside the castle?

Which party member is the prisoner travelling with?

Has the castle discovered the escape?

Which factions know about the prison break?

Which entrances can no longer be used in the same way?

The answers may all be buried somewhere in the notes.

But an answer being somewhere in the notes is not the same as the GM being able to see it now.

Session notes preserve how the story happened.

World state preserves what remains after it happened.

Sessions organize play, not in-world time

We usually organize TTRPG campaigns by session.

The first session.

The second session.

The tenth session.

One session lasts four hours. Another covers only a single conversation. One begins with combat and ends while the players are still deciding what to do next.

Sessions are useful for organizing progress in the real world.

They do not necessarily match the passage of time inside the game.

A single session might begin in the morning and end several months later.

Another might spend four hours inside the same locked room.

When the party splits up, one group may complete half a day of investigation while another group’s scene is still only a few minutes ahead of where it began.

The GM might also use the next session to play out something that was skipped previously, or return to an earlier point in time to resolve another character’s actions.

That means saying an event happened during session eight is not enough.

The world needs to know:

What happened before it?

What happened after it?

When it occurred, where had the other characters, locations, items, and conditions reached in their own histories?

A session number tells us when people sat down at the table.

Causal order tells us where the world had reached.

Not everything said at the table becomes true in the world

Session notes have another unusual problem.

Something said by a player is not necessarily something that happened.

“We will go to the harbor tomorrow.”

That may only be a plan.

“I give him the ring.”

Another player may interrupt before the exchange is completed.

“If the guards follow us, I will start a fire.”

That is a contingency, not an event that has already happened.

“I push the door open.”

The action may fail because of a roll, a lock, or a new condition revealed by the GM.

Language at the table is fluid.

Players speculate, plan, reconsider, and revise their actions. A ruling or dice result may also produce an outcome different from the one they intended.

If everything said at the table is treated as fact, the state of the world quickly becomes confused.

Session notes need to preserve how the players reached an outcome.

World state should acknowledge only the outcome that was confirmed.

Wanting to move does not mean the character arrived.

Wanting to trade does not mean the item changed hands.

Wanting an alliance does not mean the relationship between two factions has changed.

Wanting to open a door does not mean the players have seen the world behind it.

The distinction is small.

But it determines whether a campaign log is preserving conversation or establishing history.

Recaps help people remember. State helps the world continue.

GMs often turn complicated sessions into summaries.

That makes sense.

No one wants to listen to a four-hour recording or search through an entire chat history before every session.

A recap might say:

“The party made an enemy of the Northern Guild.”

“The investigators found an important document in the manor.”

“The players rescued the prisoner from the cells.”

“The captain of the guard died in the conflict.”

These sentences are useful for human readers.

But the world may need more specific information before it can continue.

After the party angered the Northern Guild, which characters were affected?

Who has the document now?

Is the manor where it was found still being guarded?

Where did the prisoner go after the rescue?

After the captain died, what happened to the key he carried, the information he knew, and the position he held?

A recap preserves the meaning of an event.

State preserves the conditions that event changed.

Neither can replace the other.

Without a recap, the campaign loses the context that helps people remember and care about what happened.

Without state, the GM has to reconstruct the world from the recap every time.

That may be manageable after a few sessions.

After a campaign has run for dozens of sessions, the reconstruction becomes another game that none of the players are there to play.

Long campaigns scatter the truth across different places

The truth of a long-running TTRPG world rarely exists in a single document.

An NPC’s original description is stored in the character notes.

What the NPC did later appears in a session log.

Changes in the NPC’s relationship with the players may exist only in notes the GM wrote during play.

An item the NPC gave away may be recorded on a player’s character sheet.

The details of the NPC’s death may survive only in chat history or a recording.

Every source may be correct.

They simply describe the truth from different times and different perspectives.

The GM’s real job is to put those truths back together into a single present.

The setting notes say the NPC belongs to a faction.

The session log says he betrayed it.

A player’s notes say he gave the party his insignia.

The GM remembers that he later died.

At the beginning of the next session, does he still count as a member of that faction?

What does the insignia represent now?

Does the faction know about his betrayal?

How should its other members treat the players?

None of the information has been lost.

The current state of the world has simply been scattered across several places.

What exhausts a GM during a long campaign is often not a lack of records.

It is having plenty of records without a present that can be checked directly.

Current state alone is not enough

If session notes are difficult to reconstruct, could the GM simply save the latest state?

That is not enough either.

Imagine a document that says:

The players currently have the key.

The captain of the guard is dead.

The prisoner has escaped the castle.

The Northern Guild is now hostile.

The GM can quickly see what is true now.

But another important question has disappeared:

Why?

Was the key stolen, or did the guard hand it over willingly?

Was the captain killed by the players, or by another faction?

Did the players rescue the prisoner, or did the prisoner use the confusion to escape alone?

Why is the Northern Guild hostile, and can that relationship be repaired?

State without history leaves only the result.

The stories that follow in a TTRPG often grow from how that result came to exist.

The players may possess the same key through theft, inheritance, trade, or force. Each path creates different consequences.

An NPC may be equally dead after being murdered by the players, sacrificing himself for them, or dying because they failed to intervene. Each history leaves behind a different relationship.

A long campaign should not replace session notes with a list of current states.

History and state need to answer each other.

When the GM sees the present, they should still be able to return to the event that created it.

When the GM revisits an event, they should be able to see what it changed in the world.

Reliable world state should be derived from events

If world state is just another table the GM has to maintain by hand, it quickly becomes another burden.

After every session, the GM has to update the NPC list.

Update the item list.

Update the location list.

Update the faction list.

Update the clue list.

Update the player states.

Then make sure every document still agrees with the others.

This only replaces rereading session notes with maintaining several separate versions of the present.

A more reliable approach is to treat confirmed events as the source.

A character’s location changes when their movement is completed.

An item’s ownership changes when the transfer is confirmed.

An NPC’s living state changes when the death is confirmed.

A location’s access conditions change when it is sealed.

A faction’s structure changes when a character actually joins or leaves it.

As these events accumulate over time, the current world state is derived from their combined results.

If an earlier event is removed or changed, the states that follow should be calculated again.

The GM no longer has to maintain two potentially conflicting truths: what happened and what is true now.

Events preserve the history.

Replay the events, and they produce the present.

InkWeave keeps confirmed changes in the story timeline

InkWeave does not automatically turn everything a player says into an event.

It does not need to interpret an entire session on the GM’s behalf.

What needs to be preserved are the changes the GM has confirmed as having happened.

A character actually moved to a new location.

An item actually changed hands.

A location was actually sealed or destroyed.

A character actually died, disappeared, or changed state.

A faction actually gained, lost, or reorganized its members.

Foreshadowing, flags, and conditions were actually established, checked, or resolved.

Once these confirmed events enter InkWeave’s story timeline, they are no longer only sentences in a session summary.

They become the source of the world states that follow.

The GM can still preserve a complete narrative record.

The players’ laughter, surprises, arguments, and all the details that only the people at that table would understand can remain intact.

But when the next session requires an answer about where a character is, who has an item, whether a location can still be entered, or whether a faction’s structure has changed, the GM does not have to rely entirely on memory and cross-referencing.

InkWeave does not measure how exciting the session was.

It tracks what remained in the world after the excitement ended.

The next session needs more than a recap

A recap tells the players:

What they did last time.

Whom they met.

What they discovered.

How badly they complicated the situation.

The GM needs to go one level deeper.

What does the world allow now?

What does it refuse?

What has it lost?

What new possibilities exist because of the players’ choices?

Not all of these answers should be revealed to the players.

Some are hidden information.

Some are consequences that have not surfaced yet.

Some may take a long time before the players discover what they changed.

But the GM needs to know that those consequences still exist.

Session notes preserve the story a group experienced together.

World state preserves the conditions that story leaves behind for the next session.

What a long campaign needs to remember is not only what happened last time.

It needs to remember what the world has become when it wakes up again.