Build Games That Actually Work

We assume you know basic programming. If you've written code in any language, you'll be fine. The first few weeks cover Unreal's specific patterns—reflection system, garbage collection, macros that look weird but matter.

You'll write a lot of gameplay code during this phase. Movement systems, combat basics, inventory management. The kind of systems every game needs in some form.

Most studios use both C++ and Blueprints. You need to know when each makes sense. We spend time on the C++/Blueprint boundary—exposing functions properly, using Blueprint interfaces, understanding when Blueprint overhead actually matters.

Some students prefer staying in C++. That's fine. But you should at least understand how designers will want to use your systems.

Networking in Unreal is its own beast. Replication, RPCs, relevancy, prediction—there's a lot. We don't cover every edge case, but you'll build a functional multiplayer prototype and debug the weird desyncs that always show up.

This section depends heavily on what your project needs. Some groups go deep on dedicated servers. Others focus on peer-to-peer gameplay. We adjust based on interest.

Your game will run slowly at some point. We teach you how to find out why. Unreal's profiling tools, CPU vs GPU bottlenecks, memory tracking, load time optimization.

This is where a lot of students have those "oh, that's why" moments. Understanding the cost of what you're doing changes how you write code.

How to package builds that don't crash. Setting up automation for cooking assets. Writing editor tools so you're not doing repetitive tasks manually. Version control strategies that don't make your teammates hate you.

Not glamorous, but these skills separate people who ship games from people who just work on them forever.