A friend who’d primarily played in and run long-session games found herself about to run a weekly game on work nights, and asked for my advice on how short sessions differ from long. Here it is, repackaged and with advice from the other side (for those who’ve done short games but are intimidated by the longer form).
As a meta-consideration, how often you’re going to run the game can make a big difference. In general, the less often you can play, the longer you’ll want to play when you do get to play. The longer you go between sessions, the more your players will forget, and the less inertia you’ll have at the start of a session (which lets you get even less done, as your players try to rediscover their characters and remember their goals).
- If you’re playing monthly or less frequently, you generally want to get enough done in a session to reach a solid stopping point, where time can pass in play as well as out of play; if you leave your players in the middle of a mission or dungeon and they don’t play for a month, it’s going to take forever to get them back up to speed.
- Conversely, if you’re playing weekly (or more frequently!?), you can often leave off at the closest break that makes sense as soon as you’re ready to quit for the night, and trust your players to remember what’s going on when you resume.
- When you’re playing every other week, you’re in a weird spot where you don’t really want to leave too many irons in the fire, but you also don’t have to end on too much of a solid note. Your players will forget minor things, but probably not major things.
All of these issues can be mitigated by having someone at the table that takes copious notes and can recap the events of the last session at the start of the new one. It’s a really big help to have someone like that, and if one of your players is a natural game journalist, encourage it.
For a short session, I’m generally assuming that this is a weeknight at or after dinner for 3-4 hours. Some of this might not apply if you’re squeezing in gaming at an odd time, and your session length restriction is not because you’re playing after work/school. Some of this may apply even more seriously if you’re only playing for an hour or two during a mealtime. The three big limitations of a short session are side chatter, spotlight time, and combat time.
If possible, establish a set schedule of when you’re focusing on the game and how much table chatter is too much, and make sure everyone sticks to it. Nothing kills your time worse than people gabbing about what they’ve been up to all week and otherwise chatting about meaningful but non-game things. Your biggest issues are how long it takes to actually get started and how often people get sidetracked once you start playing.
The first is a function largely of when people show up and when they’ve eaten. I tend to not even try to get people in game until everyone’s there and done eating; if you try to start and someone shows up later and/or someone’s still eating, it can be really hard to make the game go because they’re a distraction. Conversely, you want to make sure people aren’t showing up super late or taking forever to eat. It also really helps if your players see each other more often than game night, particularly if they’re good friends: if your game time is the only time good friends are going to see each other face-to-face this week, it becomes much harder to get them to focus on the game instead of catching up.
The second you have more control over, but you may have to be more draconian than you’d like. Small jokes are fine if they don’t derail focus on the game: it’s when someone tells a joke and someone else uses that as a “that reminds me…” to talk about something else that causes a problem. You basically have to yank those back to the game if they go on for more than a few seconds, and start to determine which people can safely quip without breaking focus, and which people can’t even be trusted with one-liners. If you’ve got a cut-up that’s causing problems, you have to school yourself and the other players to not reward the behavior; people that are constantly trying for a laugh to the detriment of the focus on the game will (generally) eventually pick up that people aren’t that amused at the distraction and pull back, as long as they’re getting tolerant annoyance off the others rather than laughs.
Player spotlight time is best kept small in short sessions. If a player is off doing something that takes a while and is doing it solo, that can potentially eat up a huge chunk of your playtime so the rest of the players don’t get similar focus for the evening. If a player wants to go off and accomplish something alone, try to narrate it down and err on the side of just letting her accomplish it (particularly if it doesn’t have a major impact on the main plot). If you want there to be a chance of failure, try to sum everything up to a few quick dice rolls, with varying degrees of accomplishment depending on how many rolls are a success.
In general, try to just err on the side of giving players what they want if it won’t make a big impact on the story. Time spent on them convincing you that they can do something and then having to improvise challenges for it, when you’re pretty sure it’s going to be a success, can be wasted time. You can just as easily offer them a devil’s bargain of something like, “Okay, you can do that, but it’ll result in the town guard being pissed at you.” The caveat is that you can absolutely play out unplanned side-excursions if everyone at the table seems super into it. It’s not about using narration to gloss over everything outside of the main plot, so much as not wasting time that could be more productively spent.
Combat time can be a huge pain for shorter games, particularly in D&D and other heavily tactical games with mapping and miniatures for fights. Particularly for games with slower combat, but possibly for any game where fights can eat up too much time: try to figure out if there’s a reasonable game resource you can use as a “narrated success” tax. For example, in D&D 4e and 5e, if there’s a fight that the PCs will get to take a short rest after, you can just ask them to use up a couple of healing surges/hit dice and maybe a daily resource. Then just describe the gist of the fight with a total success. Essentially, if you think there’s no chance of anyone getting seriously injured, using permanent resources, or being that engaged in the fight, it’s perfectly fine to just describe how flawlessly they party wiped out the minor threat and move on so there’s more table time for more interesting fights.
This is possibly more relevant to running modules (where there are often a bunch of filler encounters that don’t affect the plot or really challenge the players), but even when you’re planning your own stuff, be ready to throw out your babies if you realize you’ve put in a combat encounter that won’t actually raise the tension much but will eat up a lot of time to play out. You could even do this on purpose: plan out fights where all you have is a description of what’s in the room but you haven’t bothered to organize the stats, and they’re essentially just opportunities to make the players feel awesome and to let you burn off some of their daily resources before a real fight. Conversely, if players are clever enough to get around them or roleplay through, then they save the resources, but if they totally mess something up you can add a couple of speedbump fights together into a real threat.
I consider a long session to be over four hours (often six or more hours). You’ll generally get to have these on weekends and holidays unless you’re still young enough to manage an after-dinner-until-after-midnight session without everyone falling asleep before the end. They often overlap at least one mealtime (unless you have an early lunch and a late dinner with a session in between), so the biggest considerations for long sessions are blood-sugar and attention-span related.
For short sessions, particularly those that start with or right after dinner, table snacks are fun but rarely required. For long sessions, they’re more or less essential. You should absolutely get in the habit of either rotating snack duty or getting everyone used to bringing a little something to the table such that there’s a bounty of available foods. You should also work out the healthiest assortment of foods that the group will eat and can afford: cheesy poofs and candy are fine when you’re still in college, but nuts, veggies, and fine cheeses are better for the over-thirties to not wreck their increasingly delicate internal mechanisms. All of these things are to keep hunger from being a distraction.
Unless you truly bring copious snacks or lay out a buffet, a mealtime is probably going to hit mid-session and will require a pause (to consume the food, even if you can get it to the table quickly, but usually to make, order, or go get the food as well). But that’s fine, because one of the problems with long sessions anyway is the mid-session lull. After three or four hours, it’s hard to maintain tension and attention spans start to wander. So even if you don’t have a meal break, plan your game as if you did. Try to have a major story beat, cliffhanger, accomplishment, or other stopping point happen close to the middle of your session time. Then break for food (or just take a general purpose stretch, conversation, and smoke break if you aren’t breaking for food). Ramp back up slowly after the break so you can end the session on another high point (i.e., it’s very much like stapling two short sessions together around a meal break). The break and ability to ramp up again gradually helps with fraying attention spans in the middle of the session.