Writing Down an Event Does Not Mean It Has Happened

A Game Master prepares a temple.

There is a gatekeeper outside.

The gatekeeper carries a key.

Behind the door is an item that could change what happens later.

The GM expects the players to speak with the gatekeeper, notice that something is wrong from his reaction, find a way to get the key, and finally enter the temple.

That is a reasonable plot.

But it is not an event that has already happened.

The players might only watch the temple from a distance.

They might speak with the gatekeeper and then leave.

They might try to steal the key and fail the check.

They might break through the entrance instead.

They might never come here at all.

The temple can exist before the session.

The gatekeeper can exist.

The key and the item behind the door can exist.

But entering the temple, taking the key, meeting the gatekeeper, or fighting him cannot become part of the world’s history simply because the GM prepared those possibilities.

The GM writes down what might happen.

Only the outcomes confirmed at the table become things that actually happened.

Preparing Outcomes Quietly Makes Choices for the Players

To make a scenario easier to run, a GM will often write events as a sequence of outcomes.

The players arrive at the village.

The players visit the mayor.

The mayor gives them a quest.

The players accept the quest.

The players enter the forest.

The players find the missing person.

This is clear and useful when planning the expected flow of a scenario.

The problem is that it can turn choices the players have not made into things that are assumed to happen.

The players might not trust the mayor.

They might refuse the quest.

They might investigate what the mayor is hiding first.

They might accept the quest but deal with it in a way the GM never expected.

If accepting the quest has already been treated as a fact in the scenario, the preparation can feel broken as soon as the players refuse.

The GM may then start pushing them back toward the planned outcome.

Another NPC gives them the same information.

A new crisis forces them into the forest.

Every other path stops working until they accept the quest.

The players still appear to have choices.

But the world only accepts the answer the GM prepared.

When the GM prepares outcomes, player agency becomes a question of how many detours the players may take before reaching the same result.

What a GM Really Needs to Prepare Is How the World Responds

Not deciding the story for the players does not mean the GM cannot prepare anything.

There is still plenty to prepare.

What is the mayor hiding?

Why does the gatekeeper have the key?

What is the current state of the temple?

What is happening in the forest?

What danger will the missing person face if the players wait too long?

How might different factions respond when they learn what happened?

This preparation does not take choices away from the players.

It describes the conditions that already exist in the world and how the world might respond to the players.

If the players accept the quest, the mayor may offer information or resources.

If they refuse, the situation involving the missing person can continue to get worse.

If they expose the mayor’s secret, other NPCs may change how they treat him.

If they enter the forest on their own, they may encounter the same danger without having all the information.

The GM does not need to decide in advance which path must happen.

The GM only needs to understand which conditions each choice might change.

Preparing an event is not about arranging the players’ next step.

It is about making sure the world can still respond after they take that step.

A Declared Action Does Not Mean the World Has Changed

In a TTRPG, something a player says they want to do does not always become a fact immediately.

“I steal his key.”

That is an intention.

Whether the key actually changes hands still depends on the method, the resistance, the roll, and the ruling.

“I go to the temple.”

That is a decision.

Whether the character has already arrived can still depend on distance, time, blocked roads, encounters, and other conditions.

“I convince him to join us.”

That is an attempt.

The other character does not join simply because the player declared it.

A table is full of unfinished statements.

Players discuss plans, change their minds, revise their actions, and react to new information from the GM.

If the world records outcomes too early, a character may appear at a destination before arriving.

An item may change owners before the theft succeeds.

A relationship may be created before the other person has agreed to anything.

World state should not track every intention spoken at the table.

It should track the changes that were actually confirmed.

The player declares an action.

The rules and the GM determine the outcome.

From the moment that outcome becomes real, the world begins carrying its consequences.

The Same Characters, Locations, and Items Can Produce Very Different Events

A character and a temple appearing in the same passage does not mean the character has entered the temple.

The character may be watching it from a distance.

They may remember going there in the past.

They may be lying about it.

They may only be pointing to it on a map.

A character appearing near a key does not mean they have taken the key.

They may see it.

Ask about it.

Try to steal it.

Give their own key to someone else.

Or discover that a key they should have is missing.

Two characters appearing in the same passage does not mean they have met.

One may only be talking about the other.

They may be reading a letter the other person left behind.

They may be remembering a meeting that happened long ago.

The same world entities can form many different events.

Only the GM knows the immediate context, the player’s intention, and the final ruling well enough to decide which change the world should accept.

Names appearing near each other can suggest that an interaction may be happening.

It cannot prove that the interaction has happened.

Events the Players Do Not Choose Can Still Remain Possible

If the players do not enter the temple, the temple does not disappear from the world.

If they do not take the key, the key does not stop mattering.

If they refuse the mayor’s quest, the missing person does not stop being missing.

Prepared content can remain part of the world.

It simply should not pretend that the players have already experienced it.

The gatekeeper may continue carrying the key.

He may later give it to someone else.

The temple may remain unchanged.

It may also be sealed by another faction after the players leave.

The missing person may be rescued.

They may be moved somewhere else.

They may lose the chance to be rescued because the players decided to deal with another problem.

When the players do not choose an event, that event does not have to be deleted.

It can remain possible while its conditions change.

It can also reach a different outcome without the players being there.

The important thing is that the GM can tell the difference between:

Things that were only prepared.

Things that may still happen.

Things that have lost the conditions they needed.

And things that truly became part of the history created at the table.

InkWeave Brings Possible Interactions to the Surface Without Deciding Them

InkWeave does not move a character simply because the character’s name appears near the name of a location.

It first checks where the character is at that point in the story and what state the target location is currently in.

If the character is already there, InkWeave can show the people, items, and other information connected to that location.

If the character is somewhere else, InkWeave can ask the GM whether a movement event should be recorded.

When a character appears near an item, InkWeave does not automatically decide that the item has changed hands.

It can first show where the item currently is, who has it, and whether the character already owns it.

The GM can then confirm whether this is an acquisition, placement, transfer, use, or only a mention.

When two characters appear near each other, the world can check whether they are in the same location and whether a relationship already exists between them.

When a character appears near an attribute, InkWeave can ask whether a value or state is changing.

These are questions.

They are not verdicts.

InkWeave does not need to pretend that it understands everything the players and GM intend.

It only needs to bring possible world-changing interactions to the surface and leave confirmation to the person who knows what actually happened at the table.

The GM confirms the event.

Only then does the world remember it.

The GM Prepares Responses. The Players Turn Them Into History.

A TTRPG scenario needs preparation.

Without preparation, it is difficult for the world to respond meaningfully when the players make a choice.

But preparation is not the same as completing the story in advance.

The GM can prepare a temple.

The gatekeeper’s motives.

The location of the key.

The danger behind the door.

The costs different choices may carry.

But whether the players go there, how they enter, whom they trust, what they take, and what the world becomes afterward must be decided when the game is actually played.

Good preparation does not ask the players to perform events the GM has already written.

It gives the world enough clear conditions to honestly carry the choices the players make.

The GM does not prepare a plot the players must follow.

The GM prepares how the world might respond.

The players decide which responses finally become history.