Skip to content

36. Common Names in Multiplayer Game Servers ​

This document explains names used by other game server projects and the responsibilities they carry. “Similar” means overlapping responsibilities, not equivalent implementations. See Concepts and Names for Apollo's target terms and Architecture Overview for its target topology.

Project terminology ​

KBEngine ​

NameResponsibility
loginappLogin entry and authentication-flow coordination.
baseappBase entities and client proxies; hosts non-spatial entities.
cellappEntities and spatial logic inside a Space.
baseappmgrBaseApp selection, load information, and login allocation.
cellappmgrCellApp selection and Space/Cell creation and recovery coordination.
dbmgrDatabase access and entity-persistence coordination.
machineMachine discovery and process-management support.

Base/Cell belong to KBEngine's entity/spatial model. Apollo keeps profiles in Base, executor management in worldServer, and simulation in cell. Reuse Space/Cell semantics, initially one Cell per Space, reserving future seamless capabilities.

BigWorld ​

NameResponsibility
loginappLogin entry.
baseappBase entities, client proxies, and non-spatial player state.
cellappCell entities and Space simulation.
baseappmgrBaseApp allocation and load management.
cellappmgrCellApp/Space management and recovery coordination.
dbapp / dbappmgrDatabase task processing and management.
bwmachinedMachine discovery, monitoring, and process-management support.

BigWorld's Cell/ghost mechanisms support continuous space across Cells; see the Apollo mapping for management/execution/spatial correspondence, without claiming full implementation.

TrinityCore / AzerothCore ​

NameResponsibility
authserverAccount authentication and Realm entry.
worldserverRealm runtime, including player connections and much of the game-world logic.

These names describe public open-source implementations and do not establish the internal topology of commercial MMOs.

EQEmu ​

NameResponsibility
loginserverLogin service.
worldWorld-level coordination and client/Zone connection management.
zoneRuns a game area and its related gameplay.
ucsStandalone communication service.

zone is EQEmu's name for its area runtime; it is not an Apollo process name.

Pomelo / LordOfPomelo ​

NameResponsibility
gateInitial ingress and Connector selection.
connectorMaintains client connections and sessions and forwards messages.
areaEntities and game logic for a map area.
masterConfigures and manages service processes.

Pomelo's gate and connector are separate roles. connector is closer to the common client-Gateway responsibility.

Ryzom Core ​

NameResponsibility
FES (Front End Service)Client ingress and message front end.
EGS (Entities Game Service)Entities and core game logic.
AIS (AI Service)AI logic.
MS (Mirror Service)Inter-service entity data mirroring.
NS (Naming Service)Service discovery/naming.
AES (Administration Executor Service)Service start/stop and administration.

These abbreviations belong to Ryzom's service layout and should not be copied into Apollo as extra concepts.

Skynet ​

Skynet is a general service runtime and does not prescribe an MMO process topology. Its Gate example handles client connections and message forwarding; names such as Agent and Watchdog come from example service arrangements, with exact roles defined by the application.

Colyseus and Photon ​

Colyseus uses the actual Room type for a stateful client group; see official Rooms documentation. Photon Master Server and Game Server are service roles. External session names do not change Apollo Instance terminology.

Agones ​

Agones uses GameServer, Fleet, and FleetAutoscaler for game-server instances and orchestration resources on Kubernetes. It addresses deployment and capacity orchestration; it does not define the business model for player objects or instances.

Apollo names ​

Target nameResponsibilityExternal responsibility reference
loginServerAuthentication, credentials, directoriesloginapp/authserver authentication boundaries
gatewayClient connections and forwardingPomelo connector, Ryzom FES, Skynet Gate
baseServerPersistent-player objects and base gameplayNon-spatial BaseApp behavior; not a database process
worldServerExecutor registration, Space/Cell placement and topologyRelevant CellAppMgr management duties
cell executorPartition simulation, entities, AOI and ticksCellApp; one process may host several Cells
databaseProfile loading/saving and storage accessdbmgr/dbapp storage responsibilities
machinedLocal process lifecycle/supervisionLocal process management, not player ownership
Space (existing Scene semantics) / Cell / InstanceRuntime space / partition / temporary gameplayReuse BigWorld Space/Cell; Instance is Apollo gameplay

Cross-server play retains Base/storage affiliation; cell associates each player with its Base. See concepts. Similar responsibilities do not imply identical engine topologies.

Gateway and updates ​

Gateway is a common ingress responsibility, not a guarantee of zero-downtime updates. Multiple Gateways can accept new players after an old instance stops receiving new connections. Existing TCP connections require connection handoff or the old instance retaining them until drained. Keeping active instances running across versions additionally requires instance-state transfer, version compatibility, authority handoff, route switching, and rollback. These mechanisms must be verified separately.

Sources ​

Released under the MIT License