-
Notifications
You must be signed in to change notification settings - Fork 0
remoteExecCall
ffredyk edited this page Jul 23, 2026
·
1 revision
Multiplayer
Binary — <args> remoteExecCall [commandName, target, isJip].
<any> remoteExecCall <array> // [commandName, target, isJip]
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.
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.
// Synchronous remote execution
[params] remoteExecCall ["fn_quickUpdate", 0, false];
[data] remoteExecCall ["fn_validate", 2, false];// 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.
Depends on host implementation. Target execution is synchronous.
- remoteExec — async remote exec
- call — local synchronous execution
- publicVariable — broadcast variable
- Getting Started
- Language Guide
- Type System
- Control Flow
- Functions & Code
- Strings & Text
- Arrays & Collections
- Concurrency
- Promise System
- Thread Safety
- Host API & Embedding
- CLI Tool
- Bytecode Reference
- Multiplayer
- Syntax Sugar
- Optimization Guide
- Benchmarks
- count
- select
- pushBack
- append
- deleteAt
- deleteRange
- resize
- reverse
- sort
- find
- in
- forEach
- freeze
- thaw
- isFrozen
- currentScheduler
- clientOwner
- allSchedulers
- schedulerName
- schedulerExists
- schedulerBudget
- setSchedulerBudget
- fiberCount
- readyFiberCount
- waitingFiberCount
- schedulerLoad
- sendTo