I have a table of six players already, and have more people interested in joining my game. I wanted to consult people who had experience with running large tables to see if running for larger groups is mostly the same or whether it gets complicated or has special concerns.

Specifically in this question, I want to talk about overall game speed and how to keep up a reasonable tempo when there's a lot of people taking turns.

What strategies can you implement to speed up your game when dealing with large numbers of players?

It would seem that there are a probably other possible side effects of running larger groups - greater weight-of-rules complexity in a given encounter, problems balancing encounters, player disengagement, larger weight of disruption and interruptions, engagement issues between more and less outgoing members, scheduling difficulties, the game just slowing down, and maybe more. Those are left for other questions to explore except inasmuch as they are directly relevant here.

How do I run a game for a larger group? (But focuses on engagement)

  • 1
    \$\begingroup\$ I'm voting to close this as Too Broad as it species no system or even style of gameplay, which seems to be a minimum bar to determining how gameplay and pace should be handled. \$\endgroup\$ Jun 7, 2017 at 16:19

6 Answers 6


I blogged about this fairly recently. http://gm.sagotsky.com/?p=225#more-225 Here's a summary of what my post suggests:

  • Time limits per turn, the most obvious move. Get a timer, and if a player doesn't announce an action within a given time frame, the action is not performed.
  • Give out a bonus for players who take action immediately instead of dawdling. Let those who declare and roll right when their turn begins a +1 bonus to their roll, balanced out by flawed decisions taken in such a hurry.
  • People tend to get distracted while waiting for their move, especially when you still have the problem of rounds taking too long. During initiative, call out whose turn is taking place right now and whose turn is next, so the next player takes his/her time to think and prepare before his/her turn.
  • Tell players to gather expected dice before their turn begins and roll them at once whenever possible. This might mean that you will have to buy some more differently coloured dice.
  • Ask your players to sit in their turn order, then passing the turn clock-wise (or counter-clockwise, your choice). It will make it far more visible whose turn is next.
  • Roll enemy initiative and other checks in advance, when you just prepare for the game and print character sheets.
  • Appoint a rules lawyer, someone who is not the GM and knows the rules well enough to consult other players. Not only is GM time saved, but your rules lawyler also gets too occupied too distract the GM himself -- you kill two hares with one shot!
  • 3
    \$\begingroup\$ Oh, giving a bonus to fast-acting players could be a powerful motivator in the right group. \$\endgroup\$ Apr 29, 2011 at 20:19
  • \$\begingroup\$ could you explain further "Sort players by turn order."? \$\endgroup\$
    – apacay
    Apr 30, 2011 at 2:51
  • \$\begingroup\$ @apacy, it's explained in the link at the top of the post. Basically when you roll initiative you make the players get up and reseat themselves in the order they rolled. I helps show them whose turn it is and lets them take turns without your prompting. \$\endgroup\$
    – valadil
    Apr 30, 2011 at 4:40
  • \$\begingroup\$ @SevenSidedDie Would it be OK if I get more info from the original post to that answer? Currently it feels kinda incomplete, like a link-answer. (Yes, I know that it's been almost 6 years since it was written) \$\endgroup\$ Mar 9, 2017 at 18:37
  • \$\begingroup\$ @Baskakov_Dmitriy The current version is brief but does give an adequate “what to do” answer that doesn't require reading the original to understand or use. What additions were you thinking of? \$\endgroup\$ Mar 9, 2017 at 18:40

On the chance that this doesn't get merged into a different question, I'll go ahead and answer.

Specifically you're asking about ways to speed up play. My group has in the past implemented a couple of rules:

  1. 30 Second Decision time in combat - As in, know approximately what you want to do before your turn comes around, because once it does you have 30 seconds to state your action. If you need more time, delay. This is best with all experienced players, since the newer ones might need more time to get in the swing of things.
  2. No lone wolfing - Unless you have a legitimate (and group approved) reason to go off by yourself (such as a stealth character heading ahead to scout things out), you don't get anything accomplished until your character returns. Period. If you want to go wander out in the woods alone, and the GM has no story reason for you to do so, you go off by yourself and return some time later having gained nothing. This is only meant to punish those who tend to go off alone all the time and for no good reason.
  3. Rules Arbitration - We try to keep arbitrating the rules to a minimum during game time. If you think a game mechanic or rule is being done incorrectly, and you cannot cite specific examples rapidly (under a minute or two), we won't discuss the rule until after the game. Now of course we make exceptions for really serious things (like a character death will occur if the rule is incorrect) and using a bit of common sense.

Other offhand tips include: Sitting around a table helps keep the game focused I've found, if you have snacks make sure that they are at hand so you don't have to leave to get up, and other things that would cause disruption.


I had 7 players in my last game, so I feel your pain. Here are some things I did.

  1. Let everyone know that things will take a while with so many players. Game actions like combat in D&D can take an age with so many at the table, and it'll take some time for you to "move" all the monsters since you'll need a small horde sometimes to make the fight challenging. If someone can't be patient, perhaps that player needs to find a different table.

  2. For D&D 3.5 combat, I printed 3x5 index cards for PCs and monsters listing all stats and powers, then stack the cards in initiative order. I also had a sheet with HP and defenses sketched out so I could see the full stats of the active being and just the defenses of anyone they wanted to attack. Questions about "who's next" disappeared and we saved some time.

I'll have a couple more ideas on this tomorrow when I have some sleep in me and my brain can string words together again.

  • 1
    \$\begingroup\$ 2. Is great. If I might add that if you have a PC who likes to summon things, making them write up the stats of their most common summons before play time is an excellent idea. \$\endgroup\$
    – Cthos
    Apr 29, 2011 at 4:04

There are two choke points that can arise, most of the answers here address the obvious player-as-chokepoint. I'll start with gm-as-chokepoint.

Outsource as much as possible.

You have one brain which is able to process a limited amount of data in a given span of time. Every single player at the table places demands on that one brain. When the demands exceed your mental bandwidth, things slow down and you're a choke point. This gets especially bad when the party splits and you need to manage a subset of your actual group - especially if you favor crunchy realism and want to give the group you just left idle an equal amount of time to take actions, etc.

Giving the players as much autonomy to DM/GM themselves as you are comfortable with removes demand on your processing time as requests that would have come through you, now get resolved locally. Obviously there is a trust factor needed here, but recognize things which are unimportant to your objectives and simply outsource them to the players for whom those actions matter.

Good candidates for outsourcing:

  1. PC vs. PC dueling/sparring/opposed-rolling (they know the rules and their characters well enough, or you can appoint another player to govern that while you work with the people not part of that scene).

  2. Batch skill checks such as... Spellcraft to identify magic items, in this example: Get a list of the items in question, give a DC next to each if relevant, hand off to player and have them note where they succeed while you manage other requests.

  3. Keep a cheatsheet handy with all relevant PC stats on it so that you don't need to constantly hold those in memory. (Most of us do this, but it's the same sort of thing).

