Interaction Guides

Use Interaction guides when you want to complete a workflow from start to finish.

This section is still early. The notes below describe the intended first workflows for Dynaros Interaction as the product docs are built out.

First Interaction

The first full guide should take you from enabling the plugin to confirming that an actor can receive an interaction request.

Typical flow:

Enable plugin
        v
Add UInteractorComponent to the initiating actor
        v
Add interactable behavior to a target actor
        v
Connect input to the interaction request
        v
Display prompt data through default or project UI
        v
Verify that the target receives the request

The goal is not to teach every advanced option at once. The goal is to get one clear interaction working, then show where to customize it.

Blueprint Workflows

Blueprint users should be able to use common Interaction behavior without editing plugin internals.

Common Blueprint tasks include:

• configure interactable text and enabled state
• react when an actor becomes focused or unfocused
• respond when interaction is requested
• connect a project input action to interaction
• display prompt information in UI
• enable or disable interaction based on project state

Blueprint workflows should stay practical: add the component, configure it, connect the events you need, and keep project-specific results in your own actor or system.

C++ Workflows

C++ users can work closer to the runtime contracts.

Common C++ tasks may include:

• implementing the interactable interface on an existing actor
• calling interaction APIs directly
• subclassing reference implementations where useful
• integrating Interaction with project-specific systems
• adding custom target discovery or validation behavior as those extension points mature

Reference pages should provide exact class names, headers, functions, and expected behavior when those APIs are finalized.

Common Guide Topics

Planned guide topics include:

• installing and enabling Interaction
• opening the showcase
• creating a first interactable actor
• connecting Enhanced Input
• showing prompt UI
• creating custom interactable behavior
• using Interaction with Nexus
• using Interaction without Nexus
• integrating with other Dynaros systems
• preparing for multiplayer-aware interaction

Until the complete guides are written, use Learn Interaction for the conceptual model and Interaction Reference for the current runtime symbols.