Understanding how players connect across networks
Playing games with friends across platforms is more accessible than ever, but multiplayer networking remains prone to confusion. A player might expect to carry unlocks from console to PC, only to discover crossplay does not include cross-progression. Another might encounter sudden connection drops or teleporting opponents despite having fast broadband.
Understanding server architectures, cross-network features, and netcode principles clarifies why multiplayer sessions behave the way they do and how to troubleshoot connection issues effectively.
Crossplay, cross-progression, and cross-commerce
While often grouped together under cross-platform support, these three capabilities are technically and commercially distinct:
- Crossplay (Cross-platform multiplayer): The ability for players on different hardware ecosystems (such as PC, PlayStation, Xbox, and Nintendo Switch) to enter the same game session simultaneously. It requires unified networking protocols and often uses publisher-level accounts to bridge platform-specific friend lists.
- Cross-progression (Cross-save): The ability to carry your rank, campaign unlocks, inventory, and stats across different devices. This requires storing progression data on central publisher servers rather than relying on local machine or platform-exclusive cloud saves.
- Cross-commerce (Shared purchases): The sharing of purchased premium currencies and cosmetics across platforms. Because storefronts retain transaction fees, platform holders frequently restrict premium currency spending to the specific ecosystem where it was bought, even if cosmetics unlocked with that currency carry over.
When browsing multiplayer titles on platforms like 365Finds, confirm whether 'multiplayer' refers to online matchmaking, local split-screen, or opt-in peer-to-peer lobbies before buying.
Dedicated servers versus peer-to-peer (P2P) hosting
How a multiplayer match is hosted dictates stability, fairness, and long-term viability:
- Dedicated servers: An independent machine hosted in a data center acts as the authoritative arbitrator for the match. Every player sends input to this server, which calculates world physics, hit detection, and player positions before broadcasting the verified state back.
- Advantages: Consistent latency, immunity to host-disconnection crashes, and stronger anti-cheat enforcement.
- Trade-off: When publisher servers are retired, matchmaking ceases unless community-hosted server binaries are provided.
- Peer-to-peer (P2P) hosting: One player's computer or console is chosen as the "host," running both their local game and the simulation for all connected peers.
- Advantages: Lower operational cost for developers and the potential for direct LAN or private IP connections.
- Trade-off: The host player enjoys a latency advantage ("host advantage"), and if the host quits or experiences network packet loss, the entire lobby experiences lag spikes or host-migration pauses.
Server tickrates and update frequency
The responsiveness of a dedicated server depends heavily on its tickrate—the frequency at which the server updates game logic per second, measured in Hertz (Hz):
- 30 Hz: The server processes the world state once every 33.3 milliseconds. Common in large-scale battle royales or vehicular games with dozens of participants.
- 60 Hz: Updates occur every 16.6 milliseconds. The standard baseline for modern competitive first-person and tactical shooters.
- 128 Hz: Updates occur every 7.8 milliseconds. Reserved for tournament-tier competitive play, offering immediate hit registration at the cost of higher server compute load.
If your local frame rate is 144 FPS but the server updates at 30 Hz, animations may appear smooth locally, but weapon impact confirmations and enemy positions update at the slower server rate.
Netcode: Delay-based versus rollback
When latency (ping) introduces delays between players, the game's network code ("netcode") determines how those gaps are handled:
- Delay-based netcode: The game artificially delays your button inputs until they can be transmitted to the opponent or server and synchronized. As ping increases, controls feel sluggish and unresponsive.
- Rollback netcode: The game executes your inputs immediately on your local screen without waiting. If the server or remote player's confirmed input differs from what was predicted, the game engine rolls back to the discrepancy point and resimulates the outcome in a fraction of a millisecond. This ensures responsive controls even under moderate latency.
Diagnosing connection problems
To minimize lag and connection drops during multiplayer sessions:
- Prefer wired Ethernet over Wi-Fi: Even high-speed Wi-Fi is susceptible to radio interference and momentary packet retransmission bursts that manifest as stutter.
- Check your NAT type: An "Open" or "Moderate" NAT allows connections to most player pools. A "Strict" NAT blocks peer connections in P2P games and prevents hosting lobbies.
- Select geographically proximate server regions: Choosing server regions closest to your physical location minimizes raw ping times and packet routing hops.