MovaInteract Documentation

A Blueprint-friendly modular interaction system for Unreal Engine 5.

Drop one component on any actor to turn it into an interactive object (a door, drawer, lever, elevator, light, machine, chest, NPC) and set up what it does visually, in a custom editor panel, with no Blueprint graph. Interactions are built from reusable States (poses that also drive audio, FX, physics, lights and animation), sequenced into Groups and Cycles, and triggered by tags, proximity zones, or a player Interactor. A gate system adds locks and conditions. Everything replicates and saves.

Getting Started

• Overview
  • The problem it solves
  • What one component gives you
  • How it is triggered
  • Design principles
  • Where to go next
• Installation
  • Requirements
  • Adding the plugin to a project
  • Enabling for a Blueprint-only project
  • Verifying the install
  • Next step
• Quick Start
  • Recipe 1: A door you open (60 seconds)
  • Recipe 2: A lamp that lights as you approach (no prompt)
  • Recipe 3: A drawer locked behind a keycard (gates)
  • When it doesn't work

Concepts

• The Model
  • Why this shape
  • Special states
  • See also
• States: everything one pose can drive
  • Transform (always present)
  • Audio
  • Niagara
  • Physics
  • Visuals
  • Animation
  • Params
  • Special states are not written states
  • When a state is actually recorded
• Groups & Cycles
  • Group settings
  • Carry is decided once, at the start
  • Cycles
  • See also
• Tag Grammar Reference
  • Two principles
  • Selection: which thing
  • Bones: / (only after @)
  • Execution: whose IC runs it (the ^ suffix)
  • Chaining: where ^ sits
  • State: :
  • Gate: ? (inline precondition, tags only)
  • Flow & label: start of a verb token
  • Wildcards
  • Worked examples
  • Where the prompt appears: $X,Y,Z
  • You rarely type this
• Proximity: reacting without a prompt
  • Shape: where the volume comes from
  • Enter / Leave: the same tag grammar
  • Use cases
  • Proximity vs the player Interactor
  • See also
• Gates: locks & conditions
  • Group-level: Gates
  • Tag-level: the inline ? gate
  • Other reasons a group can be rejected
  • Cross-object gates
  • RepeatPolicy and cycle rollback
  • Worked examples
  • See also
• Bones: addressing a rig like a component
  • The address: / after @
  • Why UPoseableMeshComponent, not USkeletalMeshComponent
  • Component-space driving
  • Deltas layer onto the captured @Zero bone pose
  • Showing up in the panel
  • Worked example: a door with a rigged hinge
  • See also
• Carrying: ferrying objects on a moving target
  • Decided once, at group start
  • Why once, not continuous
  • Requirements for a carried object
  • Use cases
  • Worked example
  • See also

Guides

• The player Interactor: setup and use
  • Add it to a pawn
  • How it finds the closest interactable
  • Firing an interaction
  • Events for your HUD
  • Choice input modes
  • Physics impact hook
  • Typing / interaction mode for NPCs
  • See also
• Grab, carry & throw
  • Add it to a pawn
  • What counts as grabbable: IsGrabbable
  • Tuning the feel
  • Composing with the tag grammar
  • Multiplayer: server-authoritative
  • See also
• Multiplayer
  • Turning it on
  • Server-authoritative execution + multicast
  • Late join: ReplicatedActionStates
  • Route client requests via the Interactor
  • Validated + range-verified
  • Replicated grab
  • Verifying it
  • See also
• Save & load
  • The two functions
  • What's persisted
  • Save-on-quit / load-on-continue
  • See also
• Presets
  • Listing and applying presets
  • Saving and managing user presets
  • Checking what a preset needs
  • Why plain JSON
  • Typical workflow
  • See also
• The IC Control Panel
  • Interaction tree
  • Scrubbable timeline
  • Field pickers
  • Validation chips
  • Guided interaction builder
  • Multi-actor transforms and copy/paste
  • Empty-state templates
  • Responsive, non-destructive editing
  • Recording interactions
  • Contextual help while you work
  • See also
• Level-wide export / import
  • Where it lives
  • The diff viewer
  • Blueprint defaults and placed instances, both
  • Why plain JSON matters
  • Typical workflow
  • See also
• Debug overlay & troubleshooting
  • The console command
  • The net-role banner
  • The fastest diagnosis
  • Persistent defaults
  • Troubleshooting / FAQ
  • See also

API Reference

• Runtime Components
  • MovaIxComponent
  • MovaIxGrabComponent
  • MovaIxInteractorComponent
  • MovaIxProximity
• Runtime Types
  • Action states, actions, groups, cycles
  • Core enums and small types
  • Addressing
  • Save data
• Interactor API
  • Triggering
  • Server RPCs (routed via this component on the client)
  • Radial menu
• Grab API
  • Verbs
  • Queries
  • Events
  • Tunables
  • Full class
• Settings
  • UMovaIxSettings
  • EMovaIxChoiceInput
• Editor API
  • Control panel
  • Inspector (Details panel customization)
  • Timeline widget
  • Presets
  • Commands, menu, style, visualizers
• Blueprint API Summary
  • Interaction
  • Grab
  • Save / load
  • Presets
  • Decision hooks (override in a C++ subclass)
  • Events to bind

Appendix

• FAQ / Troubleshooting
• Glossary
• Changelog
• Screenshots: status and how to add real ones

Where to start

• New to the plugin? Start with Overview, then follow Quick Start: three recipes that teach the whole system in under ten minutes.

• Looking for the addressing syntax (@Door, %Lift^, ?@Lock:Off)? Go straight to Tag Grammar Reference.

• Writing C++ or driving the system from a subclass? See Runtime Components.

• Something not interacting? Debug overlay & troubleshooting has the live console overlay and a problem table.