How do I plan a short Daggerheart campaign (not a forever game)?

Techniclee

Forever sandboxes eat groups, and short campaigns finish. I pick the end before session 1, aim for a length my table can keep, and treat the frame’s sparks as fuel I will burn, not a wiki I will maintain.

End condition first

I write the finish line in one sentence before the first night, whether that is the prisoner rescued, the town saved or the party out of the city. If I cannot name the end, I am planning a forever game by accident.

For a first arc I aim at three to six sessions. That is enough for Fear to carry between nights, for a rest pattern to form and for one real climax, and it is not so long that character creation and travel eat the promise. I wrote down my own table’s real counts in how long a Daggerheart campaign runs in real sessions, and the first night has its own post in going from campaign frame to session 1.

Sparks as fuel

I circle three sparks from the frame and decide roughly when each one burns. The rest stays on the page. An infinite sandbox is how a short campaign turns into a folder you feel guilty about.

How I run a long campaign as short arcs

Our Motherboard campaign is not short, and it is still going, so I will not pretend it is a model of a five-session game. What keeps it moving is that I plan it as a run of short arcs, each with its own end condition. The prologue had one, which was getting the party off the roof with a choice about where to go next, and it finished in three sessions. They chose Mother, and the prologue ended with a level-up and a time jump.

Mother’s first job had one too. The end condition was rescuing the person Mother wanted back from the Collector, and I planned it for three sessions. It took four, because the bridge fight I had made deliberately deadly and a slow night of stripping scrap and talking to strangers pushed the lair back a week. We still hit the end condition, and the players felt done with the job rather than abandoned in it.

The sparks worked the same way. One of the long-term countdowns I had planned was remnants overrunning Scholea, and it burned faster than I expected. The next arc became a relief run to Scholea, planned for two sessions, and it took two because I cut every scene that did not push toward the town.

What I would change is saying the end condition out loud. On the Collector job I kept it in my notes, and naming it at the start of the first session would have made that slow scrap night feel like part of the arc rather than a detour.

What I would do tonight

Write the end in one sentence, pick a session range and circle three sparks. Leave the worldbuilding for later, and say the end condition out loud at session 0 so nobody expects forever.