Develop PC/Console Games with Expert Guidance

This is a PC/console game-development skill covering engine selection and platform-specific principles across Unity 6, Godot 4, and Unreal 5. It starts with a decision tree scoped by project type - 2D games route to Godot (if open source matters) or Unity (for larger teams and assets); 3D games route to Unreal (AAA visual quality), Unity (cross-platform priority), or Godot 4 (indie/open source); and specific technical needs route directly - DOTS performance to Unity, Nanite/Lumen to Unreal, lightweight projects to Godot:

What are you building?
│
├── 2D Game
│   ├── Open source important? → Godot
│   └── Large team/assets? → Unity
│
├── 3D Game
│   ├── AAA visual quality? → Unreal
│   ├── Cross-platform priority? → Unity
│   └── Indie/open source? → Godot 4
│
└── Specific Needs
    ├── DOTS performance? → Unity
    ├── Nanite/Lumen? → Unreal
    └── Lightweight? → Godot

A comparison table backs the decision tree: Unity 6 scores good on both 2D and 3D with a medium learning curve and revenue-share cost; Godot 4 is rated excellent for 2D, free, and easy to learn but best suited to solo-to-medium teams; Unreal 5 is excellent for 3D, hardest to learn, and free until $1M revenue (5% share after).

Use this skill when selecting a game engine, integrating Steam platform features (achievements, cloud saves, leaderboards, workshop mods, rich presence), meeting console certification requirements (PlayStation's TRC compliance, Xbox's XR compliance, Nintendo's Lotcheck), designing controller input, or optimizing performance. It explicitly recommends abstracting controller input to named actions like "confirm" and "cancel" rather than hardcoding specific buttons, since the same action maps to different buttons across Xbox, PlayStation, and Nintendo controllers, and names concrete anti-patterns to avoid: choosing an engine by hype rather than project needs, ignoring platform certification guidelines, hardcoding input buttons, and skipping profiling.

Input is a game project's requirements - 2D or 3D, target platforms, team size, performance needs; output is an engine choice backed by the decision tree and comparison table, platform-integration requirements (Steam features, console certification), an input-abstraction scheme mapping actions to controller buttons per platform, and a performance-optimization plan matched to the chosen engine's profiler (Unity's Profiler Window, Godot's Debugger/Profiler, Unreal Insights) and common bottleneck fixes - batching and atlases for draw calls, object pooling for GC spikes, simpler colliders for physics, LOD shaders for shader cost.

Game developers choosing between Unity, Godot, and Unreal, or implementing platform integration, controller support, and performance optimization for PC or console, who want engine-agnostic decision criteria and a concrete anti-pattern checklist rather than picking an engine by hype.