remoteExecCall: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "<code>([^<]*)\[\[([a-zA-Z][a-zA-Z0-9_]+)\]\]([^<]*) *<\/code>" to "<code>$1$2$3</code>") |
Lou Montana (talk | contribs) m (Text replacement - "\|x([0-9])= *<code>([^<]*)<\/code>" to "|x$1= <sqf>$2</sqf>") |
||
| Line 16: | Line 16: | ||
|r1= see [[remoteExec]] | |r1= see [[remoteExec]] | ||
|x1= < | |x1= <sqf>["hello"] remoteExec ["hint"]; // runs unscheduled | ||
["hello"] remoteExecCall ["hint"]; // no difference at all</ | ["hello"] remoteExecCall ["hint"]; // no difference at all</sqf> | ||
|x2= < | |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</ | ["my message"] remoteExecCall ["BIS_fnc_infoText"]; // wrong - BIS_fnc_infoText needs a scheduled environment, see its spawn need</sqf> | ||
|x3= < | |x3= <sqf>remoteExecCall ["fnc1"]; | ||
call fnc2; // 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; // fnc2 will be executed after fnc1</ | 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]] | ||
Revision as of 10:23, 13 May 2022
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
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