gds-game-architecture

Start the workflow by describing your game concept and requirements. The Skill walks you through sequential decision steps covering engine, rendering, physics, networking, and persistence, then generates a complete architecture document with a decision summary table and implementation patterns.

The decision depends on your requirements: Unreal suits high-fidelity 3D and AAA pipelines, Unity fits cross-platform and mobile projects, and Godot works well for 2D games, open-source priorities, and web export. The Skill's decision catalog maps requirement triggers to recommended engines.

Yes, the decision catalog includes networking options such as Unity Netcode, Photon, Mirror, Unreal replication, Godot MultiplayerAPI, and custom UDP solutions. It distinguishes between competitive PvP, co-op, turn-based, and MMO-scale networking models with suggested stacks for each.

Godot cannot export to consoles directly because console SDKs are under NDA. You must contract a third-party porting company such as W4 Games, Lone Wolf Technology, or Pineapple Works, which adds cost and timeline considerations to your architecture decision.

MCP servers let AI assistants inspect and edit your game project directly, such as reading scenes or modifying scripts in Unity, Godot, Unreal, or Roblox Studio. They are optional but significantly improve AI-assisted development; the Skill recommends verified options per engine.

Avoid Phaser when you need 3D graphics, native mobile or desktop as the primary target, complex physics simulation, or CPU-intensive logic like large-scale pathfinding. Phaser is a 2D browser-first framework, and heavy computation hits JavaScript's single-threaded performance ceiling.