A game development roadmap for 2026 built around finishing games - programming basics, choosing Unity, Unreal or Godot, game maths and physics, design, audio, optimisation and publishing.
8 stages
12-18 months part time
Engine flexible
Realistic timeline
12-18 months at 10-15 hours per week
Stages
8 in order
Starting point
No coding needed to start
Game developers turn ideas into interactive experiences. Depending on the team, that can mean programming gameplay, building tools, writing shaders, optimising performance or designing systems. In small studios and solo projects, it often means all of those at once.
This game developer roadmap is built around one principle: finish small games. Every stage ends with something playable, because completed games teach scope, polish and debugging in a way that endless prototypes never do. General programming habits from the software developer roadmap will help at every step.
Overview
Game development roadmap at a glance
Eight stages, each ending in something you can actually play.
Select a stage to see what it covers. Filter by level to focus.
1. Programming basics for games
6-8 weeks
Write simple programs and understand how a game loop works.
Variables, conditions, loops and functions
Classes and objects
Collections: arrays, lists and dictionaries
The game loop: input, update, render
Frame time and delta time
Git for game projects
Done when: A text or simple 2D game with a working loop, win condition and restart.
Keep every project small enough to finish. Scope is the skill most beginners underestimate.
1
Foundation · Beginner
Programming basics for games
6-8 weeks
Write simple programs and understand how a game loop works.
Choose the language of the engine you are leaning toward: C# for Unity, GDScript or C# for Godot, C++ for Unreal (with Blueprints as a visual starting point). Learn variables, conditions, loops, functions and classes, then the idea at the heart of every game: the loop that reads input, updates the world and draws a frame, many times per second.
Skills
Variables, conditions, loops and functions
Classes and objects
Collections: arrays, lists and dictionaries
The game loop: input, update, render
Frame time and delta time
Git for game projects
Milestone
A text or simple 2D game with a working loop, win condition and restart.
Project ideas
Pong or Snake in a simple framework
A text adventure with branching choices
2
Tools · Beginner
Learn one game engine
8-10 weeks
Build and export a complete small 2D game in your chosen engine.
Unity is widely used for mobile, indie and cross-platform games. Unreal Engine leads in high-fidelity 3D and is common in larger studios. Godot is free, open source and lightweight, and popular with indie developers. Pick one and learn its editor, scene structure, scripting model, physics components, animation and UI system. Resist switching engines when things get hard.
Skills
Editor, scenes and the object hierarchy
Scripts, components and lifecycle events
Sprites, tilemaps and animation
Colliders, rigidbodies and triggers
UI: menus, HUD and pause screens
Building and exporting for a platform
Milestone
A finished 2D game with a menu, three levels and a build someone else can play.
Project ideas
A 2D platformer
A top-down arena shooter
3
Core skills · Intermediate
Game maths and physics
6-8 weeks
Use vectors and transforms confidently to control movement, aiming and cameras.
Game programming is applied maths. Learn vectors (position, direction, velocity), normalisation, dot and cross products, trigonometry for angles, and interpolation for smooth motion. Understand transforms and coordinate spaces, quaternions at a practical level, and how physics engines handle collisions. This knowledge makes the difference between fighting the engine and directing it.
Skills
Vectors, normalisation, dot and cross products
Trigonometry for rotation and aiming
Lerp, easing and smoothing
Transforms and local versus world space
Quaternions in practice
Collision detection and physics settings
Milestone
A third-person or top-down controller with smooth camera follow and correct aiming.
Project ideas
A physics puzzle game
A homing projectile and enemy vision cone demo
4
Core skills · Intermediate
Game design and game feel
5-6 weeks
Make games that are satisfying to play, not just technically working.
Developers who understand design build better games. Learn core loops, feedback, difficulty curves and player motivation. Study game feel: responsive controls, screen shake, particles, sound cues and animation timing. Playtest with other people early and watch silently - their confusion is your best data.
Skills
Core loops and player goals
Difficulty curves and level pacing
Juice: feedback, particles and screen shake
Audio integration and mixing basics
Playtesting and iterating on feedback
Scoping a game to fit your time
Milestone
Run a playtest with at least five people and ship an update based on what you saw.
Project ideas
Polish an earlier game with a "juice" pass and compare before and after
5
Frameworks · Intermediate
3D development and core systems
8-10 weeks
Build a small 3D game with the systems real games depend on.
Move into 3D: models, materials, lighting and cameras. Then build the systems that show up in most games - state machines for characters and AI, inventory, save and load, dialogue or quest data, and simple enemy behaviour with navigation meshes. Keep art simple by using free, properly licensed assets.
Skills
3D scenes, materials and lighting
Character controllers and animation state machines
Finite state machines and behaviour trees
Pathfinding and navigation meshes
Saving and loading game state
Data-driven design with configuration files
Milestone
A small 3D game with enemy AI, saving and at least one data-driven system.
Project ideas
A 3D collect-and-escape game
A small dungeon crawler
6
Advanced topics · Advanced
Performance, graphics and specialisation
8-12 weeks
Make games run well and choose an area to specialise in.
Learn to profile CPU, GPU and memory, reduce draw calls, pool objects and manage garbage collection. Then explore a specialisation: shaders and graphics programming, multiplayer networking, gameplay systems, tools programming, or mobile optimisation. Each is a deep field with its own career path.
Skills
Profiling CPU, GPU and memory
Object pooling and batching
Shaders and shader graphs
Multiplayer basics: authority, latency and prediction
Editor tools and pipeline scripts
Platform constraints for mobile and consoles
Milestone
Profile a game, fix the top three bottlenecks and document the frame-time improvement.
Project ideas
A two-player online game
A custom shader effects showcase
7
Portfolio · Advanced
Ship and publish a game
8-12 weeks
Release a polished game publicly and learn from real players.
Publishing teaches lessons nothing else does: builds for multiple platforms, store pages, settings menus, bug reports and player reviews. Start with free platforms like itch.io, or game jams, which are an excellent way to finish something under a deadline. Consider a paid storefront only once you have shipped smaller titles.
Skills
Release builds and platform settings
Store pages, screenshots and trailers
Settings, accessibility and controller support
Bug tracking and patching
Game jams and working to deadlines
Reading and responding to player feedback
Milestone
A publicly released game with a store page and at least one post-launch update.
Project ideas
Enter a 48-hour game jam
Publish a polished game on itch.io
8
Job ready · Advanced
Portfolio and studio interviews
4-6 weeks
Show studios playable, well-explained work in your specialisation.
Studios want to play your games and read your code. Build a portfolio site with playable builds, short videos and breakdowns of the systems you wrote. Prepare for programming tests, maths questions and discussions of your technical decisions.
Skills
Portfolio site with playable builds
Technical breakdowns and devlogs
Programming tests in C# or C++
Game maths interview questions
Collaborating with artists and designers
Milestone
A portfolio with three playable games and a written breakdown for each.
Project ideas
A devlog series documenting one project
Progression
Game developer skills by level
What each level looks like in practice, so you know where you stand.
Beginner
Months 0-4
You can program simple games and finish a small 2D project in one engine.
Focus on
Programming basics
Game loop
One engine
Sprites and physics components
You can: Finish and share a small 2D game.
Intermediate
Months 4-10
You use game maths confidently and build satisfying 3D games with real systems.
Focus on
Vectors and transforms
Game feel
3D and animation
State machines and AI
You can: Build a polished small 3D game.
Advanced
Months 10-18+
You optimise, specialise and ship games to real players.
Focus on
Profiling
Shaders or networking
Publishing
Portfolio breakdowns
You can: Release a game and specialise.
Technologies
Game development tools and technologies
Dark chips are worth learning early. Light chips can wait until a project needs them.
Game engines
Pick one and stay with it for at least a year.
Start with
Unity
Godot
Unreal Engine
Add later or when needed
A second engine
Custom engine experiments
Languages
Determined largely by your engine.
Start with
C# (Unity, Godot)
GDScript (Godot)
C++ (Unreal)
Add later or when needed
Blueprints
HLSL or GLSL
Lua
Art and audio tools
Enough to make placeholder and simple assets.
Start with
Aseprite or Krita
Blender basics
Add later or when needed
Audacity
FMOD or Wwise
Substance tools
Maths and physics
Applied every day in gameplay code.
Start with
Vectors
Trigonometry
Interpolation
Add later or when needed
Quaternions
Matrices
Physics integration
Workflow
Keeps projects safe and organised.
Start with
Git with LFS
A task board
Add later or when needed
Perforce
Build automation
Publishing
Where your games meet players.
Start with
itch.io
Game jams
Add later or when needed
Steamworks
Google Play Console
Console dev kits
Priorities
What to learn first, and what can wait
Focus beats coverage. These lists keep the first months pointed at what pays off.
Learn these first
1Programming fundamentals in your engine's language
2The game loop and delta time
3One engine's editor, scenes and scripting model
4Vectors for movement and direction
5Finishing tiny games from start to export
Safe to skip at the start
Writing your own engineA fascinating project, but it delays making games. Do it later if engine programming is your goal.
Open-world or MMO ideasFar beyond the scope of a first year. Save the dream project until you have shipped small ones.
Advanced shader programmingImportant for graphics roles, but gameplay basics come first.
Multiplayer networkingNetworking multiplies complexity. Learn it after single-player systems feel solid.
High-end 3D artUse free, licensed assets and focus on code and design.
Projects
Game development projects to finish
Ordered by difficulty. Two or three finished ones beat ten half-built ones.
Beginner
Arcade classic remake
Recreate Pong, Breakout or Asteroids with a score, restart and simple sound.
Game loop
Collisions
Beginner
Three-level platformer
Jumping, hazards, collectibles and a menu, exported as a playable build.
Engine basics
Tilemaps
Intermediate
Top-down survival game
Enemies with state machines, waves, upgrades and a save system.
AI
Saving
Game feel
Intermediate
3D puzzle game
Physics-driven puzzles with smooth camera control and clear feedback.
3D
Physics
Vectors
Advanced
Online two-player game
A small competitive game handling latency, synchronisation and disconnection.
Networking
Advanced
Published polished game
A complete game with settings, accessibility options, a store page and post-launch fixes.
Publishing
Optimisation
Avoid these
Common mistakes
Patterns that slow most learners down, and what to do instead.
Starting with a dream project
Large first projects are almost never finished. Build tiny games first and grow scope gradually.
Engine hopping
Every engine has frustrating parts. Switching resets your progress. Push through with one.
Ignoring maths
Copying movement code without understanding vectors leads to bugs you cannot fix.
No playtesting
You cannot judge your own game fairly. Watch other people play early and often.
Polishing too early
Make the core loop fun with placeholder art before investing in visuals.
Not using version control
Corrupted projects and broken changes are common. Git with LFS protects your work.
Career
Game developer career path
Portfolio, interviews and the checklist to review before you apply.
The games industry is competitive, and studios hire for specific skills: gameplay programming, tools, graphics, networking or engine work. General software skills keep more doors open - many game developers also work in simulation, education, film and interactive media. The software developer roadmap strengthens the fundamentals studios test for.
Typical job titles
Game Developer
Gameplay Programmer
Unity Developer
Unreal Developer
Tools Programmer
Technical Designer
Job-ready checklist
You are fluent in one engine and its language
You have finished and shared at least three games
You can explain vector maths used in your projects
You have profiled and optimised a game
You have worked to a deadline, such as a game jam
Portfolio guidance
Playable builds in the browser where possible
Short gameplay videos at the top of each project
Breakdowns of systems you personally built
Clean, readable code samples
State your role clearly on team projects
Interview preparation
C# or C++ programming tests
Vector maths and 3D transform questions
Designing a gameplay system on a whiteboard
Performance and memory questions
Discussing collaboration with art and design teams
Resources
Where to learn each part
References worth keeping open, plus the pages here that go deeper.
If you want to connect, please WhatsApp: 3265503569
One-to-one mentorship for the roadmaps on Fox Is Happy is being set up. Sessions will cover code review, project feedback, interview preparation and a learning plan matched to where you actually are - not where a generic curriculum assumes you are.
Pricing will be reasonable and listed clearly before you book - pay per session, with student-friendly rates planned. No subscriptions and no bundles you do not need.
Register interest
3265503569
WhatsApp only. Message on WhatsApp to register interest and be told first when places open.
Mention Game Developer Roadmap in your message so the reply matches what you are working on.
What game development work is really like
Making games is creative, technical and demanding. The developers who progress are the ones who ship - which means learning to cut features as skilfully as they add them.
Unity, Unreal or Godot?
All three can produce commercial games, and the skills transfer more than you might expect. Choose based on the games you want to make and the jobs near you.
Comparing popular game engines
Engine
Language
Strengths
Consider if
Unity
C#
Mobile, indie, 2D and 3D, large community
You want broad job options and many tutorials
Unreal Engine
C++ and Blueprints
High-fidelity 3D, AAA pipelines
You aim for large studios or realistic 3D
Godot
GDScript and C#
Free, open source, lightweight, great for 2D
You want a simple, fully open engine for indie work
Check each engine's current licensing terms before you publish commercially, since they can change.
How long does it take to become a game developer?
Most learners can make simple games within a few months. Becoming employable usually takes twelve to eighteen months of consistent practice, with several finished games to show. Specialised roles like graphics or engine programming take longer and often benefit from a computer science background.
Programmer, designer or both?
In large studios, programmers and designers are separate roles. In small teams, the lines blur. This roadmap focuses on the development side, but includes design because understanding why a mechanic is fun makes you far more effective at building it. Technical designer roles combine both.
Beyond the games industry
Game engine skills are in demand in simulation, training, architecture visualisation, film and interactive installations. These fields often offer more stable work and use the same tools. Strong programming fundamentals keep all of these routes open, and backend skills from the backend development roadmap are useful for online games.
A step-by-step learning plan for making games. This one takes you from programming basics through an engine, maths, design, 3D systems, optimisation and publishing, with a finished game at each stage.
Which engine should a beginner learn first?
Unity and Godot are the most beginner-friendly. Choose Unity for broad job options and tutorials, Godot for a free, lightweight open-source engine, or Unreal if you are focused on high-end 3D.
Do I need to be good at maths to make games?
You need practical vector maths, basic trigonometry and interpolation. These are learnable through projects. Graphics and physics programming need more advanced maths.
Can I become a game developer without a degree?
Yes, especially in indie and mobile studios, where playable work matters most. Larger studios and engine programming roles more often prefer a degree in computer science or a related field.
What games should I build for a portfolio?
Three small, polished, finished games that show different skills - for example a 2D platformer, a 3D game with AI, and a game jam entry - plus breakdowns of the systems you wrote.
Is C++ necessary for game development?
Not for everyone. C# is enough for Unity and Godot. C++ is important for Unreal, engine programming and many AAA studio roles.
