Ue Gameplay Framework

This walks you through Unreal's core gameplay classes and, crucially, which ones exist on server versus client. The editor's take: most multiplayer bugs come from misunderstanding that GameMode only lives on the server while GameState replicates everywhere, or that each client only sees its own PlayerController. The skill opens with a context check that forces you to declare single-player versus multiplayer and dedicated versus listen server, which is smart because those answers change which classes you subclass. It includes the actual API signatures from engine headers for spawn pipelines, login flow, and replication setup. If you've ever wondered why your score variable isn't showing up on clients or why possession fails silently, start here.

skills.sh installs: 1.4K
GitHub stars: 446
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add quodsoler/unreal-engine-skills --skill ue-gameplay-framework --agent claude-code

Installs into .claude/skills of the current project.

Files

UE Gameplay Framework

Target engine: UE 5.8. APIs below are verified against the 5.8 headers; older forms are listed under "Deprecated — do not use".

The gameplay framework is the set of classes the engine spawns for you — AGameModeBase, AGameStateBase, APlayerController, APlayerState, APawn, ACharacter, AHUD, UGameInstance — plus the join, spawn, match-state, travel and damage flows that wire them together. All of it ships in the Engine module (Classes/GameFramework, Classes/Engine, Classes/Kismet), so Build.cs needs "Core", "CoreUObject", "Engine". Add "EnhancedInput" when binding input, and "OnlineSubsystem" + "OnlineSubsystemUtils" (or "OnlineServicesInterface") only when touching sessions.