Code that runs
Variables, functions, conditionals, loops, and data structures control real creeps inside a persistent room.

Students build inside Screeps, an online strategy world where JavaScript controls a live colony. They code the systems that keep that colony running and leave with Git-backed proof of how they think. For parents, schools, churches, and program directors, it is a six-week workforce-development experience that blends fun, community, AI literacy, and real software habits.
Every concept connects to a colony students can see: loops move creeps, functions become reusable behaviors, Git protects working bot versions, APIs explain how code talks to systems, and automation helps the colony scale.
Variables, functions, conditionals, loops, and data structures control real creeps inside a persistent room.
Students commit working bot versions, read diffs, recover from broken changes, and leave with a visible repo history.
Screeps game objects make API thinking concrete while spawn logic, roles, and Memory teach automation loops.
Every cohort gets a dedicated AutoNateAI Discord channel for coding questions, Screeps discussion, hackathons, and industry networking.
Students test whether their automation, debugging, and strategy can hold up when another bot is trying to win.
The course starts with programming fundamentals inside Screeps, then moves toward strategy: roles, memory, automation, Git branches, and Codex-supported improvements. By the end, students are not just showing a project. They are running a colony built from their own decisions.

The cohort ends with an AutoNateAI capture-the-flag tournament inside Screeps where student colonies battle head-to-head. This is where the course gets loud: students see whether their logic, automation, and architecture hold up when another colony is trying to win.
These reads help families and program leaders see the bigger picture: why the game is fun, why the code matters, and how the cohort turns curiosity into workforce-ready habits.
The strongest youth technology programs do more than introduce tools. They help students practice focus, problem solving, communication, version control, and follow-through.
A tournament gives students a real reason to care about debugging, architecture, and strategy. Their code has to compete against another student's code.
A good coding program should help students understand feedback loops, constraints, resources, and tradeoffs. A real project gives those ideas something students can operate.