The world does not pause while the players are doing other things. An event makes that visible. It hands the NPCs new problems and hands the players new choices — usually both at once, which is the point.
A festival brings opportunity. A plague brings urgency. An assassination redraws the board. A drought makes water political. None of these require the players to have caused them. They happen because the world has its own momentum.
Events work because they change what
The test for a useful event: does it create friction the players can act on? A festival the players can attend, exploit, or disrupt is an event. A political collapse narrated in a cutscene is not — it is a history lesson. Good events are open. Bad events are already over.
Sometimes the players walk away from the campaign you prepped. Not out of spite — because something caught their attention and they followed it. That is the game working. But occasionally the story you want to tell requires them to be somewhere specific.
An event can bring them back without the GM pulling rank.
The Hurricane Principle. The players say: we set sail and leave the island. A day out from shore, a hurricane destroys the ship. Next session, the players wash up on... the island.
The GM never said no. The world just had weather.
Use this sparingly. Once or twice a campaign, it is exactly the right tool. More than that, the players will start to notice that the world only ever has weather when they try to leave — and once they smell the railroad, they will resent every thunderstorm for the rest of the campaign.
The principle generalizes well beyond hurricanes. A landslide closes the pass. A letter arrives from an old name the players recognize. An NPC shows up with urgent news, looking winded. All of them say the world pulled you back here without the GM ever having to say it directly. The event is the hand on the shoulder. Keep it light.
Drop three rumors of things that might happen. The players will notice one and ignore two. Use what they noticed. The other two sit in the background — occasionally visible, occasionally referenced — and the world will feel like it was moving before the party arrived.
The ignored seeds have a quiet virtue: they make later events feel earned. The players hear about the drought two sessions before the drought matters. When it finally matters, they do not feel ambushed. They feel like they should have paid more attention — which is exactly the right feeling.
This is the same instinct behind planting more seeds than you need in Planning a Campaign. Rumors work the same way. Plant more than you can use. The world will look full.
An event is a scene prompt, not a cutscene. You are not narrating something that happened — you are handing the players a moment and seeing what they do with it.
Show the flood arriving through the eyes of an NPC the players already know. Show the fire reflected in a window they have looked through before. Show the news arriving by a messenger whose name they remember. The event is happening to the world, not at the players. Let them react. Let them decide what it means for them.
Concrete and specific beats large and abstract every time. "The river is rising" is an event. "The east bank flooded overnight — Maret's mill is gone, she is in the square, and she is asking for the party by name" is a scene.
The world remembers. That is the part most GMs skip, and it is where events pay off.
The merchant whose stall burned is poorer this season. The priest whose temple flooded is collecting donations with a slightly desperate smile. The festival nobody attended because of the plague is remembered as the year the music stopped. Every event leaves a residue — and when the players walk back through a location they have been to before, that residue is what makes it feel like a place that kept existing while they were gone.
This belongs in the category of consequences, not punishments. Events are the GM remembering, not the GM retaliating. The drought did not happen because the players made a bad choice. It happened because the world moves. The consequences land where they land. That is how a campaign starts to feel like it has history.
Events always land somewhere specific — a location that now looks different, a waystation that has new problems, a place the players will want to revisit. Creating Locations covers how to build the anchors that make those landings matter. And the moment you decide to deliver an event mid-session — the knock at the door, the messenger in the square — that is a question of pacing and handoff, which lives in Session Flow.
© Soltherra RPG System