remoteExecCall: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "{{HashLink" to "{{Link") |
Killzone Kid (talk | contribs) No edit summary |
||
Line 28: | Line 28: | ||
call fnc2; // fnc2 will be executed after fnc1</sqf> | 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]] [[remoteExecutedJIPID]] | ||
}} | }} | ||
{{GameCategory|arma3|Remote Execution}} | {{GameCategory|arma3|Remote Execution}} |
Revision as of 14:22, 14 July 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