remoteExecCall: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Lou Montana (talk | contribs) m (Text replacement - "<sqf>([^↵][^<]*↵[^<]*)<\/sqf>" to "<sqf> $1 </sqf>") |
||
(122 intermediate revisions by 10 users not shown) | |||
Line 1: | Line 1: | ||
{{RV|type=command | |||
{{ | |||
| arma3 |= | |game1= arma3 | ||
|version1= 1.50 | |||
|gr1= Multiplayer | |||
| | |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| | |||
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]] | |||
| | |p1= see [[remoteExec]] | ||
|r1= see [[remoteExec]] | |||
| | |x1= <sqf> | ||
["hello"] remoteExec ["hint"]; // runs unscheduled | |||
["hello"] remoteExecCall ["hint"]; // no difference at all | |||
</sqf> | |||
|x2= <sqf> | |||
["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 | |||
</sqf> | |||
|x2= < | |||
|x3= <sqf> | |||
remoteExecCall ["fnc1"]; | |||
call fnc2; // fnc1 may or may not be executed after fnc2 | |||
call fnc1; | |||
call fnc2; // fnc2 will be executed after fnc1 | |||
</sqf> | |||
|seealso= [[remoteExec]] [[remoteExecutedOwner]] [[isRemoteExecuted]] [[isRemoteExecutedJIP]] [[Arma 3: Remote Execution]] [[canSuspend]] [[BIS_fnc_MP]] [[remoteExecutedJIPID]] | |||
}} | }} | ||
{{GameCategory|arma3|Remote Execution}} | |||
Latest revision as of 19:43, 3 September 2024
Description
- Description:
- Unscheduled version of remoteExec. The only difference between remoteExec and remoteExecCall is that remoteExecCall will run functions in unscheduled environment.
- 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:
Additional Information
- See also:
- remoteExec remoteExecutedOwner isRemoteExecuted isRemoteExecutedJIP Arma 3: Remote Execution canSuspend BIS_fnc_MP remoteExecutedJIPID
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