Networked Mover characterKBVEMover
The shared control-character layer built on UE5's Mover plugin — a networked, data-driven pawn that runs alongside the legacy CharacterMovementComponent. Server-authoritative with client prediction, so it works standalone, listen-server, and on the dedicated server.
Client-predicted, server-authoritative
Built on UE5's Mover plugin — client prediction with server authority — so it runs standalone, on a listen-server, and on the dedicated server. Runs parallel to the legacy CMC character; games opt in per game.
- Pawn — AKBVEMoverPawn is the Mover-backed IKBVEMovementDriver.
- Pulls in — Mover + EnhancedInput (depends on KBVEGameplay).
The pawn
AKBVEMoverPawn
Pawn composition
An APawn with a capsule root, skeletal mesh, third-person camera, and a UCharacterMoverComponent (default Walking / Falling / Flying modes).
Input production
Implements IMoverInputProducerInterface and sets itself as the InputProducer; Enhanced Input accumulates intent, and ProduceInput translates it into the Mover sim's FCharacterDefaultInputs (camera-relative move, orientation intent, jump).
Networked by default
Server-authoritative with client prediction — standalone, listen-server, and dedicated server, running parallel to the legacy CMC character. Movement replicates through Mover; PlaceAt teleports via FTeleportEffect so the simulation agrees.
Gameplay scaffolding
Implements IKBVEStatTarget over a replicated stat array, owns a UKBVEEffectComponent, and traces Interact input to IKBVEMoverInteractable.
Foot IK and weapon grip
UKBVEFootIKAnimInstance plants both feet on sloped ground and solves the hands onto a weapon described by a UKBVEWeaponGrip data asset.
Editor helpers
The KBVEMoverEditor module creates physics assets and measures weapon cross-sections off a skeletal mesh.
Integration
Usage
Enable the plugin (pulls in Mover + EnhancedInput), derive a BP from AKBVEMoverPawn, assign the mesh + input assets, and set it as the DefaultPawnClass. Networking is automatic. It runs parallel to a game’s legacy CMC character — opt in per game.
AKBVEMoverPawn implements IKBVEMovementDriver from KBVEGameplay, so gameplay code can drive it without binding to Mover. Move it with PlaceAt, never SetActorLocation: Mover reconciles the component to its own simulation every tick.
Planned
Roadmap
- A CMC driver behind the same
IKBVEMovementDriverseam. - A locomotion graph to replace the single-clip foot-IK layer.
- Custom movement modes (sprint / dash / swim).
Questions
Frequently asked
What is KBVEMover?
KBVEMover is the shared control-character layer for KBVE games, built on UE5's Mover plugin. It is a networked, data-driven pawn that runs alongside the legacy CharacterMovementComponent stack, working standalone, on a listen-server, and on a dedicated server.
What is AKBVEMoverPawn?
AKBVEMoverPawn is an APawn with a capsule root, skeletal mesh, third-person camera, and a UCharacterMoverComponent (Walking, Falling, Flying modes). It implements IMoverInputProducerInterface and translates Enhanced Input into the Mover sim's FCharacterDefaultInputs.
How do I use KBVEMover in a game?
Enable the plugin (it pulls in Mover and EnhancedInput), derive a Blueprint from AKBVEMoverPawn, assign the mesh and input assets, and set it as the DefaultPawnClass. Networking is automatic and it runs parallel to the legacy CMC character, so games opt in per game.
Discuss on the forum
Questions, fixes and notes on this page live in the KBVE forum.