Inside a Classic MMORPG Server Architecture: How Six Connections Power Gameplay

This diagram shows a typical zone architecture used in many MMORPGs, where each zone contains identical server groups, with multiple servers (xN) and connections indicated by red, green, and blue lines.

Connection 1 : A WebService pipeline used to insert or update user account information when a zone account is activated or its password changed.

Connection 2 : Another WebService pipeline for retrieving and controlling the user's role information within the group and handling updates such as marketplace token transactions.

Connection 3 : A local TCP/IP connection for server group registration with the login server, account verification, and operations on logged‑in accounts (e.g., kicking a player) as well as updating group data like online player count.

Connection 4 : A local TCP/IP connection that validates clients connecting to the GameServer and exchanges character data.

Connection 5 : A local TCP/IP connection facilitating communication between the public information server and multiple game servers to exchange world‑level data such as guilds, cross‑server parties, and chat channels.

Connection 6 : Shows that UserServer and GameServer agents can be interchangeable, allowing a player to stay within the same agent throughout the session, reducing connection hops and improving stability.

In this architecture, the GameServer is a composite of game‑logic components that can be further split into separate logic servers, while the PublicServer handles shared data exchange.

The UserServer acts as the leader of a ServerGroup, registering and updating group information with the LoginServer, dispatching agents to provide the least‑loaded entry point, managing roles (creation, deletion, selection), and verifying client legitimacy for the GameServer.

Games built with this structure typically exhibit the following behavior:

Users must activate a zone before logging in.

A launcher appears on client start, prompting zone selection.

After launching the main client, users enter their account credentials.

Upon successful verification, the appropriate zone server is chosen.

After server selection, players manage characters, which are not shared across servers.

This classic, well‑tested architecture is simple yet clear, making it a solid choice for MMORPGs and other online games.