isServer: Difference between revisions
Jump to navigation
Jump to search
Killzone Kid (talk | contribs) (removed category) |
Killzone Kid (talk | contribs) No edit summary |
||
Line 42: | Line 42: | ||
[[Category:Command_Group:_System_Commands|{{uc:{{PAGENAME}}}}]] | [[Category:Command_Group:_System_Commands|{{uc:{{PAGENAME}}}}]] | ||
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]] | ||
<!-- CONTINUE Notes --> | |||
<dl class="command_description"> | |||
<dd class="notedate">Posted on November 28, 2014 - 18:40 (UTC)</dd> | |||
<dt class="note">[[User:Killzone Kid|Killzone Kid]]</dt> | |||
<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:<br> | |||
<code>this && [[isServer]]</code> | |||
</dd> | |||
</dl> | |||
<!-- DISCONTINUE Notes --> |
Revision as of 19:40, 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
-
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
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