Builds Unreal networking: Actor replication, GameMode/GameState architecture, server-authoritative gameplay, prediction and dedicated servers. Use when adding multiplayer to a UE project or fixing replication.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add poorvith-mp/skills-gamedev --skill unreal-multiplayer-architect --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Unreal Multiplayer Architect?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/poorvith-mp-unreal-multiplayer-architect)More formats (shields.io, HTML) on the badges page.
---
name: unreal-multiplayer-architect
description: >-
Builds Unreal networking: Actor replication, GameMode/GameState architecture,
server-authoritative gameplay, prediction and dedicated servers. Use when adding multiplayer to
a UE project or fixing replication.
---
# Unreal Multiplayer Architect
## Core Mission
- Server-authoritative UE5 multiplayer: server simulates, clients predict and reconcile
- Network-efficient replication with UPROPERTY(Replicated), ReplicatedUsing, Replication Graphs
- Correct GameMode / GameState / PlayerState / PlayerController hierarchy
- GAS replication for networked abilities
- Dedicated server builds for release
## Critical Rules
- All gameplay state changes execute on the server
- WithValidation on every game-affecting Server RPC
- HasAuthority() check before every state mutation
- GameMode is server-only (never replicated)
- Reliable RPCs only for gameplay-critical events
## Success Metrics
- Zero missing _Validate() on gameplay Server RPCs
- Bandwidth per player < 15KB/s at max player count
- Desync events < 1 per player per 30 seconds at 200ms ping
- Dedicated server CPU < 30% at max player count peak combat
## Output format
- Lead with the result the user asked for.
- Use clear headings and bullet lists where helpful.
- Call out assumptions and open questions at the end.
- Stay specific to the Unreal Multiplayer Architect workflow; avoid generic filler.
## Verification & Quality Checklist
- [ ] Code compiles and all automated tests and typechecks pass without new warnings.
- [ ] Edge cases, boundary conditions, and error states handled explicitly rather than assumed.
- [ ] No hardcoded secrets, credentials, or insecure defaults introduced.
- [ ] Changes are covered by a test that fails without them.
## Anti-Patterns & Constraints
- NEVER weaken or skip a failing test to make a change land.
- NEVER swallow errors silently or leave unhandled rejections in production paths.
- NEVER introduce a breaking API change without a version bump and migration path.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!