And for conventional player-as-choke stuff:

Encourage players to deliver vitals to you:

Consider the following interaction:

GM - Action?

Player - I will step forward and lunge with my rapier.

GM - Roll it.

Player - 17... ummm... plus 4... plus 2... 23.

GM - Nice, hit. Damage?

Player - Hang on... [rolls]... ummm, 12.

GM - Your rapier tip pierces the fellow's abdomen, not likely to stop him but he'll be feeling that one for a while... [GM moves on]

You can shorten that entire process by having your Players frontload the dicing and math before their turn, once they've decided on their action.

GM - Action?

Player - I step forward and lunge with my rapier striking an AC of 23 for 12 damage.

GM - Nice. Your rapier tip pierces... [and so on].

Other suggestions already included above such as putting your players on a clock and rewarding players who are speedy are also good.

Limiting talking during initiative-phase action (or making people actually use actions to talk to each other during them) helps cut down on how long people will kibitz before deciding on an action for their character - this also cuts down on some of the social fun of the game, however, and groups will need some time to get used to working as a team when they can't communicate endlessly. (Or they'll seek out telepathy or other back-doors to communicate.)

Perhaps the most important thing you can do to make big games operate more smoothly, however, is not focus on speed...

Accept the reality of your situation:

More players = more demand = more lag time. Newer players will need more handholding as well, (a thing you can outsource if you have experienced players who can help newbs well) and this will really slow things down.

This is okay! As long as you and your players approach the table with that understanding, and you as the DM schedule appropriate extra time to compensate for the increase, all will be well. There are some games I have no problem running with groups of 10-12 (Battletech/Mechwarrior RPG comes to mind) and it's usually because I know the system well enough that I don't need to look stuff up anymore. Other games (like whitewolf's oWoD) I max out at 6 simply because of how much more hands-on I have to be with each player. Know your limits and plan around them.


I regularly run a one-day invitational with up to twelve players, GMing it by myself; it's 1st edition AD&D, if that makes any difference.

Out of combat, it doesn't matter how long they take. In real life, it genuinely does take some time to get twelve people to agree on anything, even pizza toppings. If some players find the pace too slow, they have it within their power to speed things up within character ("I swear to Heimdall, if that cursed dwarf doesn't stop fixating on how we'll re-cut the Eye of Argon when we haven't even recovered it, I'll stick his axe right down his mineshaft, if you get my drift."). They're aware of a general background pressure of time ("if we wait until tomorrow, then although we'll have our spells back, the reinforcements our spy saw will have arrived"), but it's up to them to decide how to prioritise and trade-off.

If the players don't mind things going slowly when the game logic permits it, and they're having fun, who am I to care?

In combat, it's different. I tend to aggregate monster attacks, simplify their rolls, ignore details which will complicate and thus slow down the play; this is all done behind a screen, so I don't have to justify it to the players.

When it comes to the players' attacks, they're arranged in a horseshoe at the gaming table, and they're used to me sweeping my arm across the party in order (alternating the end at which I start), and as my arm reaches each player, I want a "declaration of intent" within 5-10 seconds. We roll party initiative en bloc on a d6; if we rolled individual segment-based initiatives on a d10, I'd simply run through the integers from 1-10 the same way.

If they don't get their declaration of intent out, they lose that round's action through dithering. If they have questions, perhaps "Could I shout a warning to the elf, drop the broken axe haft and attack with a dagger all in one round?", then a little horse-trading with me is OK: "yes, if the warning is five words or less, and you understand you won't attack until the very end of the round"; the cardinal sin is standing there open-mouthed when the arm points at you, with no clue what you want to do.

Yes, this can be hard on players whose attack is early on; but that's combat. If in the middle of 60 seconds' worth of cut, thrust, and parry, the opportunity for pressing the attack comes three and a half seconds in, and you're not ready for it, well, tough.

I also ruthlessly trim player interaction during combat. Anything you want to say to a fellow player had damned well better be done during your action; players who insist on having tactical discussions "in the background" know that there will be loss of action, -ve xp, and ultimately "the disfavour of the Gods" (ie, you're going to start getting very unlucky).

I'm sure it helps that I'm playing old-style D&D, where the flow of time is fairly simple; one thing that's put me off later editions big-time is the huge complexity of time flow, where players with the right spells/skills can insist on jumping into the time flow.

But on the whole, the players have been fine with this; they get the chance for long drawn-out planning and discussion sections, but when combat strikes, it's going to be fast, messy and disorganised. I've never been in melee combat myself, but my understanding is that it's often fast, messy and disorganised. At any rate, the palpable feeling of relief amongst my players when the last ogre surrenders and the players are still standing, and the subsequent back-slapping, congratulation and general signs of "decompression euphoria" suggests that this works for them.


I've been at a table with probably a dozen players before. This is one of the few times when it can actually be beneficial to the flow of the game, to find some way to split the party during combat situations.

First, this does require two DMs. Then, you need find some way to get the party split into two groups and separated enough from each other that one group's actions will not likely affect the other group in real-time. Then, just run the combats separately as if they were two entirely different games.


Not the answer you're looking for? Browse other questions tagged .