How to host a room people come back to

Anyone can create a room. Getting the same eight people to show up again next Friday is harder. Most of it has nothing to do with the game. It comes down to a stable connection, a bit of preparation and a host who is easy to play with.

This is a checklist we would give a friend who is about to host for the first time.

Start with the connection

Use a cable

In most old LAN games the host is also the server. Every other player's experience depends on the host's line. If the host is on Wi-Fi, everyone inherits the jitter. A short Ethernet cable to the router is the single most useful thing a host can do, and it costs almost nothing.

Check your upload, not your download

Hosting uses upload. The host sends the game state to every player, so upload use grows with the number of players. Old games are light, but not free, and some home connections have far less upload than download, especially cable and DSL.

A rough guide for classic titles:

Room	What to aim for
2–4 players, strategy game	Almost any connection with stable upload
8 players, strategy game	A few Mbps of upload that stays steady
10–16 players, shooter	Several Mbps of upload, nothing else competing for it

These are not hard limits. The point is that steadiness matters more than the headline number. An upload that is idle is worth more than a fast one that someone else is using.

Keep the line quiet

Cloud backups, game updates, streaming in 4K in the next room: any of them can fill your upload and add delay for everyone. Pause them for the evening. If your router has SQM or a similar QoS setting, turn it on. We explain why in Why your ping is high even on fibre.

Same game, same version

Version mismatches cause more failed evenings than bad connections do. Many old games refuse to list or join a host on a different patch, and some join fine and then desync twenty minutes in.

• Say which version you are running when you invite people. For example "AoE2 The Conquerors 1.0c" or "CS 1.6, Steam version".
• If the game uses mods or custom maps, list them and link to where to get them.
• Ask everyone to test a quick join a day before, not ten minutes before.

The per-game guides, like the ones for Counter-Strike 1.6, Warcraft III and Age of Empires II, list the settings and versions that tend to work together.

A clear room name and clear rules

A room name should tell people what they are joining. "Friday AoE2 — TC 1.0c — 4v4 Arabia — beginners welcome" is better than "games lol". People skip rooms they cannot read.

Put the rules somewhere everyone sees them. The room chat is fine. Keep them short:

• Game mode, map pool and team setup
• Whether mods or specific settings are required
• Skill level, honestly. "Casual, no rush" and "we play to win" attract different people, and both are fine
• Voice etiquette, if you use the built-in voice: push-to-talk, no music over the mic

For private evenings, set a password or send the invite link only to the people you want. For open rooms, the rules do most of the moderation for you.

Start on time

If you say nine, start at nine. Maybe five minutes later for stragglers. People who arrived on time are the ones you want back, and making them wait forty minutes for the one person still patching is the fastest way to lose them.

A simple rule that works: the first game starts on time with whoever is there. Late arrivals join the next one.

Plan the map rotation

Decide the rough plan before you start. Which maps, in what order, how many rounds. It saves the ten-minute debate between every game, and it keeps things moving.

• Open with something familiar and quick, so everyone can check that the connection feels right.
• Mix in variety in the middle. Playing the same map six times in a row gets old, even if it is a great map.
• End on a crowd favourite. People remember how the evening ended.

Ask for requests in the chat before the session, not during it. Then stick to the list unless most people want to change.

Handling lag

Someone will say the game feels laggy. Take it seriously, but check before changing anything.

1. Is it one player or everyone? If it is everyone, look at the host's line first. That usually means yours.
2. If it is one player, ask whether they are on Wi-Fi, or whether something is downloading on their side.
3. Ask them to run ping against your 10.60.x.x address for a minute and watch whether the numbers jump around. The route through our nodes is picked by measured ping and changes when a path degrades, but it cannot fix a congested home line or a player on the other side of the world.
4. If it keeps happening for one player on a connection that is otherwise fine, it may be an MTU problem. We covered that in MTU, fragmentation and the mystery 3% loss.

In older strategy games, one slow player slows the whole game down for everyone. Be kind about it. A quiet "can you try a cable next time" works better than calling someone out in front of the room.

Handling leavers

People disconnect. Power cuts, kids, crashed games. Decide in advance what happens, so nobody has to argue about it mid-game:

• In team games, agree whether you restart, continue short-handed or let the AI take over, if the game supports that.
• Give a few minutes for a reconnect when the game allows it.
• If someone leaves every game the moment it goes badly, have a word in private. If it continues, it is fine not to invite them next time.

After the session

Say thanks. Announce the next date while people are still in the room. Ask what they want to play next time. It takes a minute, and it is often the difference between a one-off evening and a regular group.

If you are hosting for the first time, download the Windows app, create a room, and do a test run with one friend a day ahead. Most problems show up in the first five minutes, and it is much better to find them before everyone else arrives.

Read next