Flow Interaction
Interaction Design with Flow Interaction
Separate actor-side target selection from object-side interaction response.
- Audience
- Gameplay designers and developers
- Time
- 10 minutes
- Requires
- An actor and at least one interactable object
- Modules
- Flow Interaction
On this page
Flow Interaction models an actor choosing and using an object. The Flow Interaction Owner scans and selects. The Flow Interaction Target defines an available object, its interaction point, priority, and feedback. Graph logic decides the gameplay consequence.
Owner and Target
The Owner is the actor. It has a scan radius, selection mode, current target, optional explicit target, and Focus, Blur, and Interact events.
The Target is the object. It has a target radius, priority, local interaction point, availability, optional model root, optional Canvas feedback, and its own event routes.
此处插图应该是 Scene 视图中 Flow Interaction Owner 与三个 Target 的扫描范围 Gizmo 截图；显示 Owner Radius、各 Target Radius、当前 Focus 目标和 Forward 方向角，并标注候选筛选过程。
Runtime sequence
Focus is selection feedback, not the gameplay action. Blur removes that focus. Interact occurs only when requested and the current Target remains valid. Keep inventory changes, dialogue starts, pickups, and other consequences on the Interact route.
Choose a selection mode
| Mode | Use for | Design effect |
|---|---|---|
| Nearest | Pickups and forgiving proximity use | Distance dominates after target priority. |
| Forward | Conversations and intentional object use | The actor must face within the configured angle. |
| Explicit | Tutorials, lock-on, scripted moments, or UI selection | Graph logic assigns the target directly. |
Use Target priority sparingly. If every Target has elevated priority, nearby selection becomes difficult to predict.
Tune discoverability
- Owner radius defines how far the actor can discover candidates.
- Target radius makes large or important objects easier to include.
- Forward angle controls how precise facing must be.
- The local interaction point should match where the player expects to use the object, not necessarily its pivot.
- Canvas feedback can explain focus, while graph-owned UI handles larger panels and consequences.
Module boundary
Flow Interaction does not own quests, dialogue content, inventory, or input bindings. It detects and routes intent. A graph may respond by playing a Flow Character Gesture, changing Flow Stats, activating a Camera Shot, or calling an external system.
Video · 2:02Flow Character and Flow InteractionSee character behavior and interaction routing cooperate in one observable slice.