How It Fits Together: Difference between revisions
From OuroDev
(Lots of investigation necessary.) |
m (Try not to confuse people coming in from "Server Arch", and link to "Client Arch" for when that exists.) |
||
| Line 1: | Line 1: | ||
== Server Architecture == | |||
An attempt to explain the purpose of each part, and how they all fit together. | An attempt to explain the purpose of each part, and how they all fit together. | ||
| Line 35: | Line 37: | ||
The Game Client also connects directly to ????TODO??? during play. | The Game Client also connects directly to ????TODO??? during play. | ||
For more info about the Game Client, see [[Client Architecture]]. | |||
== Server's POV == | == Server's POV == | ||
??? TODO ??? | ??? TODO ??? | ||
Revision as of 13:53, 23 May 2019
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
- game
- 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:
- Run Launcher. This is being replaced by things like Cream Soda.
- Launcher runs Game Client.
- Game Client connects to Auth Server, receives auth token of some sort.
- Game Client connects to DB Server, which is the actual "Shard".
The Game Client also connects directly to ????TODO??? during play.
For more info about the Game Client, see Client Architecture.
Server's POV
??? TODO ???