
Racon Gunner Dispatches
The Players Drive the Plot. Consequences Write the Story.
A scenario is a starting position, not a railroad schedule.
Too many campaigns mistake preparation for destiny.
The Game Master plans encounters, scenes, and revelations. Then the players make an unexpected decision and the campaign spends the next hour forcing them back onto the track.
That is not a story. It is crowd control.
Follow the consequence
The most reliable rule I know is simple: ask what would logically happen because of what the player characters just did.
They robbed the wrong house. Who owns it? Who profits by blaming someone else? Which ally now doubts them? They spared the villain. What does the villain do with the gift of time? They destroyed the artifact. Which old protection disappeared with it?
Consequences turn players into protagonists because the world begins answering them.
Prepare forces, not outcomes
Build people with motives, institutions with needs, and places under pressure. Know what each force will do if nobody interferes. Then let the players interfere.
This approach does not eliminate preparation. It makes preparation useful. Instead of writing scenes that must occur, you build a world capable of reacting.
The result belongs to the table. Players stop saying, “We finished that module,” and start saying, “Remember when we caused that war?”
A scenario is a suggestion. The world is the stage. The players make the move. Consequences write what happens next.