How Unity actually works
Not a click-here-then-there video course. Each topic explains one idea properly, shows the C# that goes with it, and links to scripts you can drop straight into a project.
15 topics About 170 minutes in all Free, no signup
Who this is for
This guide assumes you can already write a little code, and that what you actually need is Unity's model of the world: what a GameObject is, why components matter more than class hierarchies, and which of Unity's many ways to do a thing is the right one.
Read it in order
The topics build on each other. Components come before transforms, transforms before physics, because that is the order the ideas depend on each other.
Then use the code
Every topic links to working scripts from the script library and the kits, so you can go from understanding an idea to shipping it in the same sitting.
All 15 topics, in order
- GameObjects & Components The one idea Unity is built on
- The Transform Position, rotation, scale, and parenting
- Prefabs & Variants Reusable objects that stay in sync
- The MonoBehaviour Lifecycle Awake, Start, Update, FixedUpdate
- Colliders & Rigidbodies How Unity decides what touches what
- ScriptableObjects Data that lives outside the scene
- Scenes & Loading Additive scenes and scene flow
- Canvas & UI Anchors, scaling, and layout groups
- The Input System Actions, maps, and device support
- Coroutines & Async Doing things over time
- Grids & Tilemaps Snapping a world to a lattice
- Inventory Systems Items, stacks, and slots that survive a save
- Saving & Loading Getting state onto disk without losing it
- State Machines Taming "is jumping and also dead"
- Events & Decoupling Letting systems talk without knowing each other