Choosing the right networking architecture is an important decision when building a multiplayer game in Unity.
Two common approaches are client-server and peer-to-peer (P2P) networking. They organize communication and game authority differently, which can affect security, reliability, scalability, latency, and development complexity.
For board games and turn-based multiplayer experiences, understanding these differences helps developers design a network model that fits the game's rules and expected player experience.
- Client-Server Architecture
- How Client-Server Works
- Peer-to-Peer Architecture
- How P2P Works
- Client-Server vs P2P
- Game Authority
- Security Considerations
- Latency and Reliability
- Board Game Example
- Mobile Multiplayer Considerations
- Architecture Decision Factors
- Common Design Mistakes
- Related Documentation
In a client-server architecture, players connect to a central server that coordinates the multiplayer session.
A simplified structure looks like this:
Game Server
/ | \
/ | \
▼ ▼ ▼
Client 1 Client 2 Client 3