Skip to content

remoteExecCall

ffredyk edited this page Jul 23, 2026 · 1 revision

remoteExecCall

Category

Multiplayer

Arity

Binary<args> remoteExecCall [commandName, target, isJip].

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

Description

Same as remoteExec 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

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

vs remoteExec

// 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

SQ# Wiki

Home

Engine Docs

Migration

Commands

Value Constructors

Arithmetic

Comparison

Logic

Array

String

Math

Random

Type & Introspection

HashMap

Code Execution

Concurrency

Scheduler

Thread Safety

Error

Output

Time

Multiplayer

Compiler

Clone this wiki locally