The scheduling problem and the one rule that fixes it
The single biggest killer of weekly game nights is the scheduling death spiral. It goes like this: someone cannot make Tuesday this week, so the group moves to Wednesday. Next week, someone else cannot make Wednesday, so it moves to Thursday. By week four, there is no "game night" anymore — there is just a recurring negotiation that exhausts everyone. The fix is brutally simple: pick a day and time, and do not move it. Ever.
If someone cannot make it, the group plays without them. This sounds harsh, but it is the only thing that works. A fixed schedule turns game night from a negotiation into a habit. After about six weeks, people stop double-booking that time slot because it has become "game night" in their mental calendar, not "the thing I might do if nothing else comes up." The people who genuinely cannot make the fixed time were never going to sustain weekly attendance anyway, and it is better to learn that in week two than week twelve.
The "always have a default game" principle
Groups that spend the first twenty minutes of every session deciding what to play burn out. The solution is to designate a default game — something everyone owns, everyone knows how to play, and the group can launch with zero discussion. For my group, this rotates: we spent one season defaulting to Deep Rock Galactic, another season defaulting to PlateUp, and our current fallback is a rotation of Jackbox packs.
The default game does not need to be what you play every week. It just needs to be the answer to "what are we playing?" when nobody has a strong opinion. This removes the decision fatigue that kills game night momentum. If someone brings a new game they want to try, great — but the default is always waiting in the background, ready to launch.
Rotation strategy: one new, one known
Every successful game night I have been part of follows an unspoken rhythm. Play one new game early in the session while everyone has energy for a learning curve. Then switch to a known game for the second half when the group wants the comfort of competence.
Trying to play three new games in one night is a disaster — nobody learns anything and everyone leaves frustrated. Playing only the comfort game for months is how you lose the person who wants variety. The "one new, one known" rotation gives you both novelty and competence in a single session. It also means the person who picked the new game only has to convince the group for half the night, which is a much easier sell.
What to do when someone rage quits (or quietly leaves)
Every group has a session where someone gets too tilted and leaves the call, or someone quietly disconnects and does not come back. How the group handles this determines whether that person returns next week. The worst response is to stop the session and turn it into a group therapy discussion about the person who left. The best response is to acknowledge it once ("looks like Alex needed a break"), pivot to a lighter game, and move on.
Check in with that person the next day privately — not in the group chat, not with an audience. Most of the time, the frustration was about something outside the game, and a quick check-in turns "I am never playing with those people again" into "yeah sorry, I had a rough day, see you next week."
The equipment and setup checklist nobody talks about
Before your first session, make sure everyone has: a working microphone (test this on Discord before game time, not during), a stable internet connection (wired if possible — one person with 400ms ping ruins co-op horror), and the game installed and updated before the session starts. Nothing kills momentum faster than "give me twenty minutes to download the update."
Establish a pre-session ritual. Something simple like "everyone joins the voice channel, we shoot the breeze for five minutes while the last person finishes loading, and then we launch." This buffer absorbs the inevitable technical delays and turns them from frustration into hangout time. The groups that succeed are the ones that treat the technical logistics as part of the session, not an obstacle to it.