LacNovaGame Studio

How online multiplayer games work, explained in plain words

A clear guide to how online multiplayer games work: servers, rooms, matchmaking, latency, fair results and reconnects, explained without jargon.

LacNova Team6 min read

Article

An online multiplayer game is a conversation between phones and a server. Each player's phone sends what the player did, the server checks it against the rules, decides what happens, and sends the same result back to everyone in the match. That loop runs many times a second in fast games, and once per turn in board games.

The phone is the window. The server is the referee and the source of truth. When you understand that split, almost every other part of online play makes sense: rooms, matchmaking, lag, cheating and what happens when someone's signal drops.

This guide walks through each piece in the order a match actually happens, using our own games as examples.

The two jobs: showing the game and running the game

Every online game splits its work into two jobs.

  • Showing the game happens on the player's device. It draws the board, plays the animations and sounds, and reads taps and swipes.
  • Running the game happens on the server. It holds the real state of the match: whose turn it is, where every piece sits, the score, and what is allowed next.

Keeping these apart matters. If each phone ran its own version of the match, two players could end up seeing two different games, and anyone who tampered with their phone could change the result. When the server runs the match, there is only one version, and every phone shows it.

Step one: getting players into the same match

Before anything is played, the server has to put the right people together. There are two common ways.

Private rooms

One player opens a room and gets a short code. Friends type that code on their own phones and land in the same lobby. In Ludo Fighters, online squads of 2 to 6 work this way, and NPL Cricket League uses private lobbies so friends can play a live match together.

Matchmaking

Players who want a game right now join a queue. The server looks at who is waiting and pairs people up, usually trying to balance speed against a fair match. We cover the trade-offs in matchmaking basics for mobile games.

Step two: the match loop

Once everyone is in, the match runs as a loop.

  1. A player acts: taps to roll, moves a piece, plays a shot.
  2. The phone sends that intent to the server. It does not decide the outcome.
  3. The server checks the action is legal, applies it, and works out what happens next, including any luck such as a dice roll.
  4. The server sends the new state to every phone in the match.
  5. Each phone animates the result.

In a turn-based board game, this loop runs once per move. In a real-time game, it runs continuously, and the phones fill the tiny gaps between updates with smooth animation so the game never looks jumpy.

Why luck belongs on the server

Dice, card shuffles and the outcome of a delivery are where cheating is most tempting, because one changed number can swing a whole match. That is why online results in our games are decided on our servers, not on the player's phone. The server rolls the dice or decides the ball and sends the same result to everyone at once.

There is a fairness benefit that goes beyond stopping cheats. Players stop wondering whether the other person's phone is rigged. We go deeper on this in why server-decided dice matter.

Latency: the delay you design around

Latency is the time a message takes to travel from a phone to the server and back. It is never zero, and on mobile networks it changes from moment to moment as people move between signals.

Good online games hide latency rather than pretending it is not there:

  • Show the intent at once. When you tap roll, the dice start tumbling straight away, while the real result travels back from the server.
  • Design turns with breathing room. Board and card games tolerate delay well because a short animation covers the round trip.
  • Keep messages small. Sending only what changed, not the whole match, keeps each update quick on weak connections.
  • Tell players when something is wrong. A clear reconnecting note is better than a frozen screen.

Checking every move

The server does not just pass messages along. It checks every action against the rules before it counts. A move that skips a square, a piece that is not yours, an action out of turn: all of these are rejected. Add player reports on top, and a team watching those reports in an admin dashboard, and you have the core of fair play. Our fair play policy explains how we handle it in our own games.

When a player drops out

On phones, connections drop all the time: a lift, a tunnel, a weak signal at home. A good online game treats this as normal. The server keeps the match going and holds the player's seat, so when the phone reconnects it rejoins the same match at the same turn.

If the player does not come back, the game still needs to finish for everyone else. In our games, Lumi AI, our computer opponent, can take the empty seat. You can read the full approach in handling disconnects in multiplayer games.

What it takes to build one

Here is the short list of parts a real online game needs, beyond the game itself.

Part What it does
Rooms and lobbies Let friends find each other with a short code
Matchmaking queue Pairs players who want a game now
Match server Holds the true state and decides luck
Move checking Rejects anything outside the rules
Reconnects Brings dropped players back into the same match
Seat filling Keeps matches complete when someone leaves
Admin dashboard Lets your team see matches, reports and settings

Each part is simple on its own. The work is in making them behave well together on real phones and real networks, which is why we built ours in-house and run it in our own live games first. If you want online play in your game, our multiplayer page shows what is included, and you can tell us about your game to plan rooms, matchmaking and fair play around it.

Frequently asked questions

Do all online games need a server?

Almost every fair online game does. A server holds one true version of the match and decides results, which stops players from tampering with outcomes on their own phones.

Why do online games sometimes lag?

Messages take time to travel between your phone and the server, and mobile signals change constantly. Good games hide most of that delay with instant animations and small, quick updates.

Can friends play together privately?

Yes. Most games offer private rooms: one player shares a short code and friends join from their own phones.

What happens if someone leaves an online match?

In a well-built game the server keeps their seat for a while so they can rejoin. In our games, if they do not return, Lumi AI can take over so the match still finishes.

  • #online multiplayer
  • #game servers
  • #mobile games
  • #game development
ShareinWAf

Written by

LacNova Team

The people who make, license and build games at LacNova Games: designers, artists, sound designers, developers and testers.

About the studio

Keep reading

All articles

Want this built for you?

Tell us about your players and your goal. We'll come back with a plan and a first playable.

A rocket launching from a phone: your game going live