Gameplay for Unreal Engines
Unreal gameplay is built on the Gameplay Framework, a set of classes with defined roles. GameMode sets the rules, the Pawn or Character is the controllable body, the PlayerController handles input and intent, and GameState and PlayerState hold shared and per-player data. Knowing these roles tells you where each piece of logic belongs.
Stage: Editor Basics · Part of the Unreal Engine roadmap · Last reviewed 19 November 2026
What to learn in Gameplay
- Explain what GameMode, PlayerController, Pawn and PlayerState each own
- Set a default pawn and controller for a level through GameMode
- Map keys to actions using Enhanced Input
- Spawn and destroy actors at runtime from Blueprint logic
- Communicate between Blueprints using interfaces, event dispatchers and casting
Gameplay interview questions
Why separate the PlayerController from the Pawn?
The Pawn is the physical body that can be destroyed or swapped, while the PlayerController persists and represents the player's will. Input and UI logic in the controller survives respawns, and one controller can possess different pawns such as a character or vehicle.
When should you use an interface instead of casting?
Casting creates a hard dependency on one specific class and can load extra assets. An interface lets unrelated classes respond to the same call, so a door, lever or chest can all implement Interact without the caller knowing their types.
Where Gameplay fits in the Unreal Engine roadmap
Gameplay belongs to the Editor Basics stage (beginner level), which takes about 37 hours. Learn Unreal.
Other units in this stage
Back to the full Unreal Engine roadmap