AXIOM-EMU Documentation
Configuration reference for every file shipped with an AXIOM-EMU server installation. Audience: server admins running compiled binaries + config templates.
Server Suite#
Four services make up the AXIOM-EMU server. Each ships with its own config files; each has a section here.
GameServerGame logic, per-server identity (6 .dat files)DataServerSQL Server persistence + Write-Ahead LogConnectServerServer list, client entry, UDP heartbeatsJoinServerAccount authentication + inter-server transfer
Optional Components#
Shared Game Content#
One folder shared by every GameServer instance: items, monsters, events, skills, plugins, shops, quests.
Two Config Roots for GameServer#
GameServer reads from two distinct locations:
| Location | Scope | Contents |
|---|---|---|
GameServer/Data/ | Per-server identity. One copy per running GameServer instance | The 6 GameServerInfo - *.dat files |
Data/ at release root | Shared game content. One copy per installation, read by every GameServer on it | Items, monsters, events, skills, plugins, shops, quests, messages |
Multi-server deployments get one GameServer/Data/ per instance (different ServerCode, ServerPort, LicenseKey) and share the single root-level Data/ folder.
Reading Order for New Admins#
- GameServer Overview - server topology, startup order, dependencies
- Common.dat - server identity, ports, rates, PK, guild rules (this is where most admin work happens)
- ConnectServer ServerList.xml - which servers appear to the client
- JoinServer Overview - account auth flow
- Data Overview - everything under the shared
Data/root - Section-specific pages as needed (items, monsters, events)
Key Concepts#
Getting Help#
- Check the specific page for Common Issues at the bottom
- Verify cross-file dependencies listed on each page
- Check the GameServer log for validation errors at startup
- Contact AXIOM-EMU support with the affected config section and log excerpt