Cubic Games / Pixel Gun 2
Whole-game client/server lifecycle
Owned core architecture for a voxel multiplayer FPS.
- Defined initialization, metagame, core gameplay, transitions, reloads, reconnects, and shutdown.
- Structured services and DI around GameContexts.
- Separated maps from game modes and established explicit server, client, and shared-simulation responsibilities.
- Created ECS/NetCode-ready boundaries incrementally, while educating the team in ECS-oriented thinking and avoiding a project-wide rewrite.