The players ask whether they can kill the NPC. The world asks what happens next.
The GM prepares an NPC.
He knows what is happening in the city.
He carries a key to a restricted area.
He has ties to two factions.
The next morning, he is supposed to introduce the players to another important character.
The players meet him for the first time.
They decide he sounds suspicious.
After failing to follow him, they choose to attack.
They roll.
The attack hits.
The NPC dies.
The players usually need to ask only one question:
Did we succeed?
The GM has several more questions to answer within seconds.
What happens to the key he was carrying?
Is there another source for the information he never revealed?
Does tomorrow’s meeting still happen?
Will the factions connected to him react?
Who finds the body?
Who knows the players did it?
Is the thing he was trying to prevent now more likely to happen?
The players may have killed only one NPC.
The world may have lost an entire set of conditions that were still waiting to be resolved.
That is what makes NPC death difficult in a TTRPG.
Death happens quickly.
Its consequences do not organize themselves.
An NPC is more than a plot function
It is easy for a GM to think about NPCs in terms of function.
The person who gives the quest.
The person who provides the clue.
The merchant who sells an important item.
The guard who controls an entrance.
The faction representative who negotiates with the players.
The character who will betray them at a particular moment.
These functions are useful when designing a scenario. They help the GM understand what each character contributes to the story.
But when an NPC is reduced to a function, replacing them after death becomes too easy.
The clue giver dies, so someone else provides the same clue.
The key holder dies, so another key appears in the room.
The guide dies, so the players meet someone else who happens to know the route.
Any of these solutions can work.
But if the world immediately restores the same function every time, the players will begin to notice something:
Their choices did not really change the world.
Only the NPC’s name died.
The plot function remained in place, waiting for them.
An NPC who lives in the world should be more than an interface for delivering the next piece of content.
They have a location.
They carry items.
They have relationships.
They know some things and do not know others.
They occupy a place that someone else may not be able to fill immediately.
After an NPC dies, the world has to ask more than whether their function should be preserved.
It has to ask what happens to everything that was connected to them.
Death closes off part of the future
Once an NPC dies, some events can no longer happen in the way they were prepared.
The NPC cannot give testimony in person.
They cannot attend tomorrow’s negotiation.
They cannot introduce the players to another character.
They cannot complete a promised exchange.
They cannot continue leading a faction.
They cannot betray anyone in a scene that has not happened yet.
Prepared material is not already true simply because the GM wrote it.
Until it happens at the table, it is only a possible future.
When an NPC dies, every future that depended on them being alive loses one of its conditions.
That does not mean every related plot must be deleted.
It does mean those events cannot continue unchanged.
Tomorrow’s negotiation may be cancelled.
An unprepared subordinate may be forced to take over.
A truth the NPC was supposed to reveal may have to be reconstructed from their belongings.
The planned betrayal may never happen, while the death itself creates a different conflict.
Death closes certain futures.
It may also open paths that did not exist before.
The GM does not need to write every new path immediately.
But the world has to acknowledge that the original path can no longer continue untouched.
Killing an important NPC does not have to break the scenario
Many GMs fear the death of an important NPC because it may bring the scenario to a halt.
If a clue exists only in that NPC’s dialogue, their death makes the clue disappear.
If only that NPC can open an entrance, their death closes the path.
If only that NPC can offer the quest, their death leaves the players with nowhere to go next.
This can happen.
But the players are not always the ones who broke the scenario.
Sometimes the scenario placed too many conditions on a single person.
An NPC can be important.
They can be important enough that their death changes the entire situation.
But changing the situation is not the same as stopping the game.
After the NPC dies, the players might find an undelivered document in their room.
They might infer what the NPC knew from an enemy’s reaction.
Without their guide, they may need to find a more dangerous or expensive route.
They may have to face a force that the NPC had been keeping under control.
They may also lose an answer that can never be recovered.
Not every clue has to be delivered.
Not every path has to remain open forever.
What matters is that when the players lose something, the loss comes from events that happened in the world.
It should not vanish or reappear only because the GM discovered that the prepared scenario could no longer continue.
What the dead leave behind changes what the living can do
The items carried by an NPC do not disappear when the NPC dies.
Weapons.
Keys.
Letters.
Evidence.
Money.
Talismans.
Medicine.
Maps.
An insignia representing membership in a faction.
All of these things still exist.
They may remain beside the body.
The players may take them.
An ally may recover them.
The police or guards may collect them as evidence.
Another NPC may steal them.
They may also be lost in the confusion.
Where those items go changes the conditions for later actions.
If the players take the key, they may enter a place they were not expected to reach yet.
If they wear the dead NPC’s insignia, they may gain an opportunity to impersonate them. They may also attract the attention of whoever was hunting the original owner.
An unsent letter may allow the dead to keep changing the story even after they can no longer speak.
If the GM records only that the NPC died and never resolves what they were carrying, the death is only half complete.
The dead stop acting.
Their belongings transfer part of their ability to act into the hands of the living.
A faction may lose more than a member
If the dead NPC belonged to a faction, the consequences continue into the organization.
The death of an ordinary member may have little effect.
It may also leave a group without the only person who understood what was happening.
The death of an officer may begin a struggle for power.
The death of a leader may split the organization.
The death of a negotiator may close the only path to peace.
The death of the person controlling a resource may suddenly leave their subordinates unable to act.
If the NPC had superiors, subordinates, allies, or enemies, their death is more than a change to one character’s state.
A node has been removed from a network of relationships.
Every connection maintained through that person may need to find a new place.
Who takes over?
Who refuses?
Who uses the vacancy to seize power?
Who suspects the players were involved?
Who runs away or changes sides after losing protection?
An NPC’s death may take only one line in the campaign log.
For a faction, that line may rearrange its entire structure.
Death also leaves questions about who knows, who saw it, and who believes it
An NPC’s death is a fact.
That does not mean everyone in the world knows it immediately.
The players may have witnessed the death.
A distant ally may still believe the NPC is alive.
The faction may know only that the NPC has disappeared.
An enemy may receive false information.
Someone may find the body but misunderstand the cause of death.
Another NPC may know that the players were responsible and choose to remain silent.
“The NPC is dead” and “everyone knows the NPC is dead” are not the same state.
Death immediately limits what the dead character can do.
Its social consequences unfold as information travels.
A wanted notice may not appear at once.
Revenge may wait until the body is found.
A struggle for control may begin only after the news reaches the faction.
Someone may even arrive for a planned meeting because they do not yet know that the other person will never come.
A TTRPG world needs to remember more than the death itself.
It also needs to preserve the delay before everyone understands what happened.
The system cannot infer who knows what from a single sentence.
The GM still has to confirm that information explicitly.
The world should not quietly patch over a death
When an important NPC dies, the most dangerous solution is to restore the world without telling the players.
Create someone else who knows exactly the same information.
Place another identical key nearby.
Introduce a character with the same personality and function.
Have another faction member deliver the same lines.
None of these choices is automatically wrong.
A world can have backups, heirs, deputies, and several sources for the same information.
The question is whether those alternatives already existed in the world, or whether they can grow naturally from the reaction to the NPC’s death.
If they appear only because the GM needs the plot back on its original path, the players will feel that the death changed nothing.
The world seemed to accept their choice, then quietly filled in the space it left behind.
Respecting player freedom does not mean letting the players do anything without resistance.
It means allowing what they have done to change the world they face afterward.
An NPC can be replaced.
But the replacement should also be an event.
It needs a person, a reason, time, and a cost.
It cannot be the GM renaming a lost plot function behind the screen.
InkWeave does not choose a successor. It keeps the death in effect.
In InkWeave, an NPC can exist as a world entity like any other character.
Once their death is established, their state changes.
They can no longer move, trade, or participate in later events as if they were still alive.
The items they carried have to be handled.
Those items can be transferred to living characters or left at the location where the death occurred.
If the GM later returns to an earlier point and gives the NPC another item before their death, causality validation can point out that the previously confirmed handling of their belongings no longer matches the current world state.
If the NPC was a faction leader or occupied a place in its hierarchy, their removal may also create a leadership vacancy or a break in the chain of command.
These checks do not choose a new leader.
They do not automatically hand the clue to another NPC.
They do not rewrite the quest.
They do not quietly repair a future that is no longer possible.
InkWeave does something more restrained.
It points out the later events that no longer work after the death.
Who inherits the position, where the items go, and how the information returns to the story remain decisions for the GM.
The death is not automatically repaired.
It simply continues to count.
An NPC’s death does not end the scenario. It forces the world to account for the loss.
The death of an important NPC can catch any GM off guard.
Prepared scenes stop working.
Clues lose their source.
Items change hands.
Factions develop vacancies.
Later events lose the conditions they needed.
That does not mean the players destroyed the story.
They made it impossible for the world to continue along the original path.
The GM’s job is not to restore the dead character as a plot function.
It is to understand what the death affected.
Which futures are now closed?
Which items still exist?
Who will be affected?
Which relationships are becoming unstable?
Which information may be lost forever?
What new conflicts are beginning to grow from the vacancy?
An NPC’s death is not the deletion of a name from the notes.
It forces the entire world to account for what was lost.
The players may have killed only one NPC.
But a world that respects causality will remember how many possible futures were connected to them.