isServer: Difference between revisions
Jump to navigation
Jump to search
Killzone Kid (talk | contribs) No edit summary |
SilentSpike (talk | contribs) (Fixed broken note) |
||
| 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. | <dd class="notedate">Posted on April 8, 2011 | ||
<dt class="note">'''[[User:Igneous01|Igneous01]]''' | |||
example: | <dd class="note">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. For example: <code>this && isServer</code> | ||
this && isServer | |||
<!-- Note Section END --> | <!-- Note Section END --> | ||
Revision as of 19:41, 28 November 2014
Description
- Description:
- Returns true if the machine (executing the command) is the server in a multiplayer game or is running single player.
- 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
- Posted on April 8, 2011
- Igneous01
- 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. For example:
this && isServer
Bottom Section
- Posted on November 28, 2014 - 18:40 (UTC)
- Killzone Kid
-
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, for example:
this && isServer