How to use this site

vgai Learn separates three kinds of content, the way Unity, Godot, and Unreal do. Knowing which is which saves time.

Three kinds of content

Tutorials & Capstones How to accomplish a goal. Step-by-step, with a video and images, ending in something that runs.

Manual What a feature is and how it behaves. Conceptual depth, organized by subsystem.

Reference Exact symbols and schema fields. Auto-generated from the code, so it never drifts.

• Learning a goal? Start with a tutorial, quick start, or a capstone game.
• Understanding a system? Read the manual section for that subsystem.
• Looking up a field or API? Go straight to the reference.

Pathways

If you’d rather follow a guided route, the Pathways are curated, role-based sequences — Game Developer, Technical Artist, UI Developer, Multiplayer Developer, and Integrator — each with a hands-on lab and quizzes.

How lessons earn their place

Every tutorial/capstone/quick-start lesson on this site:

• carries a video and at least three images/diagrams;
• ends in a runnable result that is actually executed during validation;
• is reviewed by independent subagents against a quality rubric (technical accuracy, steps-actually-work, completeness, pedagogy, media). Any failure reopens the lesson.

Reference pages are generated from the engine’s own definitions, so they match the code by construction. The full quality plan lives in the roadmap.

Conventions

• Note / Tip / Caution callouts flag the things worth flagging.
• Code blocks are copyable; full blocks are type-checked in CI, partial blocks point at a real source file.
• See also links connect tutorials to the manual and reference.