This page is my living Mover 2.0 link dump: Epic docs, Examples, sample projects, talks, and community notes that actually hold up when you open the editor. Mover is still Experimental—APIs move. Don’t ship the templates as-is; run Examples first, then bend them to your project.
I keep Network Prediction on a separate page: Network Prediction in Unreal Engine. Cross-read it when you pick the Network Prediction backend or touch NPP project settings.
My knowledge base (start here)
While digging through the code I keep notes in a Wiki on this site. Prefer that over a bookmark folder:
- Unreal Engine - Mover 2.0 Documentation: hub
- Mover Setup&Preparation: plugins, project settings, how to run the Examples maps
- Mover Input Mechanisms
- How Mover Affects Movement
- Mover Instant Movement Effect
- Mover Shared Settings
- Works with GAS
Two gotchas I already wrote into that KB: match the Examples Fixed Tick / Interpolated recommendations to your project—don’t cargo-cult them. And MovementMixer is created on BeginPlay, but other engine code can touch it earlier—I usually subclass MoverComponent or create the mixer during InitializeComponent. Dynamically spawned pawns are worse: Network Prediction can run before Mover’s InitializeComponent and null-crash. Place characters in the level first, then worry about spawn paths.
Official entry points
This order has worked well for me:
- Mover overview / Chinese: positioning vs CMC; README under
Engine/Plugins/Experimental/Mover/ - Mover features and concepts:
MoverComponent, modes, backends - Mover Examples: sample maps. Docs recommend Network Prediction: Preferred Ticking Policy = Fixed, Simulated Proxy Network LOD = Interpolated, Enable Fixed Tick Smoothing = True. Enable
Mover+Mover Examples, then walkL_CharacterMovementBasics; for physics-driven pawns seeL_PhysicsSimulatedCharacter - MoverNetworkPredictionLiaisonComponent: bridge when Mover uses the NP backend
- An Introduction to the Mover Plugin | Unreal Fest 2024 (YouTube): official intro, clear CMC comparison
- Project Titan on Fab: official sample-project direction with a Mover-driven player—study structure, don’t ship the jam template as production code
Talks / slides
- Network Prediction: Replication's Crystal Ball | Unreal Fest Bali 2025: concepts through NP and Mover—the talk I point people at first
- Iris And Mover Networking (Epic Games Japan · Tokyo DevDays 26'): Iris + Mover networking; Backend Liaison (Standalone / NetworkPrediction / ChaosMover) and NPP settings in detail
- Project Titan & Mover design (Epic Games Japan): open-world workflow and next-gen movement from Titan
- A Dive Into Networked Physics-Based Character Movement | Unreal Fest Stockholm 2025: Chaos Mover, networked physics, rewind / resim
- Mover 2.0 Overview (YouTube): quick capability sweep
Community notes I keep bookmarked
- Mover 2.0 + UAF + Motion Matching (UE 5.7) – David Martinez: wiring Mover into UAF / Motion Matching on source 5.7—animation-pipeline heavy
- Mover multiplayer pitfalls (Zenn): NPP clock when CMC and Mover share a session, and why Simulated Proxy should be Interpolated instead of blind Forward Predict
- Mover 5.6 Standalone Liaison issue (Epic forums): Standalone backend lifecycle quirks—worth a glance before upgrading
- UE5.4 Mover 2.0 intro (Zhihu): early Chinese overview—dated, use as an index
Pitfalls I’ve hit (short)
- Project Settings → Network Prediction: the Examples path is usually Preferred Ticking Policy = Fixed, Simulated Proxy = Interpolated, Fixed Tick Smoothing on. Tune for your latency and gameplay—don’t paste blindly.
MovementMixer/InitializeComponentordering: dynamic spawn is the crashy path; validate with scene-placed characters first.- Mixing CMC and Mover in the same multiplayer session: see the Zenn note above—NPP clocks only advance for ModelDefs that have a local Autonomous proxy.
I’ll keep adding official links and notes I’ve actually verified.
