Most Unity courses teach you what buttons to click. We teach you how to think like a developer. Our autumn 2025 programme starts with the fundamentals everyone skips — then builds from there.
See What You'll Learn
Start from scratch. No previous coding experience needed. We spend the first three weeks on C# basics and debugging techniques before touching Unity at all.
You already know the basics. This track focuses on building robust game systems — inventory management, save systems, and AI behaviour that doesn't break.
Your game runs at 15fps and you don't know why. We'll teach you profiling, optimization patterns, and the architectural decisions that prevent problems before they start.
Our September 2025 intake runs for sixteen weeks. Classes happen twice weekly in the evenings, with project work you complete at your own pace. Most students spend about twelve hours per week total.
Pure C# programming without Unity. Variables, loops, methods, classes. You'll write console applications that solve real problems. Boring but essential.
GameObjects, transforms, basic physics. You'll build three small games from scratch — each one teaching a different core system. No tutorials to follow blindly.
UI frameworks, state machines, event systems. This is where most Unity developers get stuck. We spend extra time here because it matters most.
Build something that works and ships. You'll handle version control, build pipelines, and the unglamorous work of actually finishing a game. Most courses skip this part.
Lead Instructor, Systems Architecture
I've been writing Unity code since 2014, mostly for mobile games that needed to run on terrible hardware. That constraint taught me more about good architecture than any formal training ever did. These days I spend less time making games and more time teaching others how to avoid the mistakes I made.
Before Rextron, I worked at two studios that went under because our codebases became unmaintainable. That's why this course focuses so heavily on writing code you can actually work with six months later.
Thirty-two evening classes from September through December 2025. Tuesdays and Thursdays, 7pm to 9pm. All sessions recorded if you miss one, but the real value is asking questions while we code.
Every project submission gets reviewed by an instructor. Not just graded — actually reviewed with specific feedback on what works and what doesn't. This takes time but it's where most learning happens.
Starter code for common systems — not finished solutions, but proper architecture you can build on. Includes git workflows and folder structures that won't fall apart as projects grow.
Private discussion board where you can post code questions. Instructors check in daily. Other students help too — teaching others is how you really learn something.