New: Roadmaps ordered paths through our cheat sheets and flashcards, so you always know what to study next.
Explore themSee what's new on GitHubFrom your first game design sketch to a published Unity game players can buy.
A 12-step learning path. Follow it in order, or jump to what you need.
For aspiring game developers who want a shippable, portfolio-ready route into the industry, built around Unity and C#, the combination most studios and tutorials recommend for beginners. Plan on about 6 to 8 weeks at a few hours a week, moving from game design theory and working C# through Unity's engine, the math and physics running underneath it, AI-driven NPCs, and sound, to an actual store launch. This path stays on Unity and C#: it does not cover Unreal Engine's C++ workflow or professional 3D art and animation production beyond an optional Blender primer. By the end you can build a playable game in Unity with rendering, physics, and AI systems that behave correctly, add sound and feedback that make it feel alive, and publish it to players with a store page and pricing model built to convert.
Expected: comfort with basic programming concepts (variables, loops, functions) in any language. Helpful but not required: prior exposure to object-oriented programming or a 3D engine.
Every later step in this path serves a design decision, so start by learning the vocabulary: core loops, the MDA framework, and why a game's mechanics can feel completely different from what players actually experience.
Unity's entire scripting layer runs on C#, so step 1's design ideas need a language to become code in before step 4 puts them inside a game engine.
Once step 2's code is worth keeping, it needs a safety net: branches to try risky ideas and commits to undo the ones that don't work, before step 4's engine work makes losing progress expensive.
You can name why a game's loop hooks players, write real C# logic, and keep every experiment safely versioned in Git. Next up: opening Unity and turning that logic into something you can actually see and touch.
Finish this section to unlock.
+100 XP
This is where component-based architecture replaces the class-inheritance habits step 2 taught, and the Awake-to-Update frame order is where most beginner bugs come from; expect to come back to this lifecycle more than once.
Step 4's Transform and Vector3 calls work whether or not you know why; open that box here and learn the vector, matrix, and quaternion math actually moving and rotating everything on screen.
URP and Shader Graph in step 4 show which buttons to press; this goes underneath them to the rendering pipeline, shader math, and lighting models deciding whether a scene reads as flat or real.
Collisions that punch through walls and rigid bodies that jitter finally make sense here: broad and narrow phase detection, bounding volumes, and rigid body dynamics explain what step 4's Rigidbody component is doing underneath, using the vectors and matrices from step 5. Expect to debug this one more than once.
You can build a playable Unity scene where step 5's math drives movement correctly, materials and lighting read the way you meant, and objects collide the way real physics says they should, with a few minutes of due flashcards keeping step 1 and step 2 fresh while you build on them. Next up: giving it a brain, a voice, and a way out into the world.
Finish this section to unlock.
+100 XP
Take this if you're heading toward making your own 3D art instead of relying on the Asset Store: modeling and rigging here feed directly into the materials and animation systems step 4 already taught you to use.
NPCs that only follow a NavMesh path feel dumb; behavior trees, finite state machines, and classic algorithms like minimax give step 4's AI and Navigation table an actual decision-making brain to run.
AudioSource and AudioMixer in step 4 get a sound playing; sound design craft and middleware like FMOD and Wwise are what turn that into music and effects reacting to the physics and AI wired up in steps 7 and 9.
Pick this up if mobile free-to-play is your target platform: Play Billing and StoreKit's purchase and subscription lifecycles go deeper than step 12's general monetization overview, made for apps living on in-app purchases and ads.
Every earlier step becomes a finished game here: pricing models, a Steam or itch.io store page, and a wishlist launch plan are how the design from step 1 and the systems from steps 4 through 10 actually reach players.
You've taken a game from a design idea through math, rendering, physics, AI, and sound, all the way to a store page ready for players: that's exactly what the Game Developer badge marks.
Finish this section to unlock.
+100 XP
Finish every required step, at least 70% of them genuinely done (not skipped), to earn this badge and 500 XP.