One-shots have a reputation for being the easy version of tabletop RPG. Shorter prep, lower stakes, no need to remember what happened three months ago. That reputation is wrong.
I've run a lot of them. Some went well. Some collapsed inside the first hour and never recovered. The difference between the two is rarely about the story. It's almost always about the decisions made before anyone sits down at the table.
What Actually Goes Wrong
Three things kill a one-shot more than anything else.
The first is players who haven't committed to a character before the session starts. In a campaign, you've got weeks to figure out who you are. In a one-shot, you've got about ten minutes before the story needs to move. Players who turn up without a clear sense of their character spend the first hour finding their feet, and by the time they do, you're out of time.
The second is a plot that needs too much setup. I've made this mistake. You've got a rich world, a layered mystery, factions with competing interests. It's good material. It's also material that needs four sessions to breathe, and you've got one. A one-shot plot should be legible within fifteen minutes of starting. If it isn't, cut it down.
The third is trying to fit a campaign into a single evening. This sounds obvious. It happens constantly. The instinct to give players a complete arc, a satisfying resolution, a meaningful ending, is understandable. But a one-shot doesn't need all of that. It needs one good scene, one real decision, and an ending that lands. That's it.
Chaos as a Design Tool
When you're working with limited time, the mechanics and items at the table need to carry more weight than they would in a longer campaign. A magic item that creates an unexpected situation is worth more than three pages of backstory. It gives players something to react to, and reaction is where the interesting stuff happens.
This is something Paul and I thought about a lot when we were designing The Jeff Paradox and The Blood Paradox. Both games are built around the idea that the situation should generate the story, not the other way around. You don't need a detailed world. You need a setup that forces people to make choices they didn't expect to make.
Running The Jeff Paradox
The Jeff Paradox puts players in the role of competing personalities inside a single alien hive-mind, all of them trying to control one very confused human-shaped being called The Jeff. It's chaotic by design. Players are working against each other and with each other at the same time, which creates a specific kind of energy that's hard to get from a standard cooperative game.
What catches people off guard is how quickly it escalates. The first few rounds feel manageable. Then someone makes a move that shifts the balance, and suddenly everyone's scrambling. My advice: let it escalate. Don't try to manage the chaos. The game is designed to survive it, and the moments that come out of that scramble are usually the ones people talk about afterwards.
It works well with groups who don't know each other. The competitive element means you don't need established group dynamics to get something interesting out of it.
Running The Blood Paradox
The Blood Paradox is a different kind of session. Gothic, improvisational, built around the shifting control of Dracula. Players gain control of the character and lose it just as fast. The tone is darker than The Jeff Paradox, but it's still fundamentally a game about chaos and consequence.
The thing to get right before you start is tone. The Blood Paradox can go very dark or stay at a campy horror level, and both work, but you need everyone at the table to be playing the same game. Spend five minutes before you start agreeing on where the dial sits. It saves a lot of awkwardness mid-session.
The setting is flexible. We wrote it for a classic gothic world, but I've seen it run in a 1920s speakeasy and a modern airport. The curse travels. The night is yours, as the book says.
A Few Things Worth Knowing Before You Start
Agree on tone before anyone picks up a dice. Not just horror versus comedy. The specific flavour of the session. Five minutes of conversation upfront prevents a lot of confusion later.
Give players a character concept, not a character sheet. A concept is something they can hold in their head and act from immediately. A sheet is something they have to read and interpret. In a one-shot, you want the former.
Know your ending before you know your beginning. Work backwards. Decide what the final moment of the session looks like, then build toward it. You don't have to hit it exactly, but having a destination stops the session from drifting in the last hour.
And if it falls apart anyway, that's fine. Some of the best sessions I've been part of were ones that went completely off the rails. The plan failed. Something better happened instead. That's the game.
The Games
The Jeff Paradox and The Blood Paradox are both available in the shop. If you run either of them, let us know how it went. We're genuinely curious.