isServer: Difference between revisions
Jump to navigation
Jump to search
(add. classification) |
No edit summary |
||
| Line 27: | Line 27: | ||
<dl class="command_description"> | <dl class="command_description"> | ||
<!-- Note Section BEGIN --> | <!-- Note Section BEGIN --> | ||
You can use isServer inside the condition of a trigger to have the trigger activate only for the server. All other conditions for the trigger will be checked across all machines, but it will only activate the trigger created on the server. | |||
example: | |||
this && isServer | |||
<!-- Note Section END --> | <!-- Note Section END --> | ||
Revision as of 04:31, 8 April 2011
Description
- Description:
- Returns true if the machine is either a server in a multiplayer game or if it is running a singleplayer game.
- Groups:
- Uncategorised
Syntax
Examples
- Example 1:
if (!isServer) exitWith {}
Additional Information
- See also:
- isDedicated
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
Notes
-
You can use isServer inside the condition of a trigger to have the trigger activate only for the server. All other conditions for the trigger will be checked across all machines, but it will only activate the trigger created on the server.
example:
this && isServer