# remoteExecCall

## Category
Multiplayer

## Arity
**Binary** — `<args> remoteExecCall [commandName, target, isJip]`.

```
<any> remoteExecCall <array>   // [commandName, target, isJip]
```

## Description
Same as [remoteExec](remoteExec.md) but uses **`call` semantics** (synchronous execution on the target) instead of `spawn`. The target executes the command immediately in its current scheduler context — no new fiber is created. Cannot suspend on the target.

## How It Works
Identical to `remoteExec` but the target executes via `call` instead of `spawn`. The command must not contain `sleep`/`await` or it will error on the target.

## Usage

```sqf
// Synchronous remote execution
[params] remoteExecCall ["fn_quickUpdate", 0, false];
[data] remoteExecCall ["fn_validate", 2, false];
```

### vs remoteExec
```sqf
// remoteExec: async, can sleep, returns handle
[args] remoteExec ["fn_longTask", 2, false];

// remoteExecCall: sync, cannot sleep, returns result
[args] remoteExecCall ["fn_quickQuery", 2, false];
```

> **Note**: Full networking requires host implementation.

## Thread Safety
Depends on host implementation. Target execution is synchronous.

## See Also
- [remoteExec](remoteExec.md) — async remote exec
- [call](call.md) — local synchronous execution
- [publicVariable](publicVariable.md) — broadcast variable