isServer: Difference between revisions
Jump to navigation
Jump to search
Killzone Kid (talk | contribs) No edit summary |
Killzone Kid (talk | contribs) (missing category) |
||
Line 37: | Line 37: | ||
[[Category:Scripting Commands|ISSERVER]] | [[Category:Scripting Commands|ISSERVER]] | ||
[[Category:Scripting Commands ArmA|ISSERVER]] | [[Category:Scripting Commands ArmA|ISSERVER]] | ||
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]] | |||
[[Category:Command_Group:_Multiplayer|{{uc:{{PAGENAME}}}}]] | [[Category:Command_Group:_Multiplayer|{{uc:{{PAGENAME}}}}]] | ||
[[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}}}}]] |
Revision as of 10:20, 21 December 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
- Syntax:
- isServer
- Return Value:
- Boolean
Examples
Additional Information
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