Game Architecture

A solid foundation for building browser games without the usual architectural mess. Gives you the event-driven patterns, state management, and system organization you need to keep a game project from turning into spaghetti as it grows. The core loop first principle is especially good: get input, movement, fail state, and restart working before you touch particles or screen shake. Includes practical stuff like object pooling, delta time normalization, and a pre-ship checklist that catches common gotchas like forgetting cleanup on restart. Works for both Phaser 2D and Three.js 3D games. The orchestrator pattern and centralized constants approach will save you from scattered state and magic numbers everywhere.