Preface · Why Ludo Atlas Exists

Chinese-language material on game development is never in short supply. Tutorials, videos, book lists, link dumps — a single search turns up hundreds of hits. What is missing is the skeleton that organizes them, and one complete route from "I want to make a game" to "it is out in the world."

This repository exists to add that skeleton. It addresses four long-standing problems:

• Learning has no order: beginners do not lack single-point tutorials; they lack a sequence, and a standard for how good is good enough to move on. The Getting Started section and the learning paths give three routes by goal, each step carrying an explicit bar to clear.
• Production stages lack material: most Chinese-language content stops at code and visuals, while the stages that really decide whether a project gets finished — kickoff, scope control, playtesting, localization, launch, compliance, live-ops — have very little systematic public documentation. This repository fills the gap with Pipelines & Workflows, Publishing & Business, and the playbooks, and gives each stage a minimal checklist.
• Material goes stale: engine versions, platform policies, fees and compliance requirements change every year, and blogs and videos often lag generations behind. Policy-related content here carries the date it was last checked; external links are verified one by one, and CI keeps re-checking them continuously.
• The AI era has no standard answers yet: coding agents and generative art and audio are entering real projects. The AI Workflows section collects reusable workflows, a tool matrix and compliance boundaries, to be picked up according to project scale.

The name comes from Latin: ludo (I play) and atlas (a map collection) — drawing as complete a map as possible for making games. There is only one organizing principle: place knowledge in the order real development happens. The content is Chinese-first; every document answers one concrete question, and documents reference each other instead of repeating.

This is a continuously maintained open-source project, and mistakes are unavoidable: Issues and PRs with corrections or additions are welcome, and errata get the highest priority.

If you can't do magic, you'll have to go to Hogwarts for training.