Lobbyit
How to plan a game night that actually happens
A game night happens when four things are fixed in advance: an exact time, a set number of seats, a reminder that reaches everyone shortly before, and one place where the match code gets posted. Game nights fail when they're planned in a group chat, because a chat has none of those: the time drifts, nobody knows who's in, and the reminder is somebody remembering to type 'we still on?'.
Fix the time, not the day
“Thursday” isn’t a plan. “Thursday at 21:00” is. A time means people can finish dinner, put kids to bed and sit down with five minutes to spare, and it means a reminder can fire. In Lobbyit a game night is posted with a time, and that time is what the reminder on everyone’s phone is set to.
Give it the right number of seats
A chat can’t be full. A game night can, and should be: the seat count should be the game’s. Lobbyit matches it automatically: five for an Overwatch 2 team, four for Helldivers, 150 for a Warzone private match. People grab a seat until there are none, and anyone who arrives late sees it’s full rather than turning up as the sixth person for a five-person team.
Let the reminder do the nagging
The person who organises the night shouldn’t also have to chase it. Fifteen minutes before, everyone’s phone says it’s nearly time. That one notification does more than a week of “we still on?” messages, because it arrives at the moment it’s useful.
One place for the code
When it’s time, the host drops the match code in the squad’s chat. Everyone’s gamer tag for the game is at the top of the same chat, one tap to copy, so nobody is reading a friend code aloud or hunting through a thread. The night starts when the time says, not twenty minutes later.
Make it weekly
A one-off takes organising. A regular night organises itself: Sunday Run, 21:00, pinned at the top of the chat with Going, Maybe and Can’t underneath. Three coming this week. Someone says Sunday works better than Thursday, the host moves it, same time. Saying Can’t one week doesn’t mean you’ve left; next week the seat is yours again.
Filling an empty seat
When a regular can’t make it, the seat can go to someone outside the group. Lobbyit shows players online right now at your level on your platform, each with a record from past teammates: whether they’d play together again and a rank others have confirmed. People you know lists the ones who play when you play or asked to play again. And it keeps a record of who turned up to each night and who didn’t, which is the thing a group chat never remembers.
Without an app
You can do most of this by hand: a calendar event with the exact time, a pinned message listing the seats, and the discipline to post the code in one place. It works, with one organised person doing all of it every week. Lobbyit does the same job without needing that person. It’s on iPhone and Android, and posting a night is free.
Questions people ask
Why do our game nights never happen?
Because they're planned in a chat. 'Thursday?' gets three thumbs up, the time is never fixed, nobody's phone reminds them, and by nine someone's eating and someone's forgotten. The fix is structure, not keener friends.
How many people should I invite?
As many as the game seats, and no more. Five for an Overwatch 2 team, four for Helldivers, up to 150 for a Warzone private match. Lobbyit sets the seat count from the game you pick, so a night can't be 'full' with the wrong number.
How far ahead should I plan?
A few days for a one-off, so people can keep the evening clear. For a regular night, pick a day and time and pin it; people plan around a fixed Thursday far more easily than around a question every week.
What if someone can't make it one week?
They say Can't and the seat opens for someone else. In Lobbyit, saying no to one week doesn't take you out of the squad or off next week's night.
How does everyone get the match code?
The host puts it in the squad chat when it's time, and everyone's gamer tag for that game sits at the top of the same chat, one tap to copy. No reading codes out over voice.