Skip to content
1.0 · DemoSample product content

Interaction workflow ​

The label shown to the player and the action that executes should use the same state. This example divides the workflow into four parts.

Target ​

The object the player wants to interact with. If a check finds multiple candidates, define an explicit priority rule: closest object, closest to the center of the view, or a game-specific choice.

Availability ​

Finding a target is not enough. Range, a lock, or a quest requirement may prevent an action.

ConditionExample result
No targetClear the label.
Target exists, but requirements are not metShow a reason when appropriate.
Target exists and requirements are metShow the available action.

Action ​

Check availability again when the player provides input. A door might have become locked or the target might have changed since the label was displayed. Execute against the current valid state.

Result ​

Distinguish success, failure, and cancellation. Update the object's state and the interface according to the result.

DESIGN NOTE

Hold-to-interact, multiple simultaneous targets, and network validation are outside this sample guide. If a real product supports them, document each in its own guide.

Multiple products. One knowledge base.