C++ programming
How the engine is built and how to extend it in C++, from module layering and the object model to plugins, live coding and profiling.
This section is for programmers who write engine-side C++: game modules, plugins, editor extensions and engine changes. It explains how the engine is put together and which rules keep it working. If you have written Unreal C++, most of it will look familiar: the names follow Unreal's prefixes with M in place of U (MObject, MClass, MWorld).
Gameplay topics (actors, components, physics, input) live in Gameplay. The build tool and its rules files live in Build tool.
Start here
Libraries and tools
Conventions
| Prefix | Used for | Example |
|---|---|---|
M | Garbage-collected objects (Unreal's U) | MObject, MActorComponent, MWorld |
A | Actors | AActor |
F | Plain structs and value types | FName, FTransform |
I | Interfaces | IPlatformFile |
T | Templates | TObjectPtr, TWeakObjectPtr |
E | Enums | EFileType |
Engine code lives in the Mowo namespace. Member variables are named m_Something and static members sm_Something.
The full list of public types is in the API reference: 2603 types across the engine's public headers.
Engine sources
This page describes behavior implemented in these files of the engine repository, checked against commit 3f3a08d31.
- Engine/Source/Runtime/Core/Public/Core/MObject.h
- Engine/Source/Runtime/Reflection/Public/Reflection/ReflectMacros.h
- Engine/Source/Runtime/Core/Public/Core/FModuleManager.h
- Engine/Source/Runtime/Project/Public/Project/PluginManager.h