How to package a Motion project

Use this guide after the Motion demo path and your project character work in PIE. This procedure finds broken profile references, unavailable plugin content, invalid item configs, or late initialization warnings before release.

Before packaging

1. Run Quick start and make sure that the supplied demo moves.
2. Run your project character through Add Motion to a character.
3. Make sure that tuned component profiles point at /Game/... project assets, not edited plugin defaults.
4. If the project uses native first-person items, equip and unequip the item in PIE.
5. Fix Motion warnings before starting the cook.

Use the Gameplay Debugger and GAS overlay when the runtime state is unclear. During PIE, push the apostrophe (') key to open the Gameplay Debugger. Then, use the category key shown for Motion if that category is not visible.

showdebug abilitysystem
log LogMotionAbilitySystem Verbose

Reload before cooking

1. Save all changed assets.
2. Restart Unreal Editor.
3. Reopen the map that uses your Motion character.
4. Select Play in standalone mode.
5. Walk, sprint, crouch, and jump once.

This catches setup that only worked because an unsaved editor object was still loaded.

Package from Unreal Editor

Use the standard Unreal packaging flow:

1. Open Platforms in the editor toolbar.
2. Select your target platform.
3. Run the normal package action for your project.
4. Read the Output Log for Motion warnings or unavailable asset references.

Package from command line

For a Development Win64 package, run Unreal Automation Tool with your project path:

& 'C:\Path\To\UE_5.6\Engine\Build\BatchFiles\RunUAT.bat' BuildCookRun `
  -project='C:\Path\To\YourProject\YourProject.uproject' `
  -noP4 -platform=Win64 -clientconfig=Development `
  -build -cook -stage -pak -archive `
  -archivedirectory='C:\Path\To\YourProject\Saved\MotionPackage'

Adjust the engine path, project path, config, and archive directory for your project.

Expected result:

AutomationTool exiting with ExitCode=0 (Success)

Packaging failures

Symptom	Check
Missing Motion assets	MotionCore is enabled and plugin content references are valid
Missing project profiles	Component Profile fields point at saved /Game/... assets
Character does not initialize	PlayerState or character exposes an Ability System Component
First-person item missing	The item config has one valid first-person/world mesh pair
Crouch, sprint, or jump differs after reload	Tuning was made on transient component/runtime fields instead of the assigned profile or item config

Next steps

Debug Motion in PIEUse Motion and GAS overlays before packaging.Component profilesMake sure that tuned settings are in project-owned profile assets.Verify multiplayerDo a check of multiplayer behavior in two-client PIE before packaging.