How It Fits Together

Server Architecture

An attempt to explain the purpose of each part, and how they all fit together.

Components

Based on the source directories, it seems like a full CoX system (that is, all servers, and the game client) is made up of these items:

• accountserver
• arenaserver
• auctionserver
• authserver
• chatserver - chatadmin, chatclient
• cmdrelay
• dbserver - DB Server is the actual "shard" (and does surprisingly little database work).
• game - Game Client
• launcher - Launch (and update) the game client.
• mapserver
• missionserver
• queueserver
• raidserver
• statserver
• turnstileserver

Note: I'm probably slightly off, and will update this as I investigate further. Feel free to correct any lies in here!

Player's POV

From the player's point of view:

1. Run Launcher. This is being replaced by things like Cream Soda.
2. Launcher runs Game Client.
3. Game Client connects to AuthServer, receives auth token of some sort. AuthServer sends the token and some related data to dbserver.
4. Game Client connects to dbserver, which is the actual "Shard".
5. Game Client sends login message to dbserver, and receives a lot of data in return.
6. Game Client shows player selection screen
7. Game Client sends choose player message to dbserver, which begins the process of loading the character onto a MapServer.
8. When MapServer has finished loading the character, dbserver sends |map connect message to game client. This contains an IP address, udp port, and login cookie for the client to connect to the MapServer.
9. Game Client directly connects to MapServer, as instructed. Most communication will be with the MapServer from now on, until the next time the player changes maps and needs to do a map transfer.

The Game Client also connects directly to ????TODO??? during play.

For more info about the Game Client, see Client Architecture.

Server's POV

??? TODO ???

See Dbserver-protocols for info about how the DB Server talks to things.