remoteExecCall

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.

ⓘ

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

⚠

The Call in remoteExecCall does not mean that the execution of the remote executed function / command will happen right away:

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

It just means that the execution of the function will take place in the unscheduled environment.

ⓘ

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).

Read Arma 3: Remote Execution for more information about usage, security features and advanced JIP techniques.

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, targets, JIP]: Array

functionName: String - Function or command name.
While any function or command can be used here, only those defined in 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 clients where the player is on the specified side.
• Group - The function / command will be executed on clients where the player is in the specified group.
  In order to execute the function / command where the group is local, use the groupOwner of the group: _myGroup remoteExecCall ["deleteGroup", groupOwner _myGroup];
• Array - Array of any 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 or Group is deleted, the remoteExecCall statement is automatically removed from the JIP queue.

See also Example 7 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.

Alternative Syntax

Syntax:

remoteExecCall [functionName, targets, JIP]

Parameters:

[functionName, targets, JIP]: Array

functionName: String - function or command name.
While any function can be used, only commands and functions defined in CfgRemoteExec will be executed.

targets (Optional): [default: 0 = everyone]

• Number
  • When 0, the function or command will be executed globally, i.e. on the server and every connected client, including the one where remoteExecCall was originated.
  • When 2, it will be executed only on the server.
  • When 3, 4, 5... it will be executed on the client where clientOwner ID matches the given number.
  • When number is negative, the effect is inverted. -2 means execute on every client but not the server. -12, for example, means execute on the server and every client, but not on the client where clientOwner ID is equal to 12.
• Object - the function will be executed only where unit is local
• String - the function will be executed only where object or group defined by the variable with passed name is local
• Side - the function will be executed only on clients where the player is on the specified side.
• Group - the function will be executed only on clients where the player is in the specified group. In order to execute the function where group is local pass owner of the group as param:
  _myGroup remoteExecCall ["deleteGroup", groupOwner _myGroup];
• Array - array of any of types listed above.

JIP (Optional): [default: false]

• String or Boolean - If true, function generates a unique ID for the message and the message itself is added to the JIP queue and executed for every JIP. If a non-empty string is given, it is treated a custom ID of the message and the message itself is added to the JIP queue overriding any remoteExecCall message with the same ID. Otherwise, no ID is generated and no message is placed into the JIP queue. (see also Example 7 on how to remove previously set function from JIP queue)
  
  
• Object or Group or netId - The persistent execution of the given remoteExecCall statement will be attached to the given Object or Group, passed directly by reference or by their netId: _netId = "this is my car" remoteExecCall ["hint", 0, car]; or _netId = "this is my car" remoteExecCall ["hint", 0, netId car];Upon success, the command will return netId of the used Object or Group or netId. When Object or Group is deleted and becomes objNull or grpNull, the persistent remoteExecCall statement is automatically removed from JIP queue. Manual removal of the JIP statement could be done by passing either Object, Group or netId as usual:remoteExecCall ["", car]; or remoteExecCall ["", netId car];When JIP param is String in format "Number:Number", the string will be tested first whether or not it is the valid netId of an existing Object or Group, and if not the execution will be aborted, if yes, that Object or Group will be used to set persistent execution.

ⓘ

JIP mostly makes sense for messages doing changes local to client (not directly synchronized over the network). Otherwise, after remoteExec is executed, depending on the contents of the global JIP queue there is a chance a new message could be added to it, unnecessary increasing the number of messages sent to any newly connected client. E.g. calling "..remoteExec ["setFuel"..]" is fine, however, calling "..remoteExec ["publicVariable",..]" is not.

⚠

There could be only one JIP message with the same JIP ID in the JIP queue. This means that if one tries to remoteExecCall again with the existing JIP ID, the JIP message which is already in the JIP queue will be overwritten. Passing true for JIP param autogenerates unique ID, therefore adding new message in the JIP queue each time. All other options have potential to overwrite existing JIP message.

Return Value:

Anything - Nil in case of error. String otherwise. If JIP is not requested this is an empty string, if JIP is requested, it is the JIP ID. See the topic Function for more information.

Examples

Example 1:

// runs hint "hello" on each connected client "hello" remoteExecCall ["hint"];

Example 2:

// runs hint "hello" on first connected client "hello" remoteExecCall ["hint", 3];

Example 3:

// runs hint "hello" everywhere but server "hello" remoteExecCall ["hint", -2];

Example 4:

// runs hint "hello" everywhere but server, JIPs the message // and returns e.g. "3_1" as a unique JIP id myJipID = "hello" remoteExecCall ["hint", -2, true];

Example 5:

// runs hint "hello" everywhere but server, JIPs the message under ID "some_JIP_ID" // replacing any previous message with this ID in the JIP queue. "hello" remoteExecCall ["hint", -2, "some_JIP_ID"];

Example 6:

// runs "someFuncWithNoArgs" on each connected client remoteExecCall ["someFuncWithNoArgs"];

Example 7:

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

Example 8:

// all clients will have their ammo set to 1 for their current weapon {player setAmmo [primaryWeapon player, 1];} remoteExecCall ["bis_fnc_call", 0];

Example 9:

// Object obj will have its ammo set to 1 where it is local [obj,[primaryWeapon obj, 1]] remoteExecCall ["setAmmo", obj];

Example 10:

myJipID = "hello" remoteExecCall ["", 0]; if (isNil "myJipID") then { hint "empty function name is not allowed"; };

Additional Information

See also:

remoteExecisRemoteExecutedisRemoteExecutedJIPremoteExecutedOwnercanSuspendBIS_fnc_MPRemote Execution

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

Posted on July 16, 2015 - 09:17 (UTC)

Killzone Kid

Removal of persistent call must be in the following format <no argument> remoteExecCall [<empty string>, <JIP id>]. For example: remoteExecCall ["", "5:8"];

Posted on December 29, 2015 - 20:31 (UTC)

AgentRev

remoteExec and remoteExecCall are currently filtered by BattlEye's remoteexec.txt, the string analyzed by BE is formatted the same way as the following example's output: format ["%1 %2", functionName, str params] If CfgRemoteExec class Functions is set to mode = 1;, the following remoteexec.txt exclusion can be used to safely allow all whitelisted *_fnc_* functions taking an array as parameter to go through: !="\w+?_fnc_\w+? \[[\S\s]*\]" Any attempt to exploit this exclusion using other RE methods like createUnit will run into "Error Missing ;" without any malicious code being executed. Mod makers should refrain from remote-executing raw commands from clients, as they require individual exclusions, and instead use *_fnc_* functions taking an array as parameter, which are covered by the above exclusion.

Posted on May 10, 2017 - 20:13 (UTC)

Killzone Kid

To remoteExecCall: titleText ["Test Message", "PLAIN", 1]; Use [["Test Message", "PLAIN", 1]] remoteExecCall ["titleText"];

Posted on January 17, 2020 - 15:05 (UTC)

Dscha

To send/execute custom functions and pass arguments (in this case to every connected Client, except the dedicated server):
[
[10,0],
{
player setAmmo [primaryWeapon player, (_this select 0)];
player setDamage (_this select 1)];
}
] remoteExecCall ["call", -2];