Prerequisites
Basic computer literacy and a willingness to document experiments.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- Scene, entity and component model
- Game loop and frame timing
- Input and asset pipeline
- Coordinate systems and transforms
- Unity specialization: Unity: focus on scenes, GameObjects/components, C# gameplay, physics, prefabs, profiling and build pipeline.
Tools
Unity or UnrealEngine profilerVersion control
Hands-on exercise
Create a small scene and trace update order for one interactive object. Context for this route: Unity: focus on scenes, GameObjects/components, C# gameplay, physics, prefabs, profiling and build pipeline.
Suggested project
A playable prototype with clean scene and asset structure. The outcome must directly demonstrate Unity, not merely list tools.
Learning resources
Completion criteria
The project opens from a clean checkout and behaves consistently. Evidence must be reproducible and tied to Unity.
Next: Gameplay logic & interaction
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- Input mapping and action systems
- Physics and collision basics
- Finite-state machines
- Animation state and feedback
- Unity specialization: Unity: focus on scenes, GameObjects/components, C# gameplay, physics, prefabs, profiling and build pipeline.
Tools
C# or C++Engine input systemPhysics tools
Hands-on exercise
Build a movement and interaction loop with collision edge cases. Context for this route: Unity: focus on scenes, GameObjects/components, C# gameplay, physics, prefabs, profiling and build pipeline.
Suggested project
A small gameplay mechanic with documented state transitions. The outcome must directly demonstrate Unity, not merely list tools.
Learning resources
Completion criteria
Input, physics and animation do not create invalid states. Evidence must be reproducible and tied to Unity.
Next: World building, assets & pipelines
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- Scene composition and prefabs/blueprints
- Materials, lighting and import settings
- Asset naming and source control
- Level streaming basics
- Unity specialization: Unity: focus on scenes, GameObjects/components, C# gameplay, physics, prefabs, profiling and build pipeline.
Tools
Engine editorDCC toolAsset pipeline
Hands-on exercise
Build a small level and profile asset load and draw-call behaviour. Context for this route: Unity: focus on scenes, GameObjects/components, C# gameplay, physics, prefabs, profiling and build pipeline.
Suggested project
A playable level with organised assets and performance notes. The outcome must directly demonstrate Unity, not merely list tools.
Learning resources
Completion criteria
Assets are traceable and the level loads within a stated budget. Evidence must be reproducible and tied to Unity.
Next: Game systems & data architecture
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- Inventory or quest system
- Save/load and schema versioning
- Events and decoupled systems
- UI/gameplay state boundaries
- Unity specialization: Unity: focus on scenes, GameObjects/components, C# gameplay, physics, prefabs, profiling and build pipeline.
Tools
C# or C++Save systemDiagramming
Hands-on exercise
Implement a persistent progression feature and test corrupted save data. Context for this route: Unity: focus on scenes, GameObjects/components, C# gameplay, physics, prefabs, profiling and build pipeline.
Suggested project
A reusable gameplay system with safe save/load handling. The outcome must directly demonstrate Unity, not merely list tools.
Learning resources
Completion criteria
The system restores valid state and degrades safely on invalid save data. Evidence must be reproducible and tied to Unity.
Next: AI, animation & simulation
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- Navigation and pathfinding
- Behaviour trees or state machines
- Animation blending and events
- Deterministic simulation trade-offs
- Unity specialization: Unity: focus on scenes, GameObjects/components, C# gameplay, physics, prefabs, profiling and build pipeline.
Tools
Navigation systemAnimation graphProfiler
Hands-on exercise
Create an NPC that reacts to several world states and recovers from blocked paths. Context for this route: Unity: focus on scenes, GameObjects/components, C# gameplay, physics, prefabs, profiling and build pipeline.
Suggested project
A demonstrable NPC behaviour module. The outcome must directly demonstrate Unity, not merely list tools.
Learning resources
Completion criteria
Behaviour transitions are understandable and performance is measured. Evidence must be reproducible and tied to Unity.
Next: Performance, platform & quality
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- Frame-time budgets
- Rendering and batching
- Memory, object pooling and streaming
- Input latency and platform compatibility
- Unity specialization: Unity: focus on scenes, GameObjects/components, C# gameplay, physics, prefabs, profiling and build pipeline.
Tools
Engine profilerGPU profilerAutomated test scene
Hands-on exercise
Capture a baseline and optimise one bottleneck with before/after evidence. Context for this route: Unity: focus on scenes, GameObjects/components, C# gameplay, physics, prefabs, profiling and build pipeline.
Suggested project
A performance report and stable build target. The outcome must directly demonstrate Unity, not merely list tools.
Learning resources
Completion criteria
Frame-time goals are stated and verified on the target hardware. Evidence must be reproducible and tied to Unity.
Next: Build, release & live operations
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- Build configurations and signing
- Platform input and store checks
- Crash logs and telemetry
- Patch and rollback strategy
- Unity specialization: Unity: focus on scenes, GameObjects/components, C# gameplay, physics, prefabs, profiling and build pipeline.
Tools
Engine build pipelineCI serviceCrash reporting
Hands-on exercise
Create a signed test build and validate install/update behaviour. Context for this route: Unity: focus on scenes, GameObjects/components, C# gameplay, physics, prefabs, profiling and build pipeline.
Suggested project
A release candidate with platform checklist and changelog. The outcome must directly demonstrate Unity, not merely list tools.
Learning resources
Completion criteria
Build artefacts are reproducible and platform constraints are addressed. Evidence must be reproducible and tied to Unity.
Next: Capstone: complete playable vertical slice
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- Design scope and player objective
- Gameplay systems and content pipeline
- Performance and release QA
- Portfolio capture and postmortem
- Unity specialization: Unity: focus on scenes, GameObjects/components, C# gameplay, physics, prefabs, profiling and build pipeline.
Tools
Unity/UnrealAsset toolsIssue tracker
Hands-on exercise
Conduct a playtest, identify friction and implement one evidence-driven revision. Context for this route: Unity: focus on scenes, GameObjects/components, C# gameplay, physics, prefabs, profiling and build pipeline.
Suggested project
A short playable vertical slice with documentation and performance evidence. The outcome must directly demonstrate Unity, not merely list tools.
Learning resources
Completion criteria
A reviewer can play the build and understand your design decisions. Evidence must be reproducible and tied to Unity.
End of roadmap: Complete the final project and build your portfolio.