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 C# for Game Development specialization: Track-specific focus: C# for Game Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Game Development.
Tools Unity or Unreal Engine profiler Version control
Hands-on exercise Create a small scene and trace update order for one interactive object. Context for this route: Track-specific focus: C# for Game Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Game Development.
Suggested project A playable prototype with clean scene and asset structure. The outcome must directly demonstrate C# for Game Development, 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 C# for Game Development.
Next: Gameplay logic & interaction
✓ Mark this node as complete
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 C# for Game Development specialization: Track-specific focus: C# for Game Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Game Development.
Tools C# or C++ Engine input system Physics tools
Hands-on exercise Build a movement and interaction loop with collision edge cases. Context for this route: Track-specific focus: C# for Game Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Game Development.
Suggested project A small gameplay mechanic with documented state transitions. The outcome must directly demonstrate C# for Game Development, not merely list tools.
Learning resources Completion criteria Input, physics and animation do not create invalid states. Evidence must be reproducible and tied to C# for Game Development.
Next: World building, assets & pipelines
✓ Mark this node as complete
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 C# for Game Development specialization: Track-specific focus: C# for Game Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Game Development.
Tools Engine editor DCC tool Asset pipeline
Hands-on exercise Build a small level and profile asset load and draw-call behaviour. Context for this route: Track-specific focus: C# for Game Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Game Development.
Suggested project A playable level with organised assets and performance notes. The outcome must directly demonstrate C# for Game Development, 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 C# for Game Development.
Next: Game systems & data architecture
✓ Mark this node as complete
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 C# for Game Development specialization: Track-specific focus: C# for Game Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Game Development.
Tools C# or C++ Save system Diagramming
Hands-on exercise Implement a persistent progression feature and test corrupted save data. Context for this route: Track-specific focus: C# for Game Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Game Development.
Suggested project A reusable gameplay system with safe save/load handling. The outcome must directly demonstrate C# for Game Development, 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 C# for Game Development.
Next: AI, animation & simulation
✓ Mark this node as complete
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 C# for Game Development specialization: Track-specific focus: C# for Game Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Game Development.
Tools Navigation system Animation graph Profiler
Hands-on exercise Create an NPC that reacts to several world states and recovers from blocked paths. Context for this route: Track-specific focus: C# for Game Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Game Development.
Suggested project A demonstrable NPC behaviour module. The outcome must directly demonstrate C# for Game Development, not merely list tools.
Learning resources Completion criteria Behaviour transitions are understandable and performance is measured. Evidence must be reproducible and tied to C# for Game Development.
Next: Performance, platform & quality
✓ Mark this node as complete
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 C# for Game Development specialization: Track-specific focus: C# for Game Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Game Development.
Tools Engine profiler GPU profiler Automated test scene
Hands-on exercise Capture a baseline and optimise one bottleneck with before/after evidence. Context for this route: Track-specific focus: C# for Game Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Game Development.
Suggested project A performance report and stable build target. The outcome must directly demonstrate C# for Game Development, 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 C# for Game Development.
Next: Build, release & live operations
✓ Mark this node as complete
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 C# for Game Development specialization: Track-specific focus: C# for Game Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Game Development.
Tools Engine build pipeline CI service Crash reporting
Hands-on exercise Create a signed test build and validate install/update behaviour. Context for this route: Track-specific focus: C# for Game Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Game Development.
Suggested project A release candidate with platform checklist and changelog. The outcome must directly demonstrate C# for Game Development, not merely list tools.
Learning resources Completion criteria Build artefacts are reproducible and platform constraints are addressed. Evidence must be reproducible and tied to C# for Game Development.
Next: Capstone: complete playable vertical slice
✓ Mark this node as complete
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 C# for Game Development specialization: Track-specific focus: C# for Game Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Game Development.
Tools Unity/Unreal Asset tools Issue tracker
Hands-on exercise Conduct a playtest, identify friction and implement one evidence-driven revision. Context for this route: Track-specific focus: C# for Game Development. Use the tools and standards named in this path; avoid treating this route as a generic overview of Game Development.
Suggested project A short playable vertical slice with documentation and performance evidence. The outcome must directly demonstrate C# for Game Development, 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 C# for Game Development.
End of roadmap: Complete the final project and build your portfolio.
✓ Mark this node as complete