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 $4</code>") |
Lou Montana (talk | contribs) m (Text replacement - "<code>([^<]*)\[\[([a-zA-Z][a-zA-Z0-9_]+)\]\]([^<]*) *<\/code>" to "<code>$1$2$3</code>") |
||
| Line 22: | Line 22: | ||
["my message"] remoteExecCall ["BIS_fnc_infoText"]; // 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</code> | ||
|x3= <code> | |x3= <code>remoteExecCall ["fnc1"]; | ||
[[call]] fnc2; // fnc1 may or may not be executed after fnc2 | [[call]] fnc2; // fnc1 may or may not be executed after fnc2 | ||
Revision as of 13:00, 12 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:
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