# Interactor API

Quick-reference for the Blueprint / C++ surface of
{cpp:class}`UMovaIxInteractorComponent`. For setup and usage narrative, see
{doc}`../guides/interactor`.

## Triggering

```{doxygenfunction} UMovaIxInteractorComponent::TargetInteraction
```

```{doxygenfunction} UMovaIxInteractorComponent::TargetStop
```

```{doxygenfunction} UMovaIxInteractorComponent::TargetImpact
```

## Server RPCs (routed via this component on the client)

These are what `TargetInteraction`, `TargetImpact`, and the typed-command / proximity
paths call under the hood. Call the client-facing wrappers instead of these
directly. They are listed here because the routing pattern matters for
{doc}`../guides/multiplayer`.

```{doxygenfunction} UMovaIxInteractorComponent::Server_TargetInteraction
```

```{doxygenfunction} UMovaIxInteractorComponent::Server_TargetAction
```

```{doxygenfunction} UMovaIxInteractorComponent::Server_TargetTags
```

```{doxygenfunction} UMovaIxInteractorComponent::Server_TargetImpact
```

## Radial menu

```{doxygenfunction} UMovaIxInteractorComponent::SetRadialSelectDirection
```

```{doxygenfunction} UMovaIxInteractorComponent::GetRadialSelectedIndex
```

```{doxygenfunction} UMovaIxInteractorComponent::RadialIndexFromDirection
```

Full member listing: {doc}`runtime-components`.

See also {doc}`../concepts/tag-grammar` for what a target string resolves to, and
{doc}`../guides/multiplayer` for why client requests must route via this
component, not a world-placed actor's Server RPC.