1.50

Hover & click on the images for description

Description

Description:

Asks the server to execute the given function or script command on the given target machine(s). Execution always takes place in the unscheduled environment; suspension is not allowed.
Read Arma 3: Remote Execution for more information about remote execution, security features and JIP techniques.

⚠

The "Call" in remoteExecCall does not mean that the execution of the remote executed function / command will happen right away, it just means that the execution of the function / command will take place in the unscheduled environment:

remoteExecCall ["fnc1"]; call fnc2; // It is possible that fnc1 is executed after fnc2. call fnc1; call fnc2; // fnc2 will always be executed after fnc1.

ⓘ

Just like remoteExec, remoteExecCall can be used in SP; the behaviour is the same as in MP.

ⓘ

The direct execution of call or spawn via remoteExecCall (or remoteExec) should be avoided to prevent issues in cases where the remote execution of call or spawn is blocked by CfgRemoteExec. Instead it is recommended to create a function which is then excecuted by remoteExecCall (or remoteExec).

Groups:

Multiplayer

Syntax

Syntax:

params remoteExecCall [functionName, targets, JIP]

Parameters:

params: Anything - The parameter(s) for the function / command specified in the functionName parameter.

functionName: String - Function or command name.
While any function or command can be used here, only those allowed by CfgRemoteExec will actually be executed.

targets (Optional, default: 0):

• Number (See also Machine network ID) -
  • 0: The function / command will be executed globally, i.e. on the server and every connected client, including the machine where remoteExecCall originated.
  • 2: The function / command will only be executed on the server.
  • Other number: The function / command will be executed on the machine where clientOwner matches the given number.
  • Negative number: The effect is inverted: -2 means every client but not the server, -12 means the server and every client, except for the client where clientOwner returns 12.
• Object - The function / command will be executed where the given object is local.
• String - Interpreted as an Identifier (variable name). The function / command will be executed where the object or group identified by the variable with the provided name is local.
• Side - The function / command will be executed on machines where the player is on the specified side.
• Group - The function / command will be executed on machines where the player is in the specified group.
• Array - Array of any combination of the types listed above.

JIP (Optional, default: false):

• Boolean - If true, a unique JIP ID is generated and the remoteExecCall statement is added to the JIP queue from which it will be executed for every JIP.
• String -
  • If the string is empty, it is interpreted as false.
  • If the string is in format "Number:Number" (e.g. "0:0"), it is interpreted as a netId (see below).
  • Else the string is treated as a custom JIP ID and the remoteExecCall statement is added to the JIP queue, replacing statements that have the same JIP ID.
• Object, Group or netId - The persistent execution of the remoteExecCall statement is attached to the given object or group.
  When the object / group is deleted, the remoteExecCall statement is automatically removed from the JIP queue.

The JIP parameter can only be used if the targets parameter is 0 or a negative number.
See also Example 3 on how to remove statements from the JIP queue.

Return Value:

• nil - In case of error.
• String - In case of success.
  • If the JIP parameter was false or an empty string, the return value is "".
  • If the JIP parameter was true or a custom JIP ID, the JIP ID is returned.
  • If the JIP parameter was an Object, a Group or a netId, the (corresponding) netId is returned.

Syntax:

remoteExecCall [functionName, targets, JIP]

Parameters:

functionName: String - See the main syntax above for more details.

targets (Optional, default: 0): Number, Object, String, Side, Group or Array - See the main syntax above for more details.

JIP (Optional, default: false): Boolean, String, Object, Group or netId - See the main syntax above for more details.

Return Value:

nil or String - See the main syntax above for more details.

Examples

Example 1:

Execute hint "Example 1"; on various machines: "Example 1" remoteExecCall ["hint"]; // Executed on all machines. "Example 1" remoteExecCall ["hint", 3]; // Executed only on the first connected client. "Example 1" remoteExecCall ["hint", -2]; // Executed everywhere except on the server.

Example 2:

Execute hint "Example 2"; on various machines and add it to the JIP queue: _result = "Example 2" remoteExecCall ["hint", -2, true]; // _result is a unique JIP ID, e.g. "3_1". _result = "Example 2" remoteExecCall ["hint", -2, "My_JIP_ID"]; // _result is "My_JIP_ID". _result = "Example 2" remoteExecCall ["hint", 0, MyObject]; // _result is the unique netId of MyObject, e.g. "2:3". Note that if there already was a statement with the JIP ID "My_JIP_ID" in the JIP queue, that statement has now been overwritten.

Example 3:

Remove statements from the JIP queue: remoteExecCall ["", "My_JIP_ID"]; // The persistent statement with the JIP ID "My_JIP_ID" is removed from the JIP queue. remoteExecCall ["", MyObject]; // The persistent statement attached to MyObject is removed from the JIP queue.

Example 4:

Some more complex examples: ["Open", true] remoteExecCall ["BIS_fnc_arsenal", MyTargetPlayer]; [MyCurator, [[MyObject1, MyObject2], false]] remoteExecCall ["addCuratorEditableObjects", 2];

Example 5:

A tricky example: Trying to execute player setAmmo [primaryWeapon player, 1]; (on machines where the player is in MyGroup). Consider the following statements: {player setAmmo [primaryWeapon player, 1];} remoteExecCall ["call", MyGroup]; // Statement 1 [player, [primaryWeapon player, 1]] remoteExecCall ["setAmmo", MyGroup]; // Statement 2 Both statements look very similar, but only Statement 1 has the intended effect. This is because in Statement 2, the arguments player and primaryWeapon player are not resolved on the target machine(s), but on the machine executing remoteExecCall.

Additional Information

See also:

remoteExec remoteExecutedOwner isRemoteExecuted isRemoteExecutedJIP Arma 3: Remote Execution canSuspend BIS_fnc_MP

Notes

Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note