remoteExecCall: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
(Page cleanup)
m (Text replacement - "{{HashLink" to "{{Link")
 
(9 intermediate revisions by the same user not shown)
Line 8: Line 8:
|descr= [[Scheduler|Unscheduled]] version of [[remoteExec]]. The only difference between [[remoteExec]] and [[remoteExecCall]] is that [[remoteExecCall]] will run '''functions''' in [[Scheduler#Unscheduled Environment|unscheduled environment]].
|descr= [[Scheduler|Unscheduled]] version of [[remoteExec]]. The only difference between [[remoteExec]] and [[remoteExecCall]] is that [[remoteExecCall]] will run '''functions''' in [[Scheduler#Unscheduled Environment|unscheduled environment]].
{{Feature|important|
{{Feature|important|
The "Call" in [[remoteExecCall]] only means that the remote execution will take place in [[Scheduler#Unscheduled Environment|unscheduled environment]] and does '''not''' mean it will happen right away (see {{HashLink|#Example 3}}).}}
The "Call" in [[remoteExecCall]] only means that the remote execution will take place in [[Scheduler#Unscheduled Environment|unscheduled environment]] and does '''not''' mean it will happen right away (see {{Link|#Example 3}}).}}


|s1= see [[remoteExec]]
|s1= see [[remoteExec]]
Line 16: Line 16:
|r1= see [[remoteExec]]
|r1= see [[remoteExec]]


|x1= <code>["hello"] [[remoteExec]] ["hint"]; {{cc|runs unscheduled}}
|x1= <sqf>["hello"] remoteExec ["hint"]; // runs unscheduled
["hello"] [[remoteExecCall]] ["hint"]; {{cc|no difference at all}}</code>
["hello"] remoteExecCall ["hint"]; // no difference at all</sqf>


|x2= <code>["my message"] [[remoteExec]] ["BIS_fnc_infoText"]; {{cc|correct}}
|x2= <sqf>["my message"] remoteExec ["BIS_fnc_infoText"]; // correct
["my message"] [[remoteExecCall]] ["BIS_fnc_infoText"]; {{cc|wrong - [[BIS_fnc_infoText]] needs a scheduled environment, see its [[spawn]] need}}</code>
["my message"] remoteExecCall ["BIS_fnc_infoText"]; // wrong - BIS_fnc_infoText needs a scheduled environment, see its spawn need</sqf>


|x3= <code>[[remoteExecCall]] ["fnc1"];
|x3= <sqf>remoteExecCall ["fnc1"];
[[call]] fnc2; {{cc|fnc1 may or may not be executed after fnc2}}
call fnc2; // fnc1 may or may not be executed after fnc2


[[call]] fnc1;
call fnc1;
[[call]] fnc2; {{cc|fnc2 will be executed after fnc1}}</code>
call fnc2; // fnc2 will be executed after fnc1</sqf>


|seealso= [[remoteExec]] [[remoteExecutedOwner]] [[isRemoteExecuted]] [[isRemoteExecutedJIP]] [[Arma 3: Remote Execution]] [[canSuspend]] [[BIS_fnc_MP]]
|seealso= [[remoteExec]] [[remoteExecutedOwner]] [[isRemoteExecuted]] [[isRemoteExecutedJIP]] [[Arma 3: Remote Execution]] [[canSuspend]] [[BIS_fnc_MP]]

Latest revision as of 18:43, 4 January 2023

Hover & click on the images for description

Description

Description:
Unscheduled version of remoteExec. The only difference between remoteExec and remoteExecCall is that remoteExecCall will run functions in unscheduled environment.
The "Call" in remoteExecCall only means that the remote execution will take place in unscheduled environment and does not mean it will happen right away (see Example 3).
Groups:
Multiplayer

Syntax

Syntax:
see remoteExec
Parameters:
see remoteExec
Return Value:
see remoteExec

Examples

Example 1:
["hello"] remoteExec ["hint"]; // runs unscheduled ["hello"] remoteExecCall ["hint"]; // no difference at all
Example 2:
["my message"] remoteExec ["BIS_fnc_infoText"]; // correct ["my message"] remoteExecCall ["BIS_fnc_infoText"]; // wrong - BIS_fnc_infoText needs a scheduled environment, see its spawn need
Example 3:
remoteExecCall ["fnc1"]; call fnc2; // fnc1 may or may not be executed after fnc2 call fnc1; call fnc2; // fnc2 will be executed after fnc1

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