Skip to content

ApolloLightweight Instance-Based Multiplayer Game Server Engine

A C++20 runtime for tower defense, co-op, arenas, and dungeons. MMO is a possible product form; instances come first, with seamless-map design reserved.

Apollo

Target architecture ​

Business traffic goes directly through gateway to the owning Base or current cell. world manages placement and topology. Solid lines show business traffic; dashed lines show registration and management.

Apollo process architecture: world is the manager (register/topology/capacity/migration) and cellServer the standalone simulation executor (Scene/Avatar/AOI/battle/Lua), coordinated over 960 register/961 verdict/962 assign/963 retire/967 self-report; Base owns player profiles and base gameplay persisted via database; gateway routes directly to Base and cell; interfaces receives platform callbacks; machined spawns and supervises; logger/admin collect logs and metrics.Apollo process architecture: world is the manager (register/topology/capacity/migration) and cellServer the standalone simulation executor (Scene/Avatar/AOI/battle/Lua), coordinated over 960 register/961 verdict/962 assign/963 retire/967 self-report; Base owns player profiles and base gameplay persisted via database; gateway routes directly to Base and cell; interfaces receives platform callbacks; machined spawns and supervises; logger/admin collect logs and metrics.
Target design. Implementation status is documented separately.Open full-size diagram

External HTTP Callbacks and Developer Entry Points ​

Optional interfaces receives payment/channel callbacks over HTTP/HTTPS. Durable intake precedes asynchronous delivery to the current Base, resolved by stable player identity. Base validates and fulfills through database. Gameplay WS/WSS belongs to the gateway game-message path — TCP/WS/WSS share one accepted path — and never enters the HTTP handler.

External callbacks and fulfillment: the interfaces intake chain, epoch-based current-Base resolution, and idempotent fulfillment modules are implemented; channel verification and inter-process wiring remain planned; the apolloc init scaffolding is delivered and CI runs in the repository.External callbacks and fulfillment: the interfaces intake chain, epoch-based current-Base resolution, and idempotent fulfillment modules are implemented; channel verification and inter-process wiring remain planned; the apolloc init scaffolding is delivered and CI runs in the repository.
Target design. Implementation status is documented separately.Open full-size diagram

Implementation status: the gateway game TCP/WS/WSS entries are accepted (including WSS certificate-chain/hostname rejection and key-configuration negatives); the interfaces intake chain (byte-exact raw-request retention, request-timeout and queue budgets, bounded single-writer), the order transaction domain (durable intake and pending work, epoch-based current-Base resolution, atomic fulfillment dedup credentials), and the apolloc init scaffolding are implemented with test coverage; the channel verification executor and inter-process wiring (interfaces→order intake, base write-authority lifecycle, reward apply executor) remain planned. See the Mistlane/FOGS review; root todo.md tracks implementation.

Processes, Tools, and CI ​

  • Runtime processes: gateway, login, base, world, database, interfaces, machined; cell runs as a role of the world binary. gateway serves the game TCP/WS/WSS entries (accepted); interfaces serves the HTTP/HTTPS callback entry (intake chain implemented).
  • CLI tools: apolloc (project init, delivered), fleetctl (fleet drill assertions), admin and logger (observability helpers) — developer tools, not online services.
  • CI: GitHub Actions (build/tests, contracts, docs) runs in the repository, outside the online path.

Positioning ​

Apollo is a lightweight instance-based multiplayer game server engine for tower defense, co-op PvE/PvP, arenas, and dungeons. MMO describes a possible product scale or form, not the server architecture. Seamless maps are deferred, with multiple Cells per Space, neighboring visibility, and authority handoff reserved.

The target-role model routes client base gameplay and simulation separately through gateway. Base loads/saves through database, login hosts authentication/directories, and machined optionally supervises local processes. Scene transfer retains Base/storage affiliation.

Documentation ​

TopicDocument
Target architectureArchitecture Overview
Target names and boundariesConcepts and Names
Current executable prototypesServer Applications
World and cross-server transferInstance-Based GameServer Design
Building the codeBuild Guide
BigWorld–Apollo correspondenceRoles, concepts, and code mapping
External engine comparisonsMMO Framework Comparison

External BaseApp/CellApp names retain their real meanings. Apollo uses base for persistent-player gameplay and world for Space/Cell management and cell for simulation; see the target-role glossary.

Released under the MIT License