How game engines work
Understand scenes, objects, assets, scripts, input, physics, rendering, and the main game loop.
Explore engine basics →Learning paths
Choose the level that best matches your current experience. Each path emphasizes one clear outcome and points toward a practical next step.
Beginner
Start here if you have never finished a game prototype or are still choosing an engine.
Understand scenes, objects, assets, scripts, input, physics, rendering, and the main game loop.
Explore engine basics →Match project scope, workflow, code preference, and target platform before committing.
Take the engine quiz →Turn an idea into a short loop with a player goal, clear failure state, and one polished mechanic.
Follow the roadmap →Intermediate
Use this level after you can move through an editor, write or assemble basic logic, and export a prototype.
Separate input, player state, world rules, UI, saving, and reusable data so iteration stays manageable.
Explore engine systems →Improve responsiveness through timing, animation, camera behavior, sound, particles, and readable state changes.
Study project examples →Use versioned files, naming rules, small milestones, test builds, and deliberate scope control.
Read studio notes →Advanced
Use this level when you need to reason about performance, platform constraints, tools, or custom systems.
Study frame budgets, batching, memory, asset loading, shaders, profiling, and platform-specific constraints.
Build repeatable import, validation, level-authoring, content, and deployment workflows for a team.
Compare source access, extensibility, data flow, physics, serialization, networking, and custom-engine costs.
Compare approaches →Use the engine quiz, then make a prototype small enough to finish in a few focused sessions.