Skip to content

Architecture Overview ​

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

Keep gateway, loginServer, baseServer, worldServer, database, and machined. Use the discussed cell executor: worldServer overlaps CellAppMgr management and cell overlaps CellApp execution. Base owns persistent objects and saves through database.

Space corresponds to existing Scene spatial semantics, Cell is a partition, and Instance is a temporary gameplay lifecycle. Initially one executor and one Cell per Space; reserve multiple Cells per Space. Seamless splitting, Ghosts, and cross-boundary combat remain unimplemented.

Executors register with World, which manages topology/migration. loginServer hosts service/online location projections; gateway forwards directly to Base/cell. machined supervises locally and is optional beside independently deployed World/cell. Cross-server play retains home Base/storage affiliation without moving complete profiles.

Protocol replacement separately transfers Base objects, cell simulation, and World management state before switching authority/routes. Code-only updates preserve wire and may update Lua; C++ uses replacement processes. Validate TCP, sessions, and complete activity continuity separately.

Temporary instance lifecycle ​

Group request → Base validation → World Space/Cell placement → cell creates/runs Instance → original Base/database durable settlement → departure/cleanup. Reuse eight states; persistent Spaces need no temporary Instance.

Reading ​

Preserve external-engine source names without treating them as another Apollo topology.

Released under the MIT License