game-development

Game architecture is structured by selecting between state machines, ECS, observers, commands, and behavior trees based on your specific complexity and goals. This ensures a robust core design while establishing universal subsystem principles for the complete workflow.

A game loop is best implemented using the INPUT → UPDATE → RENDER pattern with a fixed timestep. This separates gameplay logic from visual rendering, ensuring consistent physics and behavior regardless of fluctuating frame rates.

Performance budgeting targets a specific frame rate like 60 FPS and prioritizes optimization to prevent slowdowns. You must follow universal anti-patterns to avoid fragile designs and ensure the game runs within the defined limits.

Specialized guidance for web, mobile, PC, and VR/AR platforms is provided through context-based routing. The system directs you to platform-specific sub-skills for 2D, 3D, design, art, audio, and multiplayer scenarios.

Action-based input abstraction is needed to decouple physical controls from gameplay commands across different platforms. It ensures your game logic remains consistent whether the player uses a keyboard, touchscreen, or VR controllers.

Yes, this approach works for both 2D and 3D projects by applying universal core architecture principles and routing to domain-specific sub-skills. It ensures the foundational systems are solid before targeting the specific rendering needs of 2D or 3D